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

RE: Agenda for Telecon 2004-10-22

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Fri, 22 Oct 2004 11:47:08 +0100
To: "'Ben Adida'" <ben@mit.edu>
Cc: "'public-rdf-in-xhtml task force''" <public-rdf-in-xhtml-tf@w3.org>, "'Steven Pemberton'" <Steven.Pemberton@cwi.nl>
Message-ID: <010801c4b824$7edaabd0$6701a8c0@W100>

Hello all,

Many apologies but I will be travelling at just the wrong time today (well,
the right time for me ...).

However, I thought it worth jotting down a few notes on which we would like
feedback, which hopefully will supplement your own comments:

1. We've added nodeID to address [1], but are there any better names?

2. Is everyone OK with the XPointer solution to finding anonymous nodes?

3. There may still be a few 'holes' in the processing section -- it needs
one more pass through since reverting to @href as a response to [2]. But if
I quickly explain the 'approach' it might help clarify what are real errors
and what are things just waiting to be brought into line.

The 'model' we've worked to is actually that of XML events. With that you
can only do two things -- you can specify an event observer for a node that
is at some other place in the document, or you can 'attach' an event
observer to an element by making the observer a child of the element. The
first use-case requires that an observer attribute is set with an IDREF,
whilst the second is what happens if no attribute is present.

As RDF/A evolved we played around with many sets of rules, including
scanning all parents of your node to find a default subject if one was
missing on the current node, and so on. However, we ended up with the
current syntax, which we think is easier to understand.

Although this is not mentioned in the RDF/A draft, the consequence of this
is that in XHTML 2 the head and body elements will have a default value for
@about of 'this document'. We'd like to know your thoughts on whether this
value should be "#" (am I being nineties again Dan? ;)) or just empty?

This means you can do stuff like this:

  <html>
    <head>
      <meta property="dc:creator">Fred</meta>
    </head>
    <body>
      <a rel="dc:creator" href="http://example.com/joe/" />
    </body>
  <html>

and get what one would expect.

Obviously, if these same elements appeared at some further level of nesting
(such as inside a div) then the result could be anonymous nodes as defined
in RDF/A.



I hope this helps, and we look forward to your comments -- and once again
sorry for not being there!

Regards,

Mark


[1]
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2004Sep/0019.html
[2]
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2004Sep/0017.html


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/

> -----Original Message-----
> From: public-rdf-in-xhtml-tf-request@w3.org 
> [mailto:public-rdf-in-xhtml-tf-request@w3.org] On Behalf Of Ben Adida
> Sent: 21 October 2004 21:36
> To: 'public-rdf-in-xhtml task force''
> Subject: Agenda for Telecon 2004-10-22
> 
> 
> 
> 
> Hi all,
> 
> Here's our agenda: 
> http://w3.org/2001/sw/BestPractices/HTML/agenda-2004-10-22
> 
> All the referenced documents have been sent to the list 
> before. If you 
> haven't had a chance to review them, please look them over!
> 
> Talk to you tomorrow,
> 
> -Ben
> 
> 
> 
Received on Friday, 22 October 2004 10:47:37 GMT

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