W3C home > Mailing lists > Public > public-xmlhypermedia@w3.org > August 2012

Re: use cases

From: mca <mca@amundsen.com>
Date: Mon, 20 Aug 2012 02:53:04 -0400
Message-ID: <CAPW_8m6=mu8GyWo1YA+8qb_-aAy5EnARQ7u1pZw-8sJASEO15A@mail.gmail.com>
To: liam@w3.org
Cc: "Rushforth, Peter" <Peter.Rushforth@nrcan-rncan.gc.ca>, David Carlisle <davidc@nag.co.uk>, "public-xmlhypermedia@w3.org" <public-xmlhypermedia@w3.org>
<snip>
Registering a new MIME media type is a lot of work.
</snip>
registering w/ IANA (esp. via vnd.*) is not work at all. and it's the first
step anyway.

elevating to standards-level is a diff kettle of fish (usually involving
either W3C, IETF, OASIS). What we're doing here is much of that initial
legwork, too.


mca
+1.859.757.1449
skype: mca.amundsen
http://amundsen.com/blog/
http://twitter.com/mamund
https://github.com/mamund
http://www.linkedin.com/in/mikeamundsen




On Sun, Aug 19, 2012 at 10:06 PM, Liam R E Quin <liam@w3.org> wrote:

> On Mon, 2012-08-20 at 00:37 +0000, Rushforth, Peter wrote:
> > Liam,
> >
> > If the information in an unobtrusive namespaces file can be
> > retrieved/created by xslt from an xml+namespaces document, should it
> > not be reasonably possible that the result of processing a
> > namespace-free document + a unobtrusive namespace file be equivalent
> > to the result of an xml processor processing the equivalent xml
> > +namespaces document ie effectively no data model differences?
>
> Yes, that's the idea at least :)
>
> >
> > In any case it might be a pain to have to deal with two files instead
> > of one in the general case,
> >  but where a media type has been defined, as I was trying to
> > illustrate with "neoxml", it could be a matter of the appropriate
> > unobtrusive namespaces file being fixed by the the specification of
> > the media type, and provided when necessary and appropriate via
> > content negotiation on the specification URI for
> > application/namespaces+xml.
>
> I'd tie it to an (XML vocabulary + application) combination probably -
> by far the majority of XML vocabularies just use application/xml and I
> don't expect that to change. Registering a new MIME media type is a lot
> of work.
>
> Liam
>
> --
> Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
> Pictures from old books: http://fromoldbooks.org/
> Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
>
>
>
Received on Monday, 20 August 2012 06:53:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 20 August 2012 06:53:52 GMT