I am making a RDF feed for Marseille Provence 2013, which is a series of cultural events that will take place in 2013 in Marseille in France through 2013.

Here is the RDF : http://api.mp2013.fr/rdf

More than 500 events are in the feed.

The RDF is built from a source that gives us information about accessibility (in the large acceptation of the word) for each event : accessibility for handicapped people, for children, animals accepted or not).

I can't find any semantic vocabulary available for describing accessibility characteristics for events (or services) nor can I find any study on the matter.

Does somebody know if a standard semantic vocabulary exists for accessibility and if not, what would be the best practice to start a new standard ?

asked 13 Dec '12, 06:21

kaweedo's gravatar image

accept rate: 0%

edited 13 Dec '12, 06:51

Take a look at the Ticket ontology


Object properties include eligible audiences and age ranges:


You may not get everything you need from this ontology, but its definitely the place to start

permanent link

answered 13 Dec '12, 09:14

William%20Greenly's gravatar image

William Greenly
accept rate: 13%

While the tickets ontology models age eligibility well, I think that its important to consider disability very carefully before trying to reuse a vocabulary to describe accessibility. eg. I wouldn't model it as an "ineligibility criterion" for people attending the event (eg. http://vocab.muni-ontology.org/classes/Wheelchair_users.html),

The ICF - http://bioportal.bioontology.org/ontologies/1411 and http://www.meteck.org/teaching/ontologies/adolena.owl might be interesting for a more in depth example of modelling disability.

I think that it is preferable to describe a building or events facilities ie. will it be convenient for somebody in a wheelchair to attend this event.

A class such as http://purl.org/ontology/muni#Accessible_buildings isn't really suitable because some rooms are accessible eg. ground floor, while some are relatively inaccessible eg. top floor with no lift. (Exhaustingly describing bathroom facilities, lifts, ramp slopes, door widths etc. would be tedious though)

Personally I would be keen to find/coin a custom boolean property of "isWheelchairAccessible" for an event. ?see - http://sigma.ontologyportal.org:4010/sigma/OWL.jsp?kb=SUMO&term=WheelchairAccessible

permanent link

answered 13 Dec '12, 10:22

Sweet%20Burlap's gravatar image

Sweet Burlap
accept rate: 19%

News just came out of schema.org today on this topic: http://blog.schema.org/2013/12/content-accessibility.html

Our reporting here: http://semanticweb.com/welcome-schema-org-v1-0e/

The schema.org page: http://schema.org/CreativeWork

Further details on the properties and expected values: http://www.w3.org/wiki/WebSchemas/Accessibility

Congrats to all involved!

permanent link

answered 05 Dec '13, 18:41

Eric%20Franzon's gravatar image

Eric Franzon ♦♦
accept rate: 31%


While good news, it sadly doesn't answer the question which is about venue/concert accessibility instead of website accessibility. i.e. accessibility to Event instead of to CreativeWork

But contacting the people who worked on this part of schema.org to suggest an extension to mark up Events and Locations with such access information is a good idea.

(06 Dec '13, 06:04) Jerven ♦ Jerven's gravatar image
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 13 Dec '12, 06:21

question was seen: 1,148 times

last updated: 06 Dec '13, 06:06