RE: Summary of the QName to URI Mapping Problem

> >foo:barcat
> >bar:cat
> >
> >Yet, using the standard concatenation mapping, both QNames 
> are mapped to the
> >same URI:
> >
> >http://example.com/foobarcat
> >
> >While this URI identifies some resource (by definition), it 
> cannot identify
> >both of the (distinct!) resources identified by the two QNames
> >simultaneously.  Hence the mapping is deficient.
> 
> If they really were distinct, that is. Or, you could take the 
> position that the use of the mapping shows that they couldn't have 
> been distinct.

You could, but I don't think that is a valid position considering
the global scope intended for the SW.

I.e. when those two different QNames occur in
totally different serializations from totally different sources
totally ignorant of each other's use of namespaces, and 
ambiguity is introduced (needlessly) into the knowledge base
when those sources are syndicated because the resultant URIs
collide, that's really going to make for a robust and reliable SW.

Eh?

Patrick

--
Patrick Stickler                      Phone:  +358 3 356 0209
Senior Research Scientist             Mobile: +358 50 483 9453
Software Technology Laboratory        Fax:    +358 7180 35409
Nokia Research Center                 Video:  +358 3 356 0209 / 4227
Visiokatu 1, 33720 Tampere, Finland   Email:  patrick.stickler@nokia.com

Received on Thursday, 16 August 2001 16:12:28 UTC