> I probably haven't had enough coffee, but I think that changing the > namespace will break stuff that is using it now regardless, right?
Yes > If backward compatibility will be broken anyways, adding a bit of > semantics that lets you track compatibility seems a Good Idea. But I > don't feel super strong about it. > > FWIW, you don't change the namespace version unless the schema > changes-- it is not linked to version of the software, but to the > version of the schema (and probably only bump it if there were > breaking changes, unless one wants to go whole hog dependency > management). The W3C uses dates to demonstrate that there is no "minor" version change - any change in version completely changes the semantics of the document. For instance, here is the RDF namespace: http://www.w3.org/1999/02/22-rdf-syntax-ns# The # has a somewhat special meaning in RDF, so we shouldn't bother with using it. So maybe urn:X-opencast:engage/2012/09/26 Chris -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
