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

Just require URLs

• From: "Carl Hage" <carl@c...>
• To: xml-dev@i...
• Date: Mon, 31 May 1999 10:04:23 -0800

From:           	"Jonathan Borden" <jborden@m...>

> Paul Hunter wrote:
> > Using HTTP for URIs sounds intrinsically <em>bad</em> to me.  ...
...
> No one has offered a hard or
> practical example of an actual problem this creates, aside from offending
> of the sensibilities.

Turn it around-- it would be intrinsically <em>good</em> to require
all namespaces to reference a retrievable document. Any existing 
namespace registry can be mapped into a backwards compatible 
HTTP URL, returning something, e.g. http://isbn.org/isbn/1-57595-
180-0B could return the USMARC data (card catalog) formatted in 
HTML with a link to an XML representation. It serves as a URI as 
well as a source of documentation.

Software that maps hytime namespaces can just as easily map 
http://hytime.org/ namespaces, and software that knows nothing of 
hytime namespaces could follow a URL to find needed info. (Maybe 
manually, but better than nothing.)

I think the URI identifying namespaces and DTDs should be URLs 
not URNs. An XML document without retrievable documentation on 
the DTD should be considered non-compliant. The biggest problem 
isn't syntax-- it's the semantics. XML validators based on DTDs will 
only identify an insignificant percentage of errors-- hardly worth it if 
you ask me unless debugging software. (Though considering how 
Microsoft and Netscape callously violate HTML standards, I may 
need to recant.)

Likewise, a DTD->HTML converter doesn't produce human readable 
documentation, because the most important part (semantics) is 
missing.

If you ask me, XML will really work only when XML-Schema (or 
whatever) is enhanced to include human-readable detailed 
documentation (with all code-values defined in an XML thesaurus),
and the URIs in XML/DTD headers lead to a retreivable version of 
this. Putting the semantics and code-value definitions in separate 
paper documents (the norm today) must be abandoned. Instead 
everything needed should be accessable at the other end of the 
namespace URL.



--------------------------------------------------------------------------
Carl Hage                                              C. Hage Associates
<mailto:carl@c...> Voice/Fax: 1-408-244-8410      1180 Reed Ave #51
<http://www.chage.com/chage/>                          Sunnyvale, CA 94086

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...)

• Follow-Ups:
  • RE: Just require URLs
    • From: "Didier PH Martin" <martind@n...>

• References:
  • RE: Paul has volunteered (was Re: Overloaded URIs must GO!)
    • From: "Hunter, David" <dhunter@M...>
  • RE: Paul has volunteered (was Re: Overloaded URIs must GO!)
    • From: "Jonathan Borden" <jborden@m...>

• Prev by Date: RE: Paul has volunteered (was Re: Overloaded URIs must GO!)
• Next by Date: Re: xml parser for c/c++
• Previous by thread: RE: Paul has volunteered (was Re: Overloaded URIs must GO!)
• Next by thread: RE: Just require URLs
• Index(es):
  • Date
  • Thread