OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: [xml-dev] A multi-step approach on defining object-orientednature of

[ Lists Home | Date Index | Thread Index ]
  • To: "Rick Jelliffe" <ricko@allette.com.au>,<xml-dev@lists.xml.org>
  • Subject: RE: [xml-dev] A multi-step approach on defining object-orientednature of DOM
  • From: "Dare Obasanjo" <dareo@microsoft.com>
  • Date: Wed, 21 Aug 2002 14:45:01 -0700
  • Thread-index: AcJJWwi878RCDCHZR8W00rZBkSV0GgAAND+g
  • Thread-topic: [xml-dev] A multi-step approach on defining object-orientednature of DOM

> -----Original Message-----
> From: Rick Jelliffe [mailto:ricko@allette.com.au] 
> Sent: Wednesday, August 21, 2002 12:33 PM
> To: xml-dev@lists.xml.org
> Subject: Re: [xml-dev] A multi-step approach on defining 
> object-orientednature of DOM
> 
> 
> > 6. Several instances of the use of java.net.URL for 
> normalization of a 
> > namespace URI that breaks comparability.  This leads to 
> explanations 
> > that "a namespace URI is *not* a [java.net.]URL!"
> 
> Could you give some more details of this one?

What if you want a Java class that represents syntactically valid
namespace names? Until J2SE 1.4, java.net.URL was people's frequent
choice since most namespace URIs they saw were HTTP URLs.  


-- 
PITHY WORDS OF WISDOM 
Putting in a request to go home early is the best way to jinx yourself
and end up working overtime.     

This posting is provided "AS IS" with no warranties, and confers no
rights. 






 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS