OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-dd message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: Issue 156 - DPWS/WS-Discovery - Editorial - Inconsistencies inXSD/WSDL files


Updated draft XSD with proposed change discuss on the call today (removing minOccurs=0 from Hosted type).

 

From: Dan Driscoll [mailto:Dan.Driscoll@microsoft.com]
Sent: Thursday, April 23, 2009 4:48 PM
To: Toby Nixon; Ram Jeyaraman; ws-dd@lists.oasis-open.org
Subject: [ws-dd] RE: Issue 156 - DPWS/WS-Discovery - Editorial - Inconsistencies in XSD/WSDL files

 

Hi everybody-

Please see the attached proposed update to the DPWS schema which addresses the issues outlined below.

 

Thanks

--D

 

From: Toby Nixon [mailto:Toby.Nixon@microsoft.com]
Sent: Thursday, April 23, 2009 2:37 PM
To: Ram Jeyaraman; ws-dd@lists.oasis-open.org
Subject: [ws-dd] RE: Issue 156 - DPWS/WS-Discovery - Editorial - Inconsistencies in XSD/WSDL files

 

Thanks, Ram.

 

What do people think? Should we go ahead and have Dan and Vipul update the XSD and WSDL files as indicated?

 

Toby Nixon  |  Senior Standards Program Manager  |  Windows Device and Storage Technologies  |  Microsoft Corporation

toby.nixon@microsoft.com  |  www.microsoft.com | V: +1 425 706 2792  |  M: +1 206 790 6377  |  F: +1 425 708 4811

 

From: Ram Jeyaraman [mailto:Ram.Jeyaraman@microsoft.com]
Sent: Thursday, April 23, 2009 1:58 PM
To: ws-dd@lists.oasis-open.org
Subject: [ws-dd] Issue 156 - DPWS/WS-Discovery - Editorial - Inconsistencies in XSD/WSDL files

 

This issue is assigned the number 156. For further discussions on this issue, please refer to this issue number or use this thread.

 

There are some inconsistencies in the DPWS and WS-Discovery XSD/WSDL files. Please find below a description of them. I suggest fixing those inconsistencies among other if any. Fixing those inconsistencies should be non-breaking / editorial in nature and will serve to align the XSD/WSDL files with what is defined in the specifications. No changes to the specifications are necessary.

 

From: Ram Jeyaraman [mailto:Ram.Jeyaraman@microsoft.com]
Sent: Thursday, April 23, 2009 1:48 PM
To: Geoff Bullen; ws-dd@lists.oasis-open.org
Subject: [ws-dd] RE: Groups - New Action Item #0121 report back to TC on accuracy of...

 

I reviewed the XML fragments in the specifications and the associated XSD and WSDL files.

 

Here are the results of my review:

·         The XML fragments in the specifications are well formed and valid.

·         XSD and WSDL files: These are well formed. However, I spotted some editorial inconsistencies in the XSD and WSDL files.

o    WS-Discovery XSD: schemaLocation should be “http://www.w3.org/2006/03/addressing/ws-addr.xsd”.

o    WS-Discovery WSDL: ws-discovery.xsd should be called “wsdd-discovery-1.1-schema-cd-03.xsd”.

o    DPWS XSD:

§  xmlns:wsa should be “http://www.w3.org/2005/08/addressing” and schemaLocation should be “http://www.w3.org/2006/03/addressing/ws-addr.xsd”.

§  Suggest using “wsa:FaultCodesType” instead of “wsa:FaultSubcodesValues”.

§  Suggest splitting the Host and Hosted element definitions.

 

Fixing the afore mentioned inconsistencies should be non-breaking / editorial in nature and will serve to align the XSD/WSDL files with what is already defined in the specifications. I will open an issue to address the above described inconsistencies, and others if any, in the XSD/WSDL files.

 

This completes my action. Thanks.

 

