[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, Can I get a clarification on what you are suggesting? Is it that we require a source (<from>) for an AII (<to>) to be a TII, not an AII or EII. And the user must do whatever is necessary in the target expression language to conform to that requirement, whether it be .../text() or string(...). Thanks, Chris -----Original Message----- From: Rania Khalaf [mailto:rkhalaf@watson.ibm.com] Sent: Wednesday, June 22, 2005 9:14 AM To: Alex Yiu Cc: rkhalaf@us.ibm.com; Charlton Barreto; wsbpeltc; jwillis@exchange.microsoft.com Subject: Re: Fw: [wsbpel] Issue - 157 - conf call brief recap ... and carry forward ... Hi alex, My point that since AII is always a TII if you use text() , then if you want to copy from/to an attribute you should select the value not the attribute. So you can't do: <from>$var/@foo</from> but would instead do <from>$var/@foo/text()</from> then there is no distinction. With the attribute this is reasonable restriction if the agreement is that since we are not allowing creating new attributes but simply replacing old ones. Rania Alex Yiu wrote: > > Hi Rania, > > During the discussion of the "F2F-Table", I did sense that we are > treating AII and TII virtually the same. > > That means: if people think we don't lose any clarity through this > simplification, we can potentially collapse the rows and columns of > AII and TII. That is: > > /From: / > Src\Dest > EII > AII > TII > EII with > Complex-Content > RE > F > F > EII with > Simple-Content > RE > RC > RC > AII > RC > RC > RC > TII > RC > RC > RC > > > > /To: / > Src\Dest > EII > AII/TII > EII with > Complex-Content > RE > F > EII with > Simple-Content > RE > RC > AII/TII > RC > RC > > > > [** On the other hand: > > * Your first table is NOT a simpification of the "F2F-Table". In > the "F2F-Table", copy from-TII-to-EII is defined as > Replace-Content, NOT Fault. > * I am thinking whether collapsing those rows/columns might make > using XSLT to define those entries a bit more complicated ... I > guess we can worry about that when we actually arrive that step. > > **] > > Next 2 questions are: > > * Whether we want to differentiate Complex-Content from > Simple-Content of EII: My current preference is: yes, we should > differentiate. Because, our typing story will be a bit too weak, > if we allow the following happen at runtime: > > > <!-- > $nameVar is initialized to: > <foo:personName> > <foo:firstName>John</foo:firstName> > <foo:firstName>Dole</foo:firstName> > </foo:personName> > --> > <assign> > <copy> > <from> $nameVar </from> > <to> $var/name/text() </to> > </copy> > </assign> > <!-- > if we apply XPath 1.0 String() function / <xslt:value-of> > automatically to nameVar, the result would be "JohnDole". > Two strings will be concatenated together without any delimiter. > I still find this default XPath 1.0 conversion kind of funky, > except used in during string-value equal comparison. > --> > > If people want to assign "JohnDole" to that name text field, I > would say people would apply String() function to the from-spec. > E.g.: > > <assign> > <copy> > <from> string($nameVar) </from> > <to> $var/name/text() </to> > </copy> > </assign> > > > * Whether and how to support XSD substitutionGroup pattern in > <bpel:copy>. > > > > Thanks! > > > Regards, > Alex Yiu > > > > Rania Khalaf wrote: > >> Hi Alex, >> >> So it looks like the table you have reduces to the diagonal,and the >> rest are just short-hand of using 'text()' (in the case of XPath. >> Otherwise whatever the equivalent thing is .. ). AII doesn't need to >> show up on the 'basic' table because it's really just selecting the >> AII and then doing'text()'. >> >> Src\Dest >> >> >> >> EII >> >> >> >> TII >> >> EII >> >> >> >> Replace (except name) >> >> >> >> F >> >> TII >> >> >> >> F >> >> >> >> Replace >> >> >> Makes your original table reduce to pointing at the above cells (in >> italics, we just show the usage of 'text()' to undo the shortcut ): >> >> Src\Dest >> >> >> >> EII >> >> >> >> AII >> >> >> >> TII >> >> EII with >> Complex-Content >> >> >> >> EII/EII >> >> >> >> F >> >> >> >> F >> >> EII with >> Simple-Content >> >> >> >> EII/EII >> >> >> >> TII/TII >> >> /From >> EII/text() >> To >> AII/text()/ >> >> >> >> TII/TII >> >> /From/ >> >> /EII/text()/ >> >> AII >> >> >> >> TII/TII >> >> /From AII/text() >> To >> EII/text()/ >> >> >> >> I/TII// >> >> /From >> AII/text() >> To >> AII/text()/ >> >> >> >> TII/TII >> >> From >> >> /AII/text()/ >> >> >> TII >> >> >> >> TII/TII >> >> /To >> EII/text()/ >> >> >> >> TII/TII >> >> /To >> AII/text()/ >> >> >> >> Replace >> >> >> If this is the case, do we really need all these entries ? Are they >> helping that much or just adding clutter ? >> >> Note that I haven't addressed substitution groups here .. just trying >> to look closely at your table as you asked :) >> >> Regards, >> 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]