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

Re: Caching

From: Innovimax SARL <innovimax@gmail.com>
Date: Tue, 3 Apr 2007 08:18:53 +0200
Message-ID: <546c6c1c0704022318q6de66a55saee22f88eabb0189@mail.gmail.com>
To: "Norman Walsh" <Norman.Walsh@sun.com>
Cc: public-xml-processing-model-wg@w3.org

Dear,

Fine so for this special purpose, I propose to add a p:map-ports

map-ports = element p:map-ports { p:port+ }
port = element p:port { attribute base-uri { xsd:anyURI }, (p:pipe |
p:document | p:inline) }

I know it is a strong requirement, but I want to start discussion to
see where are the acceptable limits for every one

The idea behind it to give to the component a mapping it could use for
its URIResolver to link to accessible content that could be defined in
the pipeline. The reason why, I let p:document and p:inline is that it
could be useful to have such a way to make XProc aware of what could
be in use.

Any thoughts ?

Mohamed

On 4/2/07, Norman Walsh <Norman.Walsh@sun.com> wrote:
> / Innovimax SARL <innovimax@gmail.com> was heard to say:
> |> | The other one caching of URIReference that says when you overload the
> |> | URIResolver you can reroute the resolution to something in the pipe or
> |> | outside
> [...]
> | Ok ! Fine ! So what is the scope of "caching" in this thread ?
>
> The ability for a step to refer, by URI, to the output of some
> preceding step irrespective of whether or not its been serialized.
>
>                                         Be seeing you,
>                                           norm
>
> --
> Norman Walsh
> XML Standards Architect
> Sun Microsystems, Inc.
>
>


-- 
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 Tuesday, 3 April 2007 06:19:01 GMT

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