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

RE: Telecon Tuesday! 1500 UTC

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Tue, 22 Nov 2005 14:51:15 -0000
Message-ID: <0F15A396-06CF-4D4D-B5BC-66179978807D@s15.mail.x-port.net>
To: "'Ben Adida'" <ben@MIT.EDU>
Cc: "'public-rdf-in-xhtml task force'" <public-rdf-in-xhtml-tf@w3.org>

Hi Ben,

> Sorry for the late reminder, but let's still try to meet at 
> 1500 UTC, normal telecon.

I am going to have to send my apologies for this call. Sorry for the late
notice but I have to take a call a short time into the telecon.


> Agenda: review of the issues on our issues list 
> http://www.w3.org/2001/sw/BestPractices/HTML/2005-current-issues
> 
> We will start with some of the simpler issues: (13), (12), (9).

I'd still like to make some comments on the issues you plan to discuss, if
that's OK!


9: Make <link> content clickable
Looks convincing, Ben.

If you go this route, you might need to throw into the mix my suggestion
that any string value inside a <meta> element gets added automatically to
the triples as an RDFS label. And you might also need to add an automatic
@role value, of, say "xh2:a" (or 'navigable' might be better, since it could
go into the XHTML 2 'role list'). That way a processor making later use of
the triples stored could retrieve the link to Dostoevsky, work out that it
is a navigable link (as opposed to just being the object in a statement) and
then also find it had some text with which to label the 'link'.

(Note that this would result in 4 triples! The first is the reified one that
you wanted in the first place, and the remaining three involve an anonymous
node, and statements about the target URI, the fact that it's navigable, and
the rdfs:label.)


12: CURIEs in Predicates
I'd prefer not on this...I'm actually starting to be *against* this. My view
is increasingly that @href containing full URIs is the special case, i.e.,
from an RDF standpoint we deal predominantly with triples made up of CURIEs,
and it's only in XHTML 2 that *some* of the objects being referred to can be
navigated.

However...the problem remains one of consistency; if @about was CURIE only
then it would make it difficult for an author to make statements about URIs
that appear in @hrefs. So although I don't like it, I can't really see a way
out of making all the attributes URI/CURIE mixes.


13: Plain Literals
I'm not sure what the precedent is for what you are doing. I believe that in
RDF/XML you can either have the XML literal (and get the full mark-up) or a
string that contains the escaped version of the XML. I don't know how you
would get just the text.

So my suggestion for what you want would be this:

  <meta about="" property="dc:creator" content="Ben Adida"><b>B</b>en
<b>A</b>adida</meta>


I'll no doubt talk to you after the call about priorities and stuff, and
should be OK for next week.

Regards,

Mark


Mark Birbeck
CEO
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/

Download our XForms processor from
http://www.formsPlayer.com/
Received on Tuesday, 22 November 2005 14:52:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:15:00 GMT