Subject: [NEW ISSUE]: SCA schema fixes requested for sca-core.xsd (based on OSOA site versions, that may be copied to OASIS site)
Raiser: Dale Moberg
Description: For sca-core.xsd, four Unique Particle Attribution Constraint violations ( that is, multiple or “ambiguous” derivations for valid instances exist).
1. complexType “Service”, for certain cases (sca:callback omitted mainly), and when there are elements from ##other namespaces, derivations from either “Any” element within the choices can exist for a single instance.
2. complexType “Reference” problem similar to case 1
3. complexType “ComponentService” problem also involves instances where either “Any” element from ##other namespaces can appear in derivations.
4. complexType “ComponentReference” problem also involves instances where either “Any” element from ##other namespaces can appear in derivations.
Proposal: Possibly condense the “Any” elements together? Possibly a more general discussion about extensions in XSD and ways to avoid the UPA violation is needed. D. Orchard http://pacificspirit.com/Authoring/Compatibility/ has a page of links related to these questions arising out of wsdl and policy and other xsd extension and versioning struggles.