[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Content Negotiation not enough for schemas (was Re: Namespace URI

• From: Dan Brickley <Daniel.Brickley@b...>
• To: 'XML Dev' <xml-dev@i...>
• Date: Thu, 17 Jun 1999 21:38:47 +0100 (BST)

On Fri, 18 Jun 1999, Rick Jelliffe wrote:
> In any case, the only resolution system currently around for URIs is
> content negotiation, which relies on all schemas being at the same
> location and being of different MIME types, as I understand it.
> What about when the schemas are on unrelated servers or use the
> same schema language or when you want the schemas available from
> local "file:" URLs?

for eg. a 'hub' server containing only data on the variant versions
could send HTTP 'moved temporarily/permenently' headers redirecting to 
other servers. Much like the purl.org system for general web
indirection. I'd need to check the HTTP/1.1 spec to see if redirects can
be w.r.t. particular variants of a resource, but this sounds
feasible in principle.

Dan


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
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@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• References:
  • Content Negotiation not enough for schemas (was Re: Namespace URI address resources)
    • From: "Rick Jelliffe" <ricko@a...>

• Prev by Date: What should the resource of a namespace URL be?
• Next by Date: Variables
• Previous by thread: Content Negotiation not enough for schemas (was Re: Namespace URI address resources)
• Next by thread: Another reason why namespaces URLs should not be schemas
• Index(es):
  • Date
  • Thread