- From: Clark, John <CLARKJ2@ccf.org>
- Date: Tue, 13 Feb 2007 14:57:41 -0500
- To: public-grddl-wg@w3.org
I worked my way through the normative sections of the GRDDL spec; the following are my comments on the most recent editor's draft. I believe this completes my action: [[ACTION: JohnL comments on spec]]. Comments on GRDDL editor's draft, version 1.208[4] ================================================== Note that the only major comments are with respect to section 3, below. The remainder are minor edits. 1. Introduction[0] ------------------ - "GRDDL provides a relatively inexpensive mechanism for bootstrapping RDF content from uniform XML dialects; shifting the burden from formulating RDF to creating transformation algorithms specifically for each dialect." -> "GRDDL provides a relatively inexpensive mechanism for bootstrapping RDF content from uniform XML dialects, shifting the burden from formulating RDF to creating transformation algorithms specifically for each dialect." Reason: connect dependent phrase, rather than independent phrase - "These use cases also illustrate how XML and XHTML documents can be decorated with microformat" -> "These use cases also illustrate how XML and XHTML documents can be decorated with microformats" Reason: typo fix 2. Adding GRDDL to well-formed XML[1] ------------------------------------- - "The glean_title.xsl resource specifies a function from XPath document nodes to RDF/XML documents, and hence to RDF graphs; This function is the property referred to as the transformation property of the XSLT document." -> "The glean_title.xsl resource specifies a function from XPath document nodes to RDF/XML documents, and hence to RDF graphs; this function is the property referred to as the transformation property of the XSLT document." Reason: capitalization fix Comment: I might say "this function is known as the transformation property" or "this function is called the transformation property", but YMMV. 3. Using GRDDL with XML Namespace Documents[2] ---------------------------------------------- - "To associate a GRDDL transformation with a whole dialect, have the namespace document include the grddl:namespaceTransformation property." -> "To associate a GRDDL transformation with a whole dialect, have the GRDDL result for the namespace document associate the grddl:namespaceTransformation property with the namespace resource." Reason: make clear the fact that the grddl:namespaceTransformation property is actually found in a GRDDL result for the namespace resource - "and an information resource IR has an XML representation with root node NODE and with a root element associated with a namespace name NS," -> "and an information resource IR has an XML representation with root node NODE and with a root element name with the namespace name NS," Reason: clarify the association between the namespace name and the root element - This section notes that "the result of parsing an RDF/XML document is a GRDDL result of that document". Is this a logical consequence of the preceding rule, or simply an assertion of the spec? I ask because the section calls it a "degenerate case", which seems to imply that it follows from the preceding rule, but I can't see how that might be the case. - The diagram "using GRDDL with an XML Schema" shows a solid "transformation" directional link from po-doc.xml to grokPO.xsl, which seems to indicate that po-doc.xml refers to this GRDDL transformation directly, but instead it gets this GRDDL transformation indirectly from GRDDL processing of the namespace document. - Would a document author ever want to explicitly turn off this feature, so as to prevent namespace transformations from being processed? - Subsection "Using GRDDL with an XML Schema namespace document" seems to give special status to XML Schema namespace documents, but shouldn't the specification clearly indicate that the same applies for any XML namespace document? 5. GRDDL for HTML Profiles[3] ----------------------------- - "Adding GRDDL profileTransformation assertion to a profile document" -> "Adding a GRDDL profileTransformation assertion to a profile document" [0] http://www.w3.org/2004/01/rdxh/spec#intro [1] http://www.w3.org/2004/01/rdxh/spec#grddl-xml [2] http://www.w3.org/2004/01/rdxh/spec#ns-bind [3] http://www.w3.org/2004/01/rdxh/spec#profile-bind [4] http://www.w3.org/2004/01/rdxh/spec Take care, John L. Clark | Systems Analyst | Cardio-Thoracic Surgery Research Cleveland Clinic | 9500 Euclid Ave. | Cleveland, OH 44195 | (216) 445-6011 =================================== Cleveland Clinic is ranked one of the top 3 hospitals in America by U.S.News & World Report. Visit us online at http://www.clevelandclinic.org for a complete listing of our services, staff and locations. Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you.
Received on Tuesday, 13 February 2007 19:58:05 UTC