- From: Dan Connolly <connolly@w3.org>
- Date: Tue, 19 Sep 2006 15:51:46 -0500
- To: Fabien Gandon <Fabien.Gandon@sophia.inria.fr>
- Cc: Ian Davis <ian.davis@talis.com>, public-grddl-wg@w3.org
- Message-Id: <1158699106.5616.194.camel@dirk>
On Sat, 2006-09-09 at 17:51 +0200, Fabien Gandon wrote: > Hello, > > I reviewed the document as it was the 9th of September 2006 at 14:00Z > http://research.talis.com/2006/grddl-wg/primer.html [...] > "TODO: pretty diagram of this process" > Here is a proposal of a schema reusing the graphical charter of the use case > http://www-sop.inria.fr/acacia/personnel/Fabien.Gandon/tmp/grddl/hCalendar.png Can you share the source of those diagrams so that other WG members could make edits? That diagram has nice-looking icons, but I don't like the procedural aspect of it; it seems to say "first you have to find the profile, then you fetch, then..." whereas you might have the profile already in cache from working on an earlier document. The GRDDL draft uses data flow diagrams. http://www.w3.org/2004/01/rdxh/spec I tried making some for this case, but I guess they're not much of an improvement. Attached find what I've got so far, fighCalendar.svg . By the way, the source of those diagrams is N3, from which I derive .dot, .svg, and .png... ~/w3ccvs/WWW/2004/01/rdxh$ make fighCalendar python ../../../2000/10/swap/cwm.py fighCalendar.n3 txformDiagram.n3 --think --data --rdf=br --base=bogus: --bySubject > fighCalendar.xgraph xsltproc --novalid ../../../2001/02pd/rdf2dot.xsl fighCalendar.xgraph >fighCalendar.dot dot -Tsvg <fighCalendar.dot >fighCalendar.svg dot -Tpng <fighCalendar.dot >fighCalendar.png (and you need the current version of cwm has a bug in its --rdf=br support; I had to update -D2004/08/08 to get it to work.) The source of fighCalendar.n3 looks like: ---8<--- @prefix d: <http://www.w3.org/2003/g/data-view#>. @prefix : <figMultiTxform#>. @prefix s: <http://www.w3.org/2000/01/rdf-schema#>. @prefix owl: <http://www.w3.org/2002/07/owl#>. @keywords is, of, a. <http://research.talis.com/2006/grddl-wg/robin-hcal-grddl.html> d:transformation <http://www.w3.org/2002/12/cal/glean-hcal>. @prefix g: <http://www.w3.org/2001/02pd/gv#>. <http://research.talis.com/2006/grddl-wg/robin-hcal-grddl.html> g:label "XHTML +\\nhCalendar". <http://www.w3.org/2002/12/cal/glean-hcal> g:label "<glean-hcal> stylesheet". ---8<--- > First sentence of "Referencing Via Profile Documents" > "Another way to associate GRDDL instructions with an [XHTML Document] (...)" > Second sentence "(...) requires that the profile document [contains] > GRDDL (...)" > > Next to last paragraph: "(...) it expects that the [instructions] > identified by (...)" > > Also, here is a possible schema for this section: > http://www-sop.inria.fr/acacia/personnel/Fabien.Gandon/tmp/grddl/embeddedRDF.png How about 2 figures for that one, to show the recursion? (1) a figure showing how to get, from the profile document, the RDF statement: <http://purl.org/NET/erdf/profile> grddl:profileTransformation <http://purl.org/NET/erdf/extract-rdf> . and (2) a diagram starting with david-erdf.html , finding the erdf profile, and getting the calendar data out, pretty much like the existing diagram. -- Dan Connolly, W3C http://www.w3.org/People/Connolly/ D3C2 887B 0F92 6005 C541 0875 0F91 96DE 6E52 C29E
Attachments
- image/svg+xml attachment: fighCalendar.svg
Received on Tuesday, 19 September 2006 20:54:07 UTC