[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
I emailed the TC Administrator about this and wanted to pass along
to you all what I found out. I wondered if it would be possible for us to
update the XSD and WSDL files within the CD03 package and keep the CD03 number,
since the specifications didn’t change. She confirmed what I thought was likely
the case, which is that if any of the files in the package are changed,
then all of the files have to be renumbered. Taking these changes will
thus result in our having to vote on the updated DPWS and WS-Discovery packages
to be CD04. We could keep SOAP-over-UDP at CD03, since none of its files
will be modified; we will need to decide if we want to keep the numbering in
sync, or go ahead and leave SOAP-over-UDP at CD03. -- Toby 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: Toby Nixon
[mailto:Toby.Nixon@microsoft.com] 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] 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] 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----- 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 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]