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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: simple question on namespaces. Last one.

[ Lists Home | Date Index | Thread Index ]
  • From: Paul Tchistopolskii <paul@qub.com>
  • To: xml-dev@lists.xml.org
  • Date: Thu, 28 Dec 2000 17:26:58 -0800


----- Original Message ----- 
From: Andrew Layman <andrewl@microsoft.com>

> example.  If intended for general use, and not qualified in some way, this
> would be a faulty assumption by the toolmaker and would run into immediate
> interoperability problems.  The spec does not say that every namespace URI
> must reference a resource, much less one of any specific type.  

Just to make it clear.

As I've wrote in my previous letters, there is *no* interoperability 
problems if there is only one tool ( tool X ) which is fetching the URLs.

Interoperability problems start to appear only when there will be 
2 different tools both  fetching the URLs and when those 
2 tools will be using this mechanizm ( not prohibited by W3C space )
to fetch different kind of data from the URL.
 
More likely this collision will not gonna happen, because the 
first tool to market will be a de-facto standard.

This means that  first big vendor who will start fetching URLs 
has absolutely *no* problems  ( no  interoperability 
problems as well ).

Could you please tell me what do you mean by "interoperability 
problems" ?

Let's assume that tomorrow I'l ship the Parser that will 
be fetching, for example, CrazyDTD from the namespace URL 
and then validate the document with that CrazyDTD.

I'm shipping this Parser  and people start using it.

What particular interoperability problems will they have ?

No interoperability problems at all. Only benefits. 
Sorry for repeating my previous letters, but I feel that 
my arguments are not easy to understand. 

So I have to repeat that with current situation the vendor 
who starts fetching URLs has no problems *at all*. 

I really don't understand why vendors will  ignore
this legitimate opportunity to take over the world. 

If I have my tools installed on many computers - I'll just 
use this hook tomorrow, to make the format of my 
CrazyDTD a de-facto standard, because I have nothing to 
lost here.  Nothing at all.

If you can explain to me what will I lost with such a step, 
I'll be very glad. 

Many thanks.

Rgds.Paul.







 

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

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