- From: Dan Connolly <connolly@w3.org>
- Date: Thu, 30 Nov 2006 09:29:57 -0600
- To: Chimezie Ogbuji <ogbujic@bio.ri.ccf.org>
- Cc: GRDDL Working Group <public-grddl-wg@w3.org>
On Thu, 2006-11-30 at 09:47 -0500, Chimezie Ogbuji wrote: > On Thu, 30 Nov 2006, McBride, Brian wrote: > > > A GRDDL transform transforms a document to a graph. Transform authors > > typically transform a document to a serialization of graph. > > > > Conceptually what is typically happening is in two stages: > > > > 1. Transform the document to a serialization of the graph > > 2. Parse that serialization > > > > Parsing occurs in a context, e.g. same document references and base URI > > (I can't think of any others off the top of my head, but their might be > > some). > > > > Should the spec spell out that context so that transform authors know > > what they can rely on? > > I believe the reason why we moved away from language about parsing or > concrete syntaxes (someone plz correct me if I'm wrong) was to move away > from having a closed list of supported serialization syntaxes. Yes, so this sort of detail is out of scope for the main body of the spec. It is in scope, meanwhile, for the sample implementation appendix. I added (in 1.169) a TODO to consider it. http://www.w3.org/2004/01/rdxh/spec#implExp > Saying > that a 'graph' comes out implies a > concrete (and valid) syntax and a successful parse. The syntax coming out > and the base URI would constitute the context for the parsing. -- Dan Connolly, W3C http://www.w3.org/People/Connolly/ D3C2 887B 0F92 6005 C541 0875 0F91 96DE 6E52 C29E
Received on Thursday, 30 November 2006 15:30:12 UTC