[HTML] RDF-in-HTML Task Force Update to the SWBPD WG

Fellow Working Group Members,

Over the last few months, I've been unable to attend the SWBPD  
telecons, though Ralph has done a fantastic job filling in for me.  
Starting in October, I hope to attend more regularly. In the  
meantime, here is a long-overdue update on the Task Force.

If you're quickly skimming this, here are the actions where we could  
use help:

* Editors for DanBri's Note: we need you to help! See point (6).
* More participants in the Task Force: just join the mailing list and  
send me a quick email.
* Reviews of Use Cases: see points (4) and (5). If you want RDF-in- 
HTML to work for you, we need your input.
* We need help chairing the TF while I'm away for 6 weeks. See point  
(8).

==========

In general, the task force is making slow but noticeable progress. We  
have between 4 and 6 individuals at each task force telecon (weekly  
telecons on Tuesdays), with Mark and Steven from the HTML WG present  
almost every time and doing a significant portion of the work. The  
collaboration between the two WG is thus fairly good. Of course, we  
could use more help: if you have an interesting the RDF-in-HTML task  
force, now is the time to jump in and help.

Details:

1) we are no longer paying much attention to GRDDL. The last WG  
meeting consensus, the limited manpower, and the question regarding  
whether GRDDL falls within our scope have all contributed to this de- 
facto decision. The use of GRDDL in semantic web activities should  
probably be addressed in another task force at some point, but our  
task force is mostly not dealing with it anymore.

2) we are making good progress on RDF/A, the specification produced  
by Mark and Steven which now includes a number of this working  
group's suggestions and use cases. A recent version is available in  
the XHTML2's working draft from May:

http://www.w3.org/TR/2005/WD-xhtml2-20050527/

3) since this WD, more progress has been made: the next XHTML2 draft  
will include a normative reference to RDF. HTML authors will know  
that their usage of RDF/A directly implies a set of RDF triples.

4) we have just begun tracking our remaining issues at:
http://www.w3.org/2001/sw/BestPractices/HTML/2005-current-issues
(currenty, only a high-level description. More details will appear).

5) we are developing detailed examples of RDF/A vs. RDF/XML to ensure  
that attribute inheritance, reification, and bnodes are handled  
appropriately. The wiki for this is currently down, but the link that  
will surely come back up at some point is:

http://www.xforms-wiki.com/bin/view/Main/LanguageRdfA

6) DanBri has begun work on a WG Note that will specify the RDF  
schema for the default RDF relationships used for HTML backwards  
compatibility (e.g. rel="copyright", rel="first", etc...). He has  
emailed a link to his current draft:

http://www.w3.org/2005/05/hrel/

This should be fairly straight-forward to review, but it will be an  
important piece of the RDF/A puzzle.

7) We are considering a more complete RDF/A overview note to cover  
all the issues involve for those who wish to express RDF in their  
HTML. (That's the goal of our TF, after all!) Details on this will  
follow.

8) I will be absent for 6 weeks starting next week. I am recruiting  
help to continue chairing the task force. If you have time and  
interest to join the TF and help out with simple coordination (no  
tech insights needed), now's the time! Send me an email.

=========

That's it from RDF-in-HTML land,

-Ben Adida
ben@mit.edu

Received on Monday, 8 August 2005 14:43:44 UTC