[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sca-policy] ISSUE-72: Nesting <intentMap> shoud be removed fromQualifer XSD type - proposal
Dave: A couple of comments. You removed the ability to add an intent map as a child of an intent map. This is fine. In the schema you now have: <complexType name="Qualifier"> 2416 <choice minOccurs="1" maxOccurs="unbounded"> 2417 <any namespace="##other" processContents="lax"/> 2418 </choice> 2419 <attribute name="name" type="string" use="required"/> 2420 <anyAttribute namespace="##any" processContents="lax"/> 2421 </complexType> Why do we still need the <choice> ?. I think it can be removed. Some questions. 1. There used to be an example of an intent map within an intent map. Did that get dropped somewhere along the way. If not, we shd remove it now. 2. Was there ever the ability in the schema to declare qualifiers for qualified intents? I don't remember this. If we never had it, what was the purpose of allowing intent maps within intent maps? All the best, Ashok David Booz wrote: > > Attached is a proposal to resolve Issue 72 > (http://www.osoa.org/jira/browse/POLICY-72) > > /(See attached file: sca-policy-1.1-spec-cd02-issue72-v1.pdf)/ > > Dave Booz > STSM, BPM and SCA Architecture > Co-Chair OASIS SCA-Policy TC and SCA-J TC > "Distributed objects first, then world hunger" > Poughkeepsie, NY (845)-435-6093 or 8-295-6093 > e-mail:booz@us.ibm.com > > ------------------------------------------------------------------------ > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to 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]