- From: Arthur Ryman <ryman@ca.ibm.com>
- Date: Tue, 15 Nov 2005 08:48:59 -0500
- To: Lawrence Mandel <lmandel@ca.ibm.com>
- Cc: www-ws-desc@w3.org, www-ws-desc-request@w3.org
- Message-ID: <OF2967CB6D.F0493254-ON852570BA.004ABBF3-852570BA.004BE2A6@ca.ibm.com>
Lawrence, Thx. I'll add these. Arthur Ryman, IBM Software Group, Rational Division blog: http://ryman.eclipsedevelopersjournal.com/ phone: +1-905-413-3077, TL 969-3077 assistant: +1-905-413-2411, TL 969-2411 fax: +1-905-413-4920, TL 969-4920 mobile: +1-416-939-5063, text: 4169395063@fido.ca Lawrence Mandel/Toronto/IBM@IBMCA Sent by: www-ws-desc-request@w3.org 11/15/2005 02:32 AM To www-ws-desc@w3.org cc Subject types assertions I'd like to suggest the addition of the following types assertions to the WSDL 2.0 spec, appendix E. For each entry I've listed a suggested id, the assertion, and the location of the assertion in the spec.: schema-0016 Section 3.1 A WSDL 2.0 document MUST NOT refer to XML Schema components in a given namespace unless an xs:import or xs:schema element information item for that namespace is present or the namespace is the XML Schema namespace which contains built-in types as defined in XML Schema Part 2: Datatypes Second Edition [XML Schema: Datatypes]. schema-0017 Section 3.1.1.1 The referenced schema MUST contain a targetNamespace attribute information item on its xs:schema element information item and the values of these two attribute information items MUST be identical. (There are actually two assertions here for the same text: 1) The imported schema must contain a targetNamespace, 2) the target namespace of the import element and imported schema must match.) schema-0018 Section 3.1.2 For example, two or more inlined schemas may have the same targetNamespace provided that they do not define the same elements or types. (There may be a better assertion text quote for this assertion.) schema-0019 Section 3.1.2.1 The targetNamespace attribute information item defines the namespace of the element declarations and type definitions inlined in its [owner element] xs:schema element information item. WSDL 2.0 modifies the XML Schema definition of the xs:schema element information item to make this attribute information item required. schema-0020 Section 3.1.3 An element attribute information item MUST NOT refer to a global xs:simpleType or xs:complexType definition. schema-0021 Section 3.2 A specification of extension syntax for an alternative schema language MUST use a namespace that is different than the namespace of XML Schema. The namespace of the alternative schema language is used for element information items that are children of the wsdl:types element information item and for any extensibility attribute information items that appear on other components. The namespace MUST be an absolute IRI. schema-0022 Section 3.3.3 The wsdlx:interface and wsdlx:binding attributes may be used either independently or together. If they are used together then they MUST satisfy the same consistency rules that apply to the {interface} property of a Service component and the {binding} property of a nested Endpoint component, that is either the binding refers the interface or the binding refers to no interface. types-0023 Section 3.2 A specification of extension syntax for an alternative schema language MUST include the declaration of an element information item, intended to appear as a child of the wsdl:types element information item, which references, names, and locates the schema instance (an ?import? element information item). Lawrence Mandel Software Developer IBM Rational Software Phone: 905 - 413 - 3814 Fax: 905 - 413 - 4920 lmandel@ca.ibm.com
Received on Tuesday, 15 November 2005 13:49:10 UTC