W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > April 2007

p:catalog

From: Innovimax SARL <innovimax@gmail.com>
Date: Thu, 5 Apr 2007 17:58:27 +0200
Message-ID: <546c6c1c0704050858s2c40f280r23f6522fb5686bbd@mail.gmail.com>
To: "XProc WG" <public-xml-processing-model-wg@w3.org>

Dear,

The idea behind this is to provide a mechanism to overload in the
context of XProc the resolution of URI

So what is the difference with Catalog then ?

The big difference is that it have access to *two* more extensions :
* Access to inline document (which could be handy)
* Access to port without needing to serialize them


What are the use cases :
XSLT:import and XSLT:include
XInclude
File Entities (I hear some people screaming...but that's a *real* use case)
Schema:import and Schema:include and Schema:redefine

I think the idea is to scope that p:catalog the inner of what it is
defined (p:group, p:step, ...)

Any thought ?

Mohamed
-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 8 72 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Thursday, 5 April 2007 15:58:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:50 GMT