This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 3569 - It is impossible to compare QNames
Summary: It is impossible to compare QNames
Status: RESOLVED WONTFIX
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Implementation/CR Issue (show other bugs)
Version: unspecified
Hardware: PC Windows 2000
: P2 normal
Target Milestone: --
Assignee: Martin Chapman
QA Contact: Martin Chapman
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-01 21:45 UTC by Martin Chapman
Modified: 2006-08-08 19:34 UTC (History)
0 users

See Also:


Attachments

Description Martin Chapman 2006-08-01 21:45:38 UTC
This is feedback on the WS-CDL Choreography CR of 2005-11-09. I have been
implementing CDL at a bank and have some questions and feedback on the CR.

The problem I have with the CR is the XML Schema for WS-CDL requires you to
compare a QName type with an NCName type. This comparison is impossible
because the QName type does not have equality or ordering defined for it.

Section 4.2 of the CDL specification states that field
/package/relationshipType/roleType/@typeRef (a QName), must reference the
field /package/roleType/@name (a NCName). I took this from the text: 'A
relationshipType element MUST have exactly two roleTypes defined. Each
roleType is specified by the typeRef attribute within the roleType element.
The "QName" value of the typeRef attribute of the roleType element MUST
reference the name of a roleType.'

Please tell me why the datatype QName was used. I have been unable to work
out why QName was used. QName is normally used to reference elements rather
than the contents of elements.

I have been assuming the word "reference" is as an equality test as defined
by XPath 1.0. This should be explicit in the specification.

Looking through the mail-list examples (e.g.
http://lists.w3.org/Archives/Public/public-ws-chor/2005Sep/0001) it seems
that QName and NCName are being used in the style of xs:ID and xs:IDREF. Why
not just use xs:ID and xs:IDREF? This would also have the benefit of making
the constraint that a typeRef must reference a roleType name explicit. Both
xs:ID and xs:IDREF are subtypes of xs:NCName. 

At the very least typeRef and roleType should be some type of string that is
comparable, otherwise references cannot be tested.

Matthew Rawlings
Comment 1 Martin Chapman 2006-08-08 19:34:00 UTC
The proposer agrees this is not an explicit cdl issue:

http://lists.w3.org/Archives/Public/public-ws-chor/2006Jun/0000.html
At meeting on 8 Aug 06 we agreed to close no action