- From: Jacek Kopecky <jacek@systinet.com>
- Date: Mon, 25 Mar 2002 19:37:31 +0100 (CET)
- To: Noah Mendelsohn <noah_mendelsohn@us.ibm.com>
- cc: Jean-Jacques Moreau <moreau@crf.canon.fr>, Henrik Frystyk Nielsen <henrikn@microsoft.com>, Martin Gudgin <marting@develop.com>, Herve Ruellan <ruellan@crf.canon.fr>, <soap@zaks.demon.co.uk>, <xml-dist-app@w3.org>
Noah,
I don't think your second statement is just an other way of
saying the first.
The attributes id and ref are only meaningful the known way when
used on elements using the SOAP Encoding encodingStyle.
Or at least I always thought so.
Maybe this is the right time to 1) make the attributes namespace
qualified and say that SOAP Encoding references may only go to
SOAP Encoding IDs. Or to 2) say that the encodingStyle is applied
also on the targets of references. Or to 3) explain what happens
when a node in SOAP Encoding data has a different encodingStyle.
In fact, I believe we have two slightly different issues here:
A) can SOAP Encoding reference point to non-SOAP-Encoding ID?
B) what's it mean if a node in SOAP Encoding data has a
different encodingStyle?
My positions are No on A (making the attributes ns-qualified
would probably help us achieve this) and on B it's either
forbidden or a terminal node.
Best regards,
Jacek Kopecky
Senior Architect, Systinet (formerly Idoox)
http://www.systinet.com/
On Mon, 25 Mar 2002 noah_mendelsohn@us.ibm.com wrote:
> So, what I think I'm hearing is: the placement of
> SOAPENV:encodingStyle attributes has no direct bearing on the number
> of graphs. Stated another way: id/href can cross from one
> encodingStyle scope to another? I just think we have to be clear on
> this. Thanks.
>
> ------------------------------------------------------------------
> Noah Mendelsohn Voice: 1-617-693-4036
> IBM Corporation Fax: 1-617-693-8676
> One Rogers Street
> Cambridge, MA 02142
> ------------------------------------------------------------------
>
>
>
Received on Monday, 25 March 2002 13:37:33 UTC