- From: Carl Mattocks <carlmattocks@checkmi.com>
- Date: Mon, 28 Jul 2008 13:10:55 -0400 (EDT)
- To: "Frederick Giasson" <fred@fgiasson.com>
- Cc: "Alistair Miles" <alistair.miles@zoo.ox.ac.uk>, "'Laurent LE MEUR'" <laurent.lemeur@afp.com>, public-swd-wg@w3.org, public-esw-thes@w3.org
Alistair, Fred, et al: IMHO as long contributor to standards - yes it makes sense. ... ... to change the URI of all classes and properties because some properties and some classes changed their semantic. .. mostly because to do otherwise would create massive editorial burden on KOS author's finest regards Carl <quote who="Frederick Giasson"> > > Hi Alistair, > > > First, about the SKOS discovery engine, I do think that PTSW > (pingthesemanticweb.com) could be a first step in that direction (at > least a first series of URIs that use SKOS classes). > > > Now, about versionning: this is a question that everybody seems to > stumble upon. Old ontologies such as SKOS and FOAF now have a problem: > they have are getting really popular (used) and this kind of changes are > trickier and trickier. > > However, does it make sense to change the URI of all classes and > properties because some properties and some classes changed their > semantic? Possibly that it could make sense (still musing on that stuff) > only to change the URI of the classes and properties that changed their > semantics. Next question: what make sense then, to create a new > namespace for these updated properties or to keep the old one and change > the name of the class or property? > > Also, was there issues using the DeprecatedClass and > DeprecatedProperties to deprecate these "older" classes and properties? > > > However, it is probably not the definitive answer for all cases. For > example, for the UMBEL ontology, I am thinking about proceeding that way > for the UMBEL vocabulary, but I am still not sure if it is the way to go > for future version of the instantiation files (the instantiation > (subject concepts structure) of umbel). -- Carl Mattocks Chair OASIS Business Centric Methodology TC co-Chair OASIS (ISO/TS 15000) ebXMLRegistry Semantic Content SC ONTOLOG ONION CoP Leader CEO CHECKMi vmail(usa) 908 322 8715 www.CHECKMi.com Semantically Savvy Agents
Received on Monday, 28 July 2008 17:11:37 UTC