- From: Dan Connolly <connolly@w3.org>
- Date: Tue, 05 Sep 2006 09:46:14 -0500
- To: Ian Davis <ian.davis@talis.com>
- Cc: public-grddl-wg@w3.org
On Tue, 2006-09-05 at 11:29 +0100, Ian Davis wrote: > I have written a very early draft of the primer, starting with some > examples from the first use case. I think this completes my action to > consider the meeting scheduling use case. > > I've made it available here until we can move it into W3C space: > > http://research.talis.com/2006/grddl-wg/primer.html Cool... > Any suggestions for improvement gratefully received :) Rather than... | To make this document processable by a GRDDL-aware client let's say To explicitly relate the data in this document to the RDF data model, ... or To explicitly make the data in this document available in the Semantic Web ... Then... | First she needs to add a profile attribute to the head element | to denote that her document contains GRDDL metadata. What the profile attribute does is ground the term transformation (as in rel="transformation") in URI space. I think it's better to introduce the link first, then ground the link relationship in URI space. Also... I wonder if it's exemplary to include the .xsl in <link rel="transformation" href="http://www.w3.org/2002/12/cal/glean-hcal.xsl"/> it's sort of more concrete and explicit, which is sometimes good in a primer. But I'd rather leave the .xsl off in this case. Hmm... another case of "GRDDL-aware client"... | A GRDDL-aware client encountering David's page can fetch the | Embedded RDF profile URI to obtain the following profile document How about Anyone interested to get the data out of David's page can fetch... -- Dan Connolly, W3C http://www.w3.org/People/Connolly/ D3C2 887B 0F92 6005 C541 0875 0F91 96DE 6E52 C29E
Received on Tuesday, 5 September 2006 15:16:12 UTC