Distinct issue-base-param components

For bookmarking sake (and to help me track the concerns), this is an
attempt to break out the distinct aspects of the Base URI discussion

== GRDDL Source Documents ==

Where by GRDDL source documents, I mean the documents which correspond
to source against which the normative XPath statements are applied.
There is an issue of XPath not supporting XML Base mechanisms.  We can
introduce a notion of a Base URI which is 'top-level' only but follows
XML Base in how it is determined (at least with the starting point being
the assumption that there is no notion of a base 'inside'

== GRDDL Transform Source Documents ==

XSLT 1.0 is our 'first-class' GRDDL transform and (by virtue of
depending only on XPath) also has limitations on XML Base resolution.
However, it introduces a 'top-level' notion of the base URI of the
document entity which can be passed in to the API and is often assumed
to be the URI used to retrieve the source document.

== Resolution of Empty URI References in GRDDL Result RDF/XML ==

If the GRDDL transforms do not output the RDF concrete syntax with the
Base URI information embedded, then GRDDL itself needs to provide a
consistent Base URI (as the external context).  It would seem to follow
that the (default) Base URI in this case should the same as the Base URI
of the GRDDL Source Document (as determined by XML Base)

Though issue-base-param was 'spawned' by conversations on the second
category, the tests which was committed (and the corresponding
resolution) had more to do with the third category.

-- 
Chimezie Ogbuji
Lead Systems Analyst
Thoracic and Cardiovascular Surgery
Cleveland Clinic Foundation
9500 Euclid Avenue/ W26
Cleveland, Ohio 44195
Office: (216)444-8593
ogbujic@ccf.org






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 Wednesday, 18 April 2007 15:01:33 UTC