W3C home > Mailing lists > Public > public-ws-resource-access-comments@w3.org > June 2012

Re: WS-Mex dialect type

From: Robert Freund <bob.freund@hitachisoftware.com>
Date: Thu, 28 Jun 2012 02:21:26 +0000
To: "poehlsen@itm.uni-luebeck.de" <poehlsen@itm.uni-luebeck.de>
CC: "public-ws-resource-access-comments@w3.org" <public-ws-resource-access-comments@w3.org>
Message-ID: <260BC78271BF5C46B3D0F8BE98E17DA201A3D3@USINDEM103.corp.hds.com>
Stephan,
Please respond if the edits satisfies your issue?
thanks
-bob
ws-ra chair

On May 31, 2012, at 9:48 AM, Doug Davis wrote:


Stephan,
  see if the document attached to the issue https://www.w3.org/Bugs/Public/show_bug.cgi?id=17234   addresses your concerns.

thanks
-Doug Davis
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com<mailto:dug@us.ibm.com>
The more I'm around some people, the more I like my dog.


poehlsen@itm.uni-luebeck.de<mailto:poehlsen@itm.uni-luebeck.de>

05/07/2012 04:17 AM


To
        public-ws-resource-access-comments@w3.org<mailto:public-ws-resource-access-comments@w3.org>
cc

Subject
        WS-Mex dialect type







Hello,

as far as I discovered, the dialect is a mex:QNameSerialization instead
of a xs:Qname as before.
http://lists.w3.org/Archives/Public/public-ws-resource-access-notifications/2011Feb/0138.html
Are there any information available, why this was changed?

Since "Normative text within this specification takes precedence over
the XML Schema and WSDL descriptions, which in turn take precedence
over outlines, which in turn take precedence over examples." it is
quite difficult to see what seems to be right.

Especially since the serialization algorithm is only provided as a
"note" (non-normative text?) within the spec. (In the description of
the dialect attribute /mex:Metadata/mex:MetadataSection/@Dialect a
_note_ says that "the QName is serialized as
{namespace-uri}localName."
In the XML Schema exists only a regex: <xs:pattern value='\{.*\}.+'/>
In the outline in section 4 the dialect is a 'xs:Qname'
http://www.w3.org/TR/ws-metadata-exchange/#web-services-metadata

If the note is applicable Example 2-4 line 21, 27, and 34 have an
incorrect Qname serialization. It must be a QNameSerialization, same
with Example 2-6 line 19.


There is another bug:
Example 2-4 line 21 lacks an identifier. Now it is required in contrast
to the submission version of the spec.


Kind regards,
Stephan
Received on Thursday, 28 June 2012 02:22:01 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:40:12 UTC