This page for describes the 'Historical Data' proposal for a schema.org extension. The schema.org team expect to add this, when finalised.
The historical-data.org site proposes some extensions to schema.org to address historical and genealogical (family history) scenarios.
It adds HistoricalRecord, HistoricalEvent (subclass of Event), overrides attendees, subEvents, superEvent to point to HistoricalEvent. It is currently (May 2012) being amended in light of feedback from schema.org.
- discussion is focussed around the associated github repository
- several sites are publishing a lot of data using the draft vocabulary, but they understand it is experimental and subject to change
- Issues: there is interest in using 'Place' (perhaps as 'HistoricalPlace'), and in moving to use 'familyName','givenName' from Person, while acknowledging the difficulties with any structured representation of personal names.
- See also WebSchemas/Singularity decision, which introduces preferred singular terms: parent, sibling (previous pattern was to name properties with a plural, even though the point to a single entity)
The BBC is looking to publish structured data about historical events in the near future, using the Event, Timeline and Stories Ontologies. Discussion and feedback on preferred approaches from the point of view of schema.org are welcomed.
On personal naming, see
- http://www.w3.org/International/questions/qa-personal-names .
Family History -related data modeling and exchange:
- RDF and uncertainty from Jeni Tennison.
- Family trees, Gedcom::FOAF in CPAN, and provenance.
- GedComX (github), work towards an XML-based Gedcom successor.
- genealogy in the microformats wiki
Another approach to events, narrative ordering, interpretations and links to sources:
The Stories Ontology developed by Mike Jewell, Toby Harris and Paul Rissen