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

Re: c:data/@href idea

From: Alex Milowski <alex@milowski.com>
Date: Wed, 23 May 2012 10:46:09 -0700
Message-ID: <CABp3FNJq9dWsqNqcfWYpELj3UyvE+GJBE1HzQqny95NG=6kR0A@mail.gmail.com>
To: public-xml-processing-model-wg@w3.org
On Tue, May 22, 2012 at 6:12 PM, Norman Walsh <ndw@nwalsh.com> wrote:
> Alex Milowski <alex@milowski.com> writes:
>> I've been looking at one of the use cases and realize it would be
>> really, really nice if a step could output a reference:
>> <c:data href="math.png" content-type="image/png"/>
> I wonder how that will play with the ideas Vojtech had about
> handling multiple content types flowing through the pipeline.
>> That way p:store, etc. can return a standardized reference to a
>> resource created.
> But p:store already has a standard reference:
>  <c:result>math.png</c:result>

Hmm... I wouldn't call that a standard way to represent a link.

>> It may be the case that c:data is the wrong element to use for this
>> but it seems like it would be useful in some places where c:data is
>> used.
> Do you have in mind that, like base64 encoding, this would be
> "transparent" to the steps. That is that a step processing
>  <c:data href="test.xml" content-type="application/xml"/>
> would behave exactly as if test.xml had been provided "inline"
> (assuming test.xml exists and can be read, of course)?

I just want the URI + content type.  Other behaviors might be
warranted but that wasn't what I was expecting.

--Alex Milowski
"The excellence of grammar as a guide is proportional to the paucity of the
inflexions, i.e. to the degree of analysis effected by the language

Bertrand Russell in a footnote of Principles of Mathematics
Received on Wednesday, 23 May 2012 17:46:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:50 UTC