W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > January 2008

Re: Comments on the latest version of the syntax document

From: Ivan Herman <ivan@w3.org>
Date: Thu, 24 Jan 2008 13:59:29 +0100
Message-ID: <47988BB1.6080102@w3.org>
To: Mark Birbeck <mark.birbeck@x-port.net>
Cc: Shane McCarron <shane@aptest.com>, Ben Adida <ben@adida.net>, W3C RDFa task force <public-rdf-in-xhtml-tf@w3.org>


Mark Birbeck wrote:
> Hi Ivan,
> 
>> here are my comments on the latest version[1].
> 
> Many thanks...very useful comments.
>

You are welcome!

> 
> 
>> - Section 4.1: I am not sure I understand the 'Merge namespaces' issue
>> listed there, mainly in line with the latest description of the
>> @rel="next" value. Isn't that issue (if there was ever any) moot?
> 
> I'm saying that we currently have two URIs kicking around, one for the
> @profile attribute, and one for the XHTML vocabulary. My suggestion is
> that we don't need both. First, using a 'namespace' in @profile is
> counter to normal XHTML usage, so I just don't like that, anyway. I
> recognise that people want a value in @profile to indicate that 'this
> document contains RDFa', but that shouldn't be done at the expense of
> proper use of @profile.
> 
> I recognise, too, that some people want a value in @profile so that
> they can run a GRDDL transform. I did point out in other emails that
> GRDDL supports a number of mechanisms for hooking in a transform, and
> @profile is only one of them.
> 
> Anyway, my feeling is that if the document referred to by the URL used
> in @profile contained a definition of the new @rel/@rev values in
> XHTML+RDFa, then it would become a 'proper' use of @profile. It could
> of course also include the hook to GRDDL, and that would satisfy my
> desire to see us remain as consistent with 'ordinary' XHTML as
> possible.
> 
> But if we did that, surely we'd put those definitions into the
> document at "...vocab#", rather than in some RDFa namespace document?
> After all, what is the namespace document for anyway, since all of the
> new attributes belong to XHTML?
> 
> So that's my argument... :)
> 
> 

Let us not argue on the @profile issue:-) I guess what you want to say 
is that the URI used for the @profile should be the same as the one used 
for the @next values (ie, ....vocab#). The counterargument to that might 
be that '...vocab#' clearly refers to the XTHML values and the fact that 
these values are really defined by the XHTML group, whereas the current 
@profile value is independent. I know this is not a very strong argument.

Let the group decide on that. I wish this was the only major issue to be 
solved!:-)


>> - This is just a small remark, not really on the document but on one of
>> the semi-pending issue. The current text says:
>>
>> [[[
>> The [current subject]. The initial value will be the same as the initial
>> value of base, but it will usually change during the course of processing.
>> ]]]
>>
>> This, in fact, is indeed equivalent to the fact that the <html> element
>> has an implicit @about="" attribute set. (I note that because there was
>> a slight uncertainty about that in some of the discussion mails...)
> 
> Yes...I actually need to add more to this for other reasons too. I
> don't know if you saw my post the other day, but I realised that even
> if the URL for the document is:
> 
>   <http://www.w3.org/People/Ivan#me>
> 
> the *base URI* is actually:
> 
>   <http://www.w3.org/People/Ivan>
> 
> since 'absolute URIs' don't have fragment identifiers. I'm using the
> terminology from RFC 3986 very precisely, here, and since the meaning
> of 'absolute URI' runs slightly counter to what one might think it
> means in common parlance, I've removed all references to it from the
> document, and replaced it with 'full URI'.
> 
> 

Oops, I missed that one. Let us see what you will come up with:-)

Ivan



-- 

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


Received on Thursday, 24 January 2008 12:59:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 24 January 2008 12:59:41 GMT