RE: Proposed resolution to LC 77a

The WSDL/schema author says that a:c and b:c mean something.  Maybe they
are author:title and book:title.  If you then invert them, such that you
are sending author titles in book titles and vice versa, you are not
going to "GET" the resource you are thinking of, except perhaps in the
case of where Mr has author the Mr book.

The point being, the schema author says a: means authors and b: books
for the purposes of the particular URI that is described.  Use them as
the schema author says to use them.

Cheers,
Dave

> -----Original Message-----
> From: Hugo Haas [mailto:hugo@w3.org]
> Sent: Thursday, April 07, 2005 8:16 AM
> To: David Orchard
> Cc: www-ws-desc@w3.org
> Subject: Re: Proposed resolution to LC 77a
> 
> * David Orchard <dorchard@bea.com> [2005-04-07 07:29-0700]
> > The point of namespaces is to disambiguate names.  That is, you can
have
> 2 identical local names with different namespace names.  The purpose
of
> serializing the prefix is to preserve that disambiguation.
> 
> But nothing prevents me from doing something like a first message:
> 
>   <foo xmlns:a="http://example.com/1"
>        xmlns:b="http://example.com/2">
>     <a:c>1</a:c>
>     <b:c>2</b:c>
>   </foo>
> 
> serialized as a:c=1&b:c=2
> 
> and then a second:
> 
>   <foo xmlns:b="http://example.com/1"
>        xmlns:a="http://example.com/2">
>     <b:c>1</b:c>
>     <a:c>2</a:c>
>   </foo>
> 
> serialized as b:c=1&a:c=2
> 
> IOW, the prefixes only make sense to the person who has the complete
> instance data in his hand.
> 
> I have the feeling I'm still missing the use case.
> 
> --
> Hugo Haas - W3C
> mailto:hugo@w3.org - http://www.w3.org/People/Hugo/

Received on Thursday, 7 April 2005 19:01:04 UTC