RE: Issue 189 proposals:

I'm not sure what the point of your email is Sanjiva... 

Hugo has already found his answer, which hopefully is that the rest of
the xml is not serialized at all.

Do you have a counter-proposal for terminating the "case element not
cited" part of the algorithm?

Dave

-----Original Message-----
From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
Behalf Of Sanjiva Weerawarana
Sent: Monday, July 26, 2004 1:03 PM
To: www-ws-desc@w3.org
Subject: Re: Issue 189 proposals:


"Hugo Haas" <hugo@w3.org> writes:
> 
> If I have:
> 
>   <data>
>     <a>1</a>
>     <b>2</b>
>     <c>3</c>
>     <d>4</d>
>   </data>
> 
> then the draft as it stands says that:
> - location="{a}/{b}" serializes as "1/2?c=3&d=4"
> - location="{a}/{b}/" serializes as "1/2/?c=3&d=4"
> 
> Now, your proposal is that location="{a}/{b/}" serializes as "1/2",
> and that the rest be serialized as application/xml, i.e.:
> 
>   <data>
>     <c>3</c>
>     <d>4</d>
>   </data>
> 
> Am I right?

I have to say .. this is just too much black art for me. How do you
expect users to distinguish between "{a}/{b/}" and "{a}/{b}/" with
such serious implications?

I know we accepted this, but its not a winner feature IMO.

Sanjiva.

Received on Monday, 26 July 2004 17:45:18 UTC