W3C home > Mailing lists > Public > www-ws-desc@w3.org > November 2003

RE: Action item (2003-10-30) Proposed Revised wording and splitti ng of rules for RPC

From: Liu, Kevin <kevin.liu@sap.com>
Date: Thu, 13 Nov 2003 18:47:17 +0100
Message-ID: <99CA63DD941EDC4EBA897048D9B0061DA95D1F@uspalx20a.pal.sap.corp>
To: "'Umit Yalcinalp'" <umit.yalcinalp@oracle.com>, WS Description List <www-ws-desc@w3.org>

Hi Umit,
>The child elements MAY contain the following attributes:
>       xsi:Nillable, minOccurs and maxOccurs

What's the semantic when maxOccurs of a child element is >1? Is it supposed to be mapped to an array (or similar compound construct) or multiple parameters? Given the conventional rule of "Each element represents a single parameter irrespective of its cardinality", I would guess the former case is intended, but just want to make sure I got the intention right.

My apology if this is already covered by any discussion I missed.  

Best Regards,

-----Original Message-----
From: Umit Yalcinalp [mailto:umit.yalcinalp@oracle.com] 
Sent: Sunday, Nov 02, 2003 01:33 PM
To: WS Description List
Subject: Action item (2003-10-30) Proposed Revised wording and splitting of rules for RPC

Per my action item dated 2003-10-30 (it was 2003-10-23, but not 
recorder), here is the proposed wording for the rpc rules splitting the 
rules into two buckets and incorporating the agreed items [1] on Oct 
23rd 2003 concall.


[1] http://lists.w3.org/Archives/Public/www-ws-desc/2003Oct/0058.html
Received on Thursday, 13 November 2003 12:47:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:36 UTC