- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Wed, 09 Feb 2011 13:46:28 -0500
- To: W3C RDFa WG <public-rdfa-wg@w3.org>
On 02/09/11 13:08, Nathan wrote: >> RDF/RDFa Profiles >> ----------------- >> >> 1. There will be one dated RDF profile, which XML+RDFa will use: >> http://w3.org/2011/profiles/rdf >> 2. There will be one dated (X)HTML+RDFa profile: >> http://w3.org/2011/profiles/rdfa >> 3. The XML+RDF profile will be a sub-set of the (X)HTML+RDFa profile. > > RDF/XML or XML+RDFa ? Sorry, typo, I meant XML+RDFa. I was vague about non-RDFa languages such as RDF/XML on purpose. The new RDF WG may or may not support default profiles (probably not, but you never know). TURTLE or N3 could also support "default profiles" using http://w3.org/2011/profiles/rdf . The one thing I want to make sure that we do is leave the door open for those groups, but not accidentally make any sort of decision for them. >> 4. The XML+RDFa part of the RDFa Core 1.1 specification will >> reference http://w3.org/2011/profiles/rdf as the default profile. >> 5. The XHTML+RDFa 1.1 and HTML+RDFa 1.1 specifications will reference >> http://w3.org/2011/profiles/rdfa as the default profile. >> 6. Default profiles are allowed to be cached and hard-coded in >> implementations. > > but SHOULD be kept in sync with the "live" profile(s)? Yes, correct - we need to make sure to add that clarification. >> RDF/RDFa Profile Management >> --------------------------- >> >> 1. The profiles are modified on a consistent basis and do not >> change very often (perhaps once every 1-2 years). >> 2. Prefixes and terms are managed by the Semantic Web Activity Lead, >> who announces changes on some well-known mailing list prior to >> each re-publication. >> 3. Prefixes and terms MUST NOT be /removed/ from dated profiles. >> 4. Prefixes and terms MAY be /updated/ if the new meaning of the >> term or prefix is semantically backwards compatible with the >> previous term or prefix. >> 5. Vocabulary maintainers are strongly discouraged from re-using >> the same prefix for a new vocabulary performing the same purpose. >> For example, if a new non-semantically-backwards-compatible version >> of 'geo' is released, it SHOULD be named 'geo2' or 'geonext' (in >> other words, the prefix for the new vocabulary SHOULD NOT be 'geo'). > > clarification on whether new dated profiles will be released or not, and > if so what restrictions apply? New dated profiles will be released. These releases will almost always coincide with a revision of a language that uses them (such as when RDFa 2.0 is released, or when TURTLE is standardized, etc.). I don't think we need new restrictions, as the same restrictions that apply to other default profiles (as outlined in the proposal) would apply to these new profiles. -- manu -- Manu Sporny (skype: msporny, twitter: manusporny) President/CEO - Digital Bazaar, Inc. blog: Towards Universal Web Commerce http://digitalbazaar.com/2011/01/31/web-commerce/
Received on Wednesday, 9 February 2011 18:46:58 UTC