W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > August 2010

Re: How are default profiles normatively established?

From: Ivan Herman <ivan@w3.org>
Date: Tue, 24 Aug 2010 09:45:58 +0200
Cc: public-rdfa-wg@w3.org
Message-Id: <5C35B616-5374-498A-A6AB-83906C21C437@w3.org>
To: Richard Cyganiak <richard@cyganiak.de>

On Aug 23, 2010, at 14:08 , Richard Cyganiak wrote:

> I can't quite tell what the model for default profiles is.
> 
> Is it essentially a normative external profile document that is in effect for the entire document tree?
> 

That is my understanding...

> Or is it essentially a set of mappings that are normatively defined in the host language's specification document, and SHOULD also be available in an informative profile document, purely for consistency?
> 

*Conceptually* the answer is (in my view) the previous, ie, default term settings for a host language does not require any new/different mechanism from what we already have. In practice, of course, implementations may hardwire the default profile content in their parsing because there is also a note somewhere in the text that default profile specifications are not supposed to change, ie, processors are advised to cache them somehow. (Sorry not to refer to a particular place, I have a very bad connection today due to some networking change at my home.)

Whether a host language specification documents the content of the default profile becomes an editorial issue.

> Sections 7.5 makes it sound like the former, 7.2 makes it sound like the latter.
> 
> This matters for a few corner cases:
> 
> - What happens if the default profile document is unavailable due to server outage?
> 

If the caching mechanism works the processor should be able to go on happily...

> - Is the default profile in effect while processing *another profile document*?
> 

I think the answer is a clear no. Any effect of profiling is local to the document that refers to it; any profile document is an RDF(a) document on its own right, completely independent of the caller. Ie, I may process an SVG document with RDFa, using a default SVG profile for the SVG part, but referring to an external profile document in XHTML+RDFa. Clearly, the SVG default profile should have no effect on the XHTML+RDFa one.

I would think that is already clear from the document *if* the default profile is just a profile, ie, does not rely on any extra mechanism.

> I submit that the confusion has two sources:
> 
> 1. The terms “RDFa Profile” and “RDFa Profile Document” are used interchangeably, making it unclear what a “Default RDFa Profile” is. (My intuition is that a profile is an abstract data structure, while a profile document is a way of establishing a profile.)
> 
> 2. The section that explains RDFa Profile Documents does not explain how these documents relate to default profiles. (I think it should state that host languages SHOULD provide a profile document for their default profile, but that the profile document is never used in parsing.)
> 

Something like that is probably necessary, you're right.

Ivan


> Best,
> Richard


----
Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
PGP Key: http://www.ivan-herman.net/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf







Received on Tuesday, 24 August 2010 07:44:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:55:07 GMT