Namespace URI address resources

[Chris Tilt]

We built a resolver that worked exactly like this, which returned
a manifested resource based on the accept field from the client. It
worked pretty well by placing the mime types in order of most to
least desired. The client got back a URL, or a URL list (depending
on the request) and could select one of them to fetch.

This was built for a content management system that handled many
kinds of media including broadcast video, audio, and multiple
document types. It worked quite well; the hardest problem was
getting the java classes to allow setting of the "accept" field!

Cheers, Chris

Tim Bray wrote:
> 
> At 02:25 PM 6/14/99 -0400, Murray Maloney wrote:
>[deleted]
> >I am suggesting that a schema-aware processor is allowed to resolve
> >the URI to an XML Schema, if possible, and use that schema to
> >inform its processing.
> [deleted]
> In an ideal world, one might imagine that content-negotiation could
> be helpful here - i.e. do a get on the URI and say that you only
> accept text/xml-sox or some such... but I'm not convinced that media-types
> are up to handling this job. -Tim
>

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)