- From: Harry Halpin <hhalpin@ibiblio.org>
- Date: Fri, 18 Aug 2006 14:44:11 +0100
- To: public-grddl-wg@w3.org
I agree with Fabien. The three documents have three different audiences: 1) GRDDL Primer/Tutorial: People who want a quick and easy to use guide to how to GRDDL-enable their web-page, and what neat capabilities this provides them. 2) GRDDL Use Cases/Scenario Gallery: People interested in different domains the technology can use, i.e. advocacy and spreading excitement. There should be a diversity of specific domains (e-learning, healthcare, e-business) combined with applications to specific technologies (from XML Schema to XForms to Wikis..) 3) GRDDL Specification: Implementers, and dealing with all the "edge-cases" of the technical details. Our charter specifically mentions RDF/A. embedded RDF, XML Schema, and microformats. And we need a fairly comprehensive set of examples and transforms, but we can't guarantee or "standardize" our transforms as that is out of scope. However, our examples and test suite should work, and to the extent they work people using GRDDL may adopt our transforms. cheers, harry Fabien Gandon wrote: > > Hi Dan et al., > > I agree with the charter on the fact that a tutorial/primer would be > useful, however I am not sure having the tutorial/primer and the use > cases in the same document is a good thing. > I know people who might be interested in reading a use case document > to understand what GRDDL could do for them and to take strategic > decisions. > And vice-versa I know people who are convinced they can use GRDDL and > just want a quick way to start playing with it. > > IMO these should be two separate documents. > > My 2 euro cents, > > Fabien. > -- Harry Halpin, University of Edinburgh http://www.ibiblio.org/hhalpin 6B522426
Received on Friday, 18 August 2006 13:44:21 UTC