Vocabularies and schemata you may wanna compatible with

[k00ni]

@opyh: As we discussed; here is some input from my side.

During my research i found the following vocabularies and schemata, which may be of interest for a11y-json.

Linked Open Data / RDF

• The vocabulary for (L)OD description of wheelchair accessibility - http://semweb.mmlab.be/ns/wa#
• Basic Geo (WGS84 lat/long) Vocabulary - http://www.w3.org/2003/01/geo/ (you may already know that)
• dbpedia - https://dbpedia.org (and the wiki) (DBpedia is basically the RDF version of the wikipedia and therefore more meaningful information. It might be worth it to check their properties/classes.)
• DCMI Metadata Terms and - Elements - http://dublincore.org/specifications/dublin-core/dcmi-terms/2012-06-14/ (Dublin Core metadata terms cover a wide area of basic terms, including language, license, locations and physical resources. Its heavily used.)

Side note: In the Linked Open Data / Semantic Web community it is common that you try to reuse existing schemata / ontologies / vocabularies. In practice its hard to follow it all the time, because sometimes existing models/properties/classes don't fit your current use case 100%. We should take a deeper look in this space to spot further sources. Chances are high that other repositories may also using this, which automatically increases compatibility.

Common data specifications/vocabularies

• Schema.org - http://schema.org/ (i guess its widely known, but i have not seen any properties in this specification. for instance PostalAddress or OpeningHoursSpecification may candidates for future work.)
  • Regarding opening hours: Google provides a detailed site, about which data/properties are relevant: https://developers.google.com/search/docs/data-types/local-business

About the dbpedia

Its an important data source and -reference in the Linked Open Data / RDF community. If an use case is about something in the Wikipedia, related DBpedia resources will be used. That is a common way to find consensus and similarities in data and concepts. I can help here. A big advantage: If a11y-json resources reference DBpedia entries and are transformed to RDF, related data can be merged very easily.

Further information:

• Overviews here and here
• Paper about DBpedia with more details, technical information and its history

[k00ni]

Just referencing the discussion on schema.org about modelling place accessibility related information: https://github.com/schemaorg/schemaorg/issues/254