xmldb-org-general

[Xmldb-org-general] XAPI and XInclude

[Travis S. <Tra...@no...>]

I would like to address the relationship of the XAPI with the 
Xinclude[1] specification.  XInclude is a specification for merging XML 
documents.  The basic example is including an XML document at a given URL.

<?xml version='1.0'?>
<document xmlns:xi="http://www.w3.org/2001/XInclude">
  <p>120 Mz is adequate for an average home user.</p>
  <xi:include href="disclaimer.xml"/>
</document>

One should be able to specify a resource in an XML:DB database in a 
standard way.   A simple idea would be to reference the resource by ID:
<xi:include 
href="xmldb:vendorx://db.xmlmovies.com:2030/movies?resourceId=5" />.  
Should xpath and xquery also be allowed as part of the URI?

Of course the XML parser would have to know how to handle the 
xmldb:vendorx protocol, but that is a different issue.  Also, 
standardizing the relationship to XInclude would be orthogonal to 
standardizing a possible REST syntax.

Any thoughts?

-Trav

[1] http://www.w3.org/TR/xinclude/

Re: [Xmldb-org-general] XAPI and XInclude

[Per N. <per...@us...>]

Hi Travis,

onsdagen den 16 mars 2005 18.26 skrev Travis Stevens:
> I would like to address the relationship of the XAPI with the
> Xinclude[1] specification.  XInclude is a specification for merging XML
> documents.  The basic example is including an XML document at a given URL.
>
> <?xml version='1.0'?>
> <document xmlns:xi="http://www.w3.org/2001/XInclude">
>   <p>120 Mz is adequate for an average home user.</p>
>   <xi:include href="disclaimer.xml"/>
> </document>
>
> One should be able to specify a resource in an XML:DB database in a
> standard way.   A simple idea would be to reference the resource by ID:
> <xi:include
> href="xmldb:vendorx://db.xmlmovies.com:2030/movies?resourceId=5" />.

Looks good to me.

> Should xpath and xquery also be allowed as part of the URI?

XQuery is not yet fully integrated in the API. I did an intial attempt heavily 
inspired by the eXists implementaiton but there is no reference 
implementation yet and the whole thing needs some refinement before it is 
ready. I think we need to finalize how XQuery works with the API before 
extending your basic idea of referencing a' la xinclude to also include 
xquery. I see nothing bad with allowing xpath expressions as part of the URI 
though.

Best regards,
Per

>
> Of course the XML parser would have to know how to handle the
> xmldb:vendorx protocol, but that is a different issue.  Also,
> standardizing the relationship to XInclude would be orthogonal to
> standardizing a possible REST syntax.
>
> Any thoughts?
>
> -Trav
>
> [1] http://www.w3.org/TR/xinclude/
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Xmldb-org-general mailing list
> Xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmldb-org-general

Re: [Xmldb-org-general] XAPI and XInclude

[Ronald B. <rpb...@rp...>]

Finally had time to read this...

Per Nyfelt wrote:

> Hi Travis,
> 
> onsdagen den 16 mars 2005 18.26 skrev Travis Stevens:
> 
>>I would like to address the relationship of the XAPI with the
>>Xinclude[1] specification.  XInclude is a specification for merging XML
>>documents.  The basic example is including an XML document at a given URL.
>>
>><?xml version='1.0'?>
>><document xmlns:xi="http://www.w3.org/2001/XInclude">
>>  <p>120 Mz is adequate for an average home user.</p>
>>  <xi:include href="disclaimer.xml"/>
>></document>
>>
>>One should be able to specify a resource in an XML:DB database in a
>>standard way.   A simple idea would be to reference the resource by ID:
>><xi:include
>>href="xmldb:vendorx://db.xmlmovies.com:2030/movies?resourceId=5" />.
> 
> 
> Looks good to me.

+1

>>Should xpath and xquery also be allowed as part of the URI?
> 
> 
> XQuery is not yet fully integrated in the API. I did an intial attempt heavily 
> inspired by the eXists implementaiton but there is no reference 
> implementation yet and the whole thing needs some refinement before it is 
> ready. I think we need to finalize how XQuery works with the API before 
> extending your basic idea of referencing a' la xinclude to also include 
> xquery. I see nothing bad with allowing xpath expressions as part of the URI 
> though.

I'm less sure of this. XInclude already allows XPointer addressing into 
the included document, so XPath/XQuery seems a bit too much. It might 
make more sense to have a URI-based version of XAPI, which would then 
use XQuery or XPath. This could then be used in an XInclude statement.

-- Ron