[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
I'm wondering if we should treat this as a Public Review comment? All the best, Ashok David Booz wrote: > > http://www.osoa.org/jira/browse/POLICY-72 > > So much for going to PR with no open issues. > > 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 > > Inactive hide details for Raymond Feng---02/16/2009 02:08:55 > PM---TARGET: SCA Policy Framework Version 1.1, CD 01 Rev 16 > DESCRIRaymond Feng---02/16/2009 02:08:55 PM---TARGET: SCA Policy > Framework Version 1.1, CD 01 Rev 16 DESCRIPTION: > > > From: > Raymond Feng/Burlingame/IBM@IBMUS > > To: > sca-policy@lists.oasis-open.org > > Date: > 02/16/2009 02:08 PM > > Subject: > [sca-policy] [NEW ISSUE] Nesting <intentMap> shoud be removed from > Qualifer XSD type > > ------------------------------------------------------------------------ > > > > TARGET: SCA Policy Framework Version 1.1, CD 01 Rev 16 > > DESCRIPTION: > > By the XML schema for Intent, only one level of qualification is > allowed (see line 2994 for Intent and IntentQualifier). The schema > definition and the example for IntentMap hasn't been change to reflect > the restriction. > > The following is quoted from the document around Line 3057. Please > note Qualifier contains <intentMap>. > <complexType name="IntentMap"> > <choice minOccurs="1" maxOccurs="unbounded"> > <element name="qualifier" type="sca:Qualifier"/> > <any namespace="##other" processContents="lax"/> > </choice> > <attribute name="provides" type="QName" use="required"/> > <anyAttribute namespace="##any" processContents="lax"/> > </complexType> > <complexType name="Qualifier"> > <choice minOccurs="1" maxOccurs="unbounded"> > <element name="intentMap" type="sca:IntentMap"/> > <any namespace="##other" processContents="lax"/> > </choice> > <attribute name="name" type="string" use="required"/> > <anyAttribute namespace="##any" processContents="lax"/> > </complexType> > > Line 764 has the similar problem too: > <intentMap provides="xs:QName"> > <qualifier name="xs:string">? > <xs:any>* > <intentMap/> ? > </qualifier> > </intentMap> > > Line 861 also shows an example with two-level qualifications of > Intents (confidentiality.message.body or confidentiality.message.whole) > > <policySet name=”SecurityPolicy” provides=”confidentiality”> > <intentMap provides=”confidentiality” > > <qualifier name=”message”> > <intentMap provides=”message” > > <qualifier name=”body”> > <!-- policy attachment for body encryption --> > </qualifier> > <qualifier name=”whole”> > <!-- policy attachment for whole message encryption --> > </qualifier> > </intentMap> > </qualifier> > <qualifier name=”transport”> > <!-- policy attachment for transport encryption --> > </qualifier> > </intentMap> > </policySet> > > PROPOSAL: > > Fix the schema to remove the intentMap element from Qualifier type. > Fix the example to remove 2nd level of qualification. > > Thanks, > Raymond >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]