[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Fw: [wsbpel] Issue - 157 - conf call brief recap ... and carry forward ...
Hi Rania, I agree the use case is more than substitution group. In my mind the issue comes down to whether we are creating a new path. If a user identifies <from>$var/x</from><to>$varb/a/b/c</to> should $varb/a/b/c become $varb/a/b/x when the operation is done. In my mind it is better if we describe this operation as leaving the path $varb/a/b/c, but the contents of $varb/a/b/c has changed. I think the use cases were the element name for the target is unknown and derived from the source are best left to issue 11 where we should define a create new node capability (and maybe a rename, but create is the 80% case). We can put it in 157 as an option on the <to>, but maybe we are putting too much in 157. - Chris -----Original Message----- From: Rania Khalaf [mailto:rkhalaf@watson.ibm.com] Sent: Thursday, June 30, 2005 10:36 AM To: Ron Ten-Hove Cc: chris.keller@active-endpoints.com; wsbpel@lists.oasis-open.org Subject: Re: Fw: [wsbpel] Issue - 157 - conf call brief recap ... and carry forward ... Hi guys, I wanted to just point out that the element-to-element node copy (with name) is *not* only a substitution group problem: It also occurs in the case that something is uses xsd:choice or xsd:any, which are not so uncommon. Rania --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]