sca-policy message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: [NEW ISSUE] Nesting <intentMap> shoud be removed from Qualifer XSD type
- From: Raymond Feng <rfeng@us.ibm.com>
- To: sca-policy@lists.oasis-open.org
- Date: Mon, 16 Feb 2009 11:08:00 -0800
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]