Re: [sca-policy] sca-policy schema-- where is current schema located? or, perhaps, cansomeone fix the sca-policy.xsd ?

[Mike Edwards <mike_edwards@uk.ibm.com>]

Folks,

The schema files on www.osoa.org/xmlns/sca/1.0
are intended to correspond to the schemas published in the SCA 1.0
specifications on the www.osoa.org site.

This now raises an issue of us creating
equivalent schema files with correct naming on the OASIS site.  I
believe
that the schema files should be available
on the site via a dereferencable URL, just as on the OSOA site.
I will raise an issue for this in the
Assembly TC (as Assembly owns the main namespace) - other TCs will need
to consider what to do with any XSDs
they own that are not in the main namespace.


Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  
Email:  mike_edwards@uk.ibm.com

ashok malhotra <ashok.malhotra@oracle.com>

26/11/2007 19:05

Please respond to
ashok.malhotra@oracle.com

To	Moberg Dale <dmoberg@axway.com>
cc	sca-policy@lists.oasis-open.org
Subject	Re: [sca-policy] sca-policy schema-- where is current schema located? or, perhaps, can someone fix the sca-policy.xsd ?

Hi Dale:
I'm not sure of the status of the Schemas on the osoa site.
For the SCA Policy TC, the Schemas are in the latest framework document
document on the website.

I think you have, indeed, found bugs in the Schema.  In both the cases
you mention, we want to include
elements defined in WS-Policy as well elements defined by SCA.  This
would lead to a UPA violation with the <any>
Please raise an issue!

Ashok


Moberg Dale wrote:

>At http://www.osoa.org/xmlns/sca/1.0/ I found sca related schemas and
>was looking at the sca-policy.xsd on the call today.
>
>sca-binding-ejb.xsd              22-Feb-2007
13:00  1.5K  
>sca-binding-jms.xsd              28-Jun-2007
10:18  5.2K  
>sca-binding-sca.xsd              14-Feb-2007
06:15  1.1K  
>sca-binding-webservice.xsd       28-Jun-2007 10:16  1.4K
 
>sca-core.xsd                
    04-Oct-2007 05:58   15K  
>sca-definitions.xsd              13-Feb-2007
04:32  898   
>sca-implementation-composite.xsd 09-Feb-2007 07:26  1.1K  
>sca-implementation-cpp.xsd       28-Feb-2007 06:25  2.4K
 
>sca-implementation-java.xsd      09-Feb-2007 07:26  1.1K
 
>sca-interface-cpp.xsd            28-Feb-2007
06:25  1.7K  
>sca-interface-java.xsd           28-Jun-2007
10:11  1.0K  
>sca-interface-wsdl.xsd           28-Jun-2007
10:11  1.0K  
>sca-policy.xsd                
  19-Feb-2007 11:38  3.2K  
>sca.xsd                  
       28-Jun-2007 10:19  813   
>
>Are these the current schemas the TCs are to be considering?
>If not, where are the current drafts?
>
>If so, it seems that the sca-policy.xsd has some of the annoying
>ambiguous derivation errors in 2 of its complex types that have a choice
>over elements from the targetNamespace and from a web service policy
>namespace. Since the wsp policy elements are not in the targetNamespace,
>the "any" element clause would also apply to them along with
the wsp:
>element clauses explicitly mentioned. Hence, the derivation would be
>ambiguous. Here are the two types Oxygen 9 flags as mistaken. (Also,
the
>other schema files have a lot of these ambiguous derivation error
>messages.)
>
>                
<complexType name="Qualifier">
>                
                 <choice
minOccurs="1" maxOccurs="unbounded">
>                
                 
               
<element name="intentMap" type="sca:IntentMap"/>
>                
                 
               
<element ref="wsp:PolicyAttachment"/>
>                
                 
               
<any namespace="##other" processContents="lax"/>
>                
                 </choice>
>                
                 <attribute
name="name" type="string" use="required"/>
>                
                 <anyAttribute
namespace="##any" processContents="lax"/>
>
>                
</complexType>
>
>
><complexType name="PolicySet">
>                
                 <choice
minOccurs="0" maxOccurs="unbounded">
>                
                 
               
<element name="policySetReference"
>type="sca:PolicySetReference"/>
>                
                 
               
<element name="intentMap" type="sca:IntentMap"/>
>                
                 
               
<element ref="wsp:PolicyAttachment"/>
>                
                 
               
<element ref="wsp:Policy"/>
>                
                 
               
<element ref="wsp:PolicyReference"/>
>                
                 
               
<any namespace="##other" processContents="lax"/>
>                
                 </choice>
>                
                 <attribute
name="name" type="QName" use="required"/>
>                
                 <attribute
name="provides" type="sca:listOfQNames"
>use="optional"/>
>                
                 <attribute
name="appliesTo" type="string"
>use="required"/>
>                
                 <anyAttribute
namespace="##any" processContents="lax"/>
>
>                
</complexType>
>
>---------------------------------------------------------------------
>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
>
>
>  
>


-- 
All the best, Ashok

---------------------------------------------------------------------
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

---

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU