On Thu, Jan 29, 2015 at 11:03 AM, jean-delahousse <delahousse.jean@gmail.com > wrote: > Thoughts: > > PROV(enance) ontology could be very useful to describe the changes and > link them to related "issues" as well as formal decision which validate > the change. > In terms of linking between versions of the schema, these W3C PROV predicates may be useful: * http://www.w3.org/TR/prov-primer/ prov:wasRevisionOf prov:wasDerivedFrom prov:wasRevisionOf >From OWL and dcterms: owl:versionIRI owl:priorVersion dc:isVersionOf >From XKOS (for more granular relations between (versions of) vocabularies): * https://github.com/linked-statistics/xkos/blob/master/xkos.ttl * http://www.ddialliance.org/Specification/RDF/XKOS xkos:supersedes xkos:precedes xkos:succeeds [...] There's likely some insight here: https://stackoverflow.com/questions/2014237/what-are-the-best-practices-for-versioning-xml-schemas It may be helpful to ask a question here: http://answers.semanticweb.com/ * http://answers.semanticweb.com/search/?q=versioning&Submit=search&t=question * http://answers.semanticweb.com/questions/453/how-to-implement-semantic-data-versioning * http://answers.semanticweb.com/questions/2815/how-do-i-knowmodel-the-applied-version-of-an-ontology-specification * http://answers.semanticweb.com/questions/3499/ontology-version-control-systems * http://answers.semanticweb.com/questions/3677/what-provenance-vocabulary-should-we-use (2011) The Talis Changeset vocabulary does seem very approachable: * http://vocab.org/changeset/schema.html > Best regards > >
Received on Thursday, 29 January 2015 18:45:25 UTC