- From: Danny Ayers <danny.ayers@gmail.com>
- Date: Tue, 13 Feb 2007 21:06:45 +0100
- To: public-grddl-wg <public-grddl-wg@w3.org>
I think this doc is ok to go forward, overall it works nicely. I'm in two minds about the Introduction, it does cross over into Primer territory, redundant when we have a Primer, but then again I guess it does no harm. Some editorial tweak suggestions below, the rest to follow soon. btw, I think the differences in style & wordcount between the different cases works rather well in offering different angles. ----- *** Abstract See recent modifications of spec & primer abstracts. *** Table of Contents The style of the titles isn't very consistent, described in separate mail. *** 1. Introduction: Data and Documents This doc is associated with the primer, so it'd be good to link to the RDF Primer, maybe at the end of the para beginning "The Resource Description Framework[RDFC04] provides..." http://www.w3.org/TR/rdf-primer/ [[ RDF includes an XML concrete syntax and an abstract model. Software tools that use the Resource Description Framework naturally work with documents whose data is encoded using RDF/XML. ]] => [[ RDF is based on an abstract model but includes an XML concrete syntax (RDF/XML). Software tools that use the Resource Description Framework can generally read data encoded as RDF/XML. ]] [[ GRDDL is a mechanism for Gleaning Resource Descriptions from Dialects of Languages; that is, for extracting RDF data from XML documents by way of transformation algorithms, typically represented in XSLT. ]] add [[ The results of the transformations will usually be RDF/XML documents, although other RDF syntaxes may be used. ]] [[ The following HTML and RDF excerpts illustrate the correspondence ]] maybe add little subtitles to separate the listings, HTML : <html... RDF/XML: <rdf:RDF... [[ The transformation algorithm used is expressed in an XSLT transformation, dc-extract.xsl. ]] => [[ The transformation algorithm to convert between the different formats can be specified using XSLT, in this case dc-extract.xsl. ]] *** Use case #1 - Scheduling : Jane is trying to coordinate a meeting. [[ Despite their different formats, the calendars of all four friends can be used as source documents ]] => [[ Despite their different formats, the calendars of all four friends can be used as GRDDL source documents ]] [[ These groups publish their calendars in various HTML-based formats: microformats, eRDF, RDFa, or some home-grown way to express calendar information. ]] => [[ These groups publish their calendars in various HTML-based formats: microformats, eRDF, RDFa, and other home-grown ways of expressing calendar information. ]] [[ The rendered XHTML+RDFa provides a copy- paste functionality via, right-clicking on an event right in the rendered XHTML+RDFa. ]] Not sure what the intent here is - can Jane's Personal Calendar read RDFa? Or maybe her GRDDL-enabled browser will give it her as iCalendar format? *** Use case #2: Health Care: Querying XML-based clinical data using a standard ontology First 3 paragraphs, minor tweaking could bring the motivation further up, maybe to: [[ Kayode, a developer for a clinical research data management system, uses XML as the main representation format for their computer-based patient record. He currently edits the XML remotely via forms, submits the XML document to a unique URI for each such record over HTTP. But elsewhere Kayode has found RDF queries useful for investigative querying. He wants to use a content management system which includes a mechanism to automatically replicate an XML document into equivalent, named RDF graphs for persistence in synchrony with any changes to the document. The expense of dual representation as single-purpose XML vocabulary and RDF includes space and synchrony problems, but the primary value is being able to query both as XML and as RDF. The corresponding XML documents can be transformed into other non-RDF formats, evaluated by XPath and XPointer expressions, cross-linked by XLink or XInclude, and structurally validated by RELAX NG (or XML Schema). With the RDF query facility he can ask speculative questions using standard healthcare ontologies for patient records, such as the HL7 OWL ontology. ]] [[ Kayode realizes a GRDDL approach alleviates this expense ]] => [[ Kayode realizes a GRDDL approach can alleviate the expense of maintaining a dual representation ]] *** Use case #3 - Aggregating data: Stephan wants a synthetic review before buying a guitar. (bit short, but I think ok) *** Use case #4 - Querying sites and digital libraries: DC4Plus Corp. wants to automate the publication of its electronic documents. (ok) *** Use case #5 - Wikis and e-learning: The Technical University of Marcilly decided to use wikis to foster knowledge exchanges between lecturers and students. The ref. link for "wikis" goes to the French Wikipedia - swap for English? I believe "learning objects" is well-known in the domain, but it would be good to have a reference link - http://en.wikipedia.org/wiki/Learning_Object -- http://dannyayers.com
Received on Tuesday, 13 February 2007 20:06:57 UTC