RE: [wsn] AI from telecon 10/11

["Patil, Sanjay" <sanjay.patil@sap.com>]

Title: Message

 

Following is my proposed text for this new issue. Please review.

 

Thanks,

Sanjay

 

WSN2.31: Namespace prefix change may result into unbound QNames

Some of the message components (such as TopicExpression and Selector) may include QName strings in their value.  The namespace prefixes used in the QNames are normally declared by some in-scope parent element.

It is possible that toolings modify the namespace declarations and change the prefix values without necessarily updating the QName strings appearing in the message content, resulting into unbound QNames.

Specifications

• WS-BaseNotification

Proposed Recommendations

Steve made the following proposal via email - http://www.oasis-open.org/archives/wsn/200410/msg00021.html

For each message exchange that describes a component that may include a QName embedded in a string, the following normative text be included in the description of that component:

If the value of the component contains QNames, then the namespace declarations that specify the mapping of the QName's prefix to an actual namespace URI can be found amongst any namespace declaration in scope for the component.  Note: Some XML processors MAY modify the namespace declarations. Designers should be aware that such transforms exist and may render the expression incoherent, as it is likely the change in namespace declaration will not update a QName embedded within a string.

Notes

http://www.oasis-open.org/archives/wsn/200409/msg00031.html

Status:   Open

Date: Oct 11, 2004

Contact:

Igor Sedukhin

Cross Reference:

WSN2.12 raises a related issue.

-----Original Message-----
From: Steve Graham [mailto:sggraham@us.ibm.com]
Sent: Monday, Oct 11, 2004 10:37 AM
To: wsn@lists.oasis-open.org
Subject: [wsn] AI from telecon 10/11

I took an AI to suggest resolution text to the proposed problem:
>Problem with the use of namespace prefixes in topic and selector expressions. Client tooling may modify the the >prefixes used
>in a web service request, so prefixes used in these expressions may become unbound. Igor has observed a similar >problem in WS-E[6]

I propose the resolution be as follows:
For each message exchange that describes a component that may include a QName embedded in a string, the following normative text be included in the description of that component:

If the value of the component contains QNames, then the namespace declarations that specify the mapping of the QName's prefix to an actual namespace URI can be found amongst any namespace declaration in scope for the component.  Note: Some XML processors MAY modify the namespace declarations. Designers should be aware that such transforms exist and may render the expression incoherent, as it is likely the change in namespace declaration will not update a QName embedded within a string.

sgg
++++++++
Steve Graham
(919)254-0615 (T/L 444)
STSM, On Demand Architecture
Member, IBM Academy of Technology
<Soli Deo Gloria/>
++++++++