1 / 12

Enabling Unambiguous GRDDL Results

This presentation explores the issue of ambiguity in GRDDL transformation results and proposes solutions to ensure clarity and accuracy in XML document serialization. It discusses potential sources of unwanted ambiguity and presents two proposals for addressing the problem. The document emphasizes the importance of enabling transformation authors to be unambiguous if desired and highlights the distinctions between desired and undesired ambiguity. Moreover, it discusses the implications of proposed changes and suggests leaving the door open for further clarification on "Complete GRDDL Results."

polk
Download Presentation

Enabling Unambiguous GRDDL Results

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enabling Unambiguous GRDDL Results David Booth <dbooth@hp.com>Presentation to GRDDL Working Group, 20-June-2007This document: http://dbooth.org/2007/grddl/ambiguity.ppt

  2. What this issue is about • Given an XML document, what RDF did the GRDDL transformation author intend to denote? • Document receiver needs to be able to determine precisely what graph the XML document was intended to denote • Critical when XML document is a serialization of RDF • GRDDL transformation says how to deserialize

  3. What this issue is NOT about • NOT about desired ambiguity • Transformation author may intend variable results • Can be useful sometimes -- a feature, not a bug • NOT about eliminating ambiguity that the transformation author is willing to accept • NOT about forcing the transformation author to be unambiguous • NOT about requiring the GRDDL-aware agent to actually produce the transformation author's intended results • Users may not need them all, for example • This is only about giving the transformation author the ability to be unambiguous if desired

  4. Kinds of unwanted ambiguity • 1. Wrong results. Results contain different triples than intended. • Source of problem: ambiguous parsing/pre-processing • Proposed solutions: • Proposal 1b part 1, or • Proposal 2b part 1 • 2. Subsetting. User unknowingly gets a proper subset of the intended results, while believing that he/she got all of them. • Source of problem: Lack of a definition of "complete GRDDL results" • Proposed solution: WG Note • Proposal 1b parts 2, 3 & 4

  5. Proposal 1b part 1: Partial solution • Proposal: Change input of GRDDL transformation from XPath node tree to representation • Observations: • Reduces unwanted ambiguity problem • Permits transformation author to reduce variability in the "transformation application" step • Simple normative change • No changes to test cases

  6. Proposal 2b part 1: Better solution • Proposal: • Change input of GRDDL transformation from XPath node tree to representation; and • Specify that parsing is minimal, non-validating/me wn/ • Observations: • Reduces unwanted ambiguity problem • Permits transformation author to reduce variability in the "transformation application" step • Simple normative change • No changes to test cases

  7. Leaving the door open to a WG Note on "Complete GRDDL Results" • Note could define "complete GRDDL results" • Based on existing sec. 7 algorithm • Not required to be implemented • Not on our critical path - could be done anytime before the WG closes

  8. Proposed changes to leave the door open on such a Note • a. Add one sentence to Faithful Renditions. • b. Add non-committal mention of possible WG Note.

  9. BACKUP SLIDES

  10. XMLDoc RDF XPathnodetree Variability in results -- current spec Transformation Determination Transformation Application GRDDLTransf. Select Representation Parse XSLT/other

  11. XMLDoc RDF XPathnodetree Proposal 1b: Partial solution • Reduces problem in "transformation application" step • But not in "transformation determination" step Transformation Determination Transformation Application GRDDLTransf. Select Representation Parse XSLT/other

  12. XMLDoc RDF XPathnodetree Proposal 2b: Full(?) solution • Limits parsing to minimum, non-validating Transformation Determination Transformation Application GRDDLTransf. Select Representation Parse XSLT/other

More Related