-----Original Message-----
From: geoff.bullen@microsoft.com [mailto:geoff.bullen@microsoft.com]
Sent: Tuesday, April 14, 2009 4:33 PM
To: Ram Jeyaraman
Subject: Groups - New Action Item #0121 report back to TC on accuracy of...

 

 

OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) TC member,

 

Geoff Bullen has created a new action item.

 

Number: #0121

Description: report back to TC on accuracy of...

Owner: Mr. Ram Jeyaraman

Due: 21 Apr 2009

 

Comments:

 

 

View Details:

http://www.oasis-open.org/apps/org/workgroup/ws-dd/members/action_item.php?action_item_id=2647

 

 

 

PLEASE NOTE:  If the above links do not work for you, your email application

may be breaking the link into two pieces.  You may be able to copy and paste

the entire link address into the address field of your web browser.

 

- OASIS Open Administration

<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright (c) OASIS(r) 2009. All Rights Reserved.

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.

OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.

OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.

The name "OASIS" is trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.
-->
<xs:schema
    targetNamespace="http://docs.oasis-open.org/ws-dd/ns/dpws/2009/01";
    xmlns:tns="http://docs.oasis-open.org/ws-dd/ns/dpws/2009/01";
    xmlns:wsa="http://www.w3.org/2005/08/addressing";
    xmlns:xs="http://www.w3.org/2001/XMLSchema";
    elementFormDefault="qualified"
    blockDefault="#all" >

  <xs:import
    namespace="http://www.w3.org/2005/08/addressing";
    schemaLocation="http://www.w3.org/2006/03/addressing/ws-addr.xsd"; />

  <xs:element name="ThisModel" type="tns:ThisModelType" />
  <xs:complexType name="ThisModelType" >
    <xs:sequence>
      <xs:element name="Manufacturer" type="tns:LocalizedStringType"
          maxOccurs="unbounded" />
      <xs:element name="ManufacturerUrl" type="xs:anyURI"
          minOccurs="0" />
      <xs:element name="ModelName" type="tns:LocalizedStringType"
          maxOccurs="unbounded" />
      <xs:element name="ModelNumber" type="xs:string" minOccurs="0" />
      <xs:element name="ModelUrl" type="xs:anyURI" minOccurs="0" />
      <xs:element name="PresentationUrl" type="xs:anyURI"
          minOccurs="0" />
      <xs:any namespace="##other" processContents="lax"
          minOccurs="0" maxOccurs="unbounded" />
    </xs:sequence>
    <xs:anyAttribute namespace="##other" processContents="lax" />
  </xs:complexType>

  <xs:element name="ThisDevice" type="tns:ThisDeviceType" />
  <xs:complexType name="ThisDeviceType" >
    <xs:sequence>
      <xs:element name="FriendlyName" type="tns:LocalizedStringType"
          maxOccurs="unbounded" />
      <xs:element name="FirmwareVersion" type="xs:string"
          minOccurs="0" />
      <xs:element name="SerialNumber" type="xs:string" minOccurs="0" />
      <xs:any namespace="##other" processContents="lax"
          minOccurs="0" maxOccurs="unbounded" />
    </xs:sequence>
    <xs:anyAttribute namespace="##other" processContents="lax" />
  </xs:complexType>


  <xs:complexType name="LocalizedStringType" >
    <xs:simpleContent>
      <xs:extension base="xs:string" >
        <xs:anyAttribute namespace="##other" processContents="lax" />
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>

  <xs:element name="Relationship" >
    <xs:complexType>
      <xs:sequence>
        <xs:any namespace="##any" processContents="lax"
            minOccurs="0" maxOccurs="unbounded" />
      </xs:sequence>
      <xs:attribute name="Type" type="tns:DeviceRelationshipTypes" use="required" />
      <xs:anyAttribute namespace="##other" processContents="lax" />
    </xs:complexType>
  </xs:element>

  <xs:simpleType name="DeviceRelationshipTypes" >
    <xs:union memberTypes="tns:DeviceRelationshipTypeURIs xs:anyURI" />
  </xs:simpleType>

  <xs:simpleType name="DeviceRelationshipTypeURIs" >
    <xs:restriction base="xs:anyURI" >
      <xs:enumeration value="http://docs.oasis-open.org/ws-dd/ns/dpws/2009/01/host"; />
    </xs:restriction>
  </xs:simpleType>

  <xs:simpleType name="DeviceMetadataDialectURIs" >
    <xs:restriction base="xs:anyURI" >
      <xs:enumeration value="http://docs.oasis-open.org/ws-dd/ns/dpws/2009/01/ThisModel"; />
      <xs:enumeration value="http://docs.oasis-open.org/ws-dd/ns/dpws/2009/01/ThisDevice"; />
      <xs:enumeration value="http://docs.oasis-open.org/ws-dd/ns/dpws/2009/01/Relationship"; />
    </xs:restriction>
  </xs:simpleType>

  <xs:simpleType name="DeviceEventingFilterDialects" >
    <xs:union memberTypes="tns:DeviceEventingFilterDialectURIs xs:anyURI" />
  </xs:simpleType>

  <xs:simpleType name="DeviceEventingFilterDialectURIs" >
    <xs:restriction base="xs:anyURI" >
      <xs:enumeration value="http://docs.oasis-open.org/ws-dd/ns/dpws/2009/01/Action"; />
    </xs:restriction>
  </xs:simpleType>

  <xs:simpleType name="DeviceActionURIs" >
    <xs:restriction base="xs:anyURI" >
      <xs:enumeration value="http://docs.oasis-open.org/ws-dd/ns/dpws/2009/01/fault"; />
    </xs:restriction>
  </xs:simpleType>

  <xs:simpleType name="DeviceSoapFaultSubcodes" >
    <xs:union memberTypes="tns:DeviceSoapFaultSubcodeQNames wsa:FaultCodesType xs:QName" />
  </xs:simpleType>

  <xs:simpleType name="DeviceSoapFaultSubcodeQNames" >
    <xs:restriction base="xs:QName" >
      <xs:enumeration value="tns:FilterActionNotSupported" />
    </xs:restriction>
  </xs:simpleType>

  <xs:element name="Host" type="tns:HostServiceType" />
  <xs:complexType name="HostServiceType" >
    <xs:sequence>
      <xs:element ref="wsa:EndpointReference" />
      <xs:element ref="tns:Types" minOccurs="0" />
      <xs:any namespace="##other" processContents="lax"
          minOccurs="0" maxOccurs="unbounded" />
    </xs:sequence>
    <xs:anyAttribute namespace="##other" processContents="lax" />
  </xs:complexType>
  
  <xs:element name="Hosted" type="tns:HostedServiceType" />
  <xs:complexType name="HostedServiceType" >
    <xs:sequence>
      <xs:element ref="wsa:EndpointReference"
          maxOccurs="unbounded" />
      <xs:element ref="tns:Types" />
      <xs:element ref="tns:ServiceId" />
      <xs:any namespace="##other" processContents="lax"
          minOccurs="0" maxOccurs="unbounded" />
    </xs:sequence>
    <xs:anyAttribute namespace="##other" processContents="lax" />
  </xs:complexType>

  <xs:element name="ServiceId" type="xs:anyURI" />
  <xs:element name="Types" type="tns:QNameListType" />
  <xs:simpleType name="QNameListType" >
    <xs:list itemType="xs:QName" />
  </xs:simpleType>

  <xs:simpleType name="DiscoveryTypeValues" >
    <xs:restriction base="xs:QName" >
      <xs:enumeration value="tns:Device" />
    </xs:restriction>
  </xs:simpleType>

  <xs:element name="Profile" type="tns:AssertionType" />
  <xs:complexType name="AssertionType" >
    <xs:complexContent>
      <xs:restriction base="xs:anyType">
        <xs:anyAttribute namespace="##other" processContents="lax" />
      </xs:restriction>
    </xs:complexContent>
  </xs:complexType>

  <xs:attribute name="DiscoveryType" type="xs:anyURI" />

</xs:schema>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]