Altova Mailing List Archives


Re: [xml-dev] Revised Internet-Draft: Media Feature - xmlns

From: "Rick Jelliffe" <ricko@-------.---.-->
To: <xml-dev@-----.---.--->
Date: 1/25/2002 2:23:00 AM
From: "Simon St.Laurent" <simonstl@s...>
 
> I'm also maintaining both an archive of these drafts and the currently
> open (unsubmitted) draft at:
> http://simonstl.com/ietf/

> Comments and suggestions are welcome.

Looks good. It still falls down for the same reason that the whole
"out-of-band signalling using MIME headers" falls down:
there needs to be some convention (other than by parsing
the whole document including subentities) for a webserver to 
construct the information in the first place. 

Is there value in constructing pipes when there are no
feasible connectors?   At the moment, the WWW basically
runs on 
  file extension -> MIME type -> type handler
We know that a document is xslt not because of its top-level
element but because it is .xsl or .xslt.

The obvious way to have access to namespace precis in
a document (saved as a file) is to bubble up all namespace
declarations to the top-level element.

But if we need to canonicalize our documents in this way
in order to have the namespace details in a convenient
place for a webserver to re-extract it, why not just
send the document like that in the first place, and let
the application decide how to handle it? 

It seems to me that "best practise" XML should include
having xmlns:* declarations for all namespaces used
in the document at the top level element, even if 
the namespaces are used by default declarations
within the document rather than the dummy prefixes
at the top-level.

Would it make processing and dispatching easier if
XML tools did this?

Cheers
Rick Jelliffe

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.