- From: Shane McCarron <shane@aptest.com>
- Date: Tue, 01 Mar 2011 14:22:37 -0600
- To: Manu Sporny <msporny@digitalbazaar.com>
- CC: RDFa WG <public-rdfa-wg@w3.org>, Harry Halpin <hhalpin@w3.org>
- Message-ID: <4D6D558D.70302@aptest.com>
Sorry to continue on this thread, but... in RDFa Core we say: > The Host Language /may/ define a default RDFa Profile. If it does, the > RDFa Profile triples that establish term or URI mappings associated > with that profile /must not/ change without changing the profile URI. > RDFa Processors /may/ embed, cache, or retrieve the RDFa Profile > triples associated with that profile. We do not say 'the host language may define a bunch of profiles and require they all be read in a certain order'. Is that what we want to say? I have to say that I really hate that. On 2/28/2011 4:13 PM, Manu Sporny wrote: > On 02/28/11 13:07, Ivan Herman wrote: >> Just for my understanding: what this means is that what I said >> remains true at least for XHTML: >> >> - the XHTML default profile does not (necessarily) include the >> content of the RDFa+XML default profile - in the case of XHTML, an >> implementation has to load both of them (conceptually) and has to >> reconcile the prefixes and terms. > Correct. > >> The difference you seem to stress is that a particular host language >> has the possibility to declare that it does _not_ want to get the >> RDFa+XML default profile to be loaded prior to its own profile. > Yes. > > -- manu > -- Shane P. McCarron Phone: +1 763 786-8160 x120 Managing Director Fax: +1 763 786-8180 ApTest Minnesota Inet: shane@aptest.com
Received on Tuesday, 1 March 2011 20:23:17 UTC