RE: New Issue 141: WS-Discovery - Editorial - Remove wildcard fromthe normative outline descriptions

[Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>]

Please ignore this thread. This issue is now 142. Thanks.

 

From: Geoff Bullen [mailto:Geoff.Bullen@microsoft.com]
Sent: Monday, January 05, 2009 2:35 PM
To: ws-dd@lists.oasis-open.org
Subject: [ws-dd] New Issue 141: WS-Discovery - Editorial - Remove wildcard from the normative outline descriptions

 

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

From: Vipul Modi
Sent: Monday, January 05, 2009 2:03 PM
To: Ram Jeyaraman; Geoff Bullen
Subject: New Issue: WS-Discovery - Editorial - Remove wildcard from the normative outline descriptions

 

Issue

The normative outline for the Discovery messages describes uses XPATH like syntax to describe various elements of the message. This syntax uses wildcard in the description of few of the elements. Here is an example of such path from the description of Hello message: /s:Envelope/s:Body/*/d:MetadataVersion. The wildcard here is unnecessary and may unnecessarily define the MetadataVersion element in other parts of the Body (including extensions) as well.

 

Proposal

Replace the wildcard with exact path. This results in the following modifications in the spec.

 

 

Original:

4.1 Hello

/s:Envelope/s:Body/*/a:EndpointReference

/s:Envelope/s:Body/*/d:Types

/s:Envelope/s:Body/*/d:Scopes

/s:Envelope/s:Body/*/d:XAddrs

/s:Envelope/s:Body/*/d:MetadataVersion

 

4.1.1 Target Service:

Its metadata changes (see /s:Envelope/s:Body/*/d:MetadataVersion above).

 

 

A Target Service MAY vary the amount of metadata it includes in Hello messages (or Probe Match or Resolve Match messages), and consequently, a Client (or a Discovery Proxy) may receive two such messages containing the same /s:Envelope/s:Body/*/d:MetadataVersion but containing …

 

4.2 Bye

/s:Envelope/s:Body/*/a:EndpointReference

/s:Envelope/s:Body/*/d:Types

/s:Envelope/s:Body/*/d:Scopes

/s:Envelope/s:Body/*/d:XAddrs

/s:Envelope/s:Body/*/d:MetadataVersion

 

5.3 Probe Match

/s:Envelope/s:Body/d:ProbeMatches/d:ProbeMatch/d:Types

See /s:Envelope/s:Body/*/d:Types in Section 5.1 Hello.

/s:Envelope/s:Body/d:ProbeMatches/d:ProbeMatch/d:Scopes

See /s:Envelope/s:Body/*/d:Scopes in Section 5.1 Hello.

/s:Envelope/s:Body/d:ProbeMatches/d:ProbeMatch/d:XAddrs

See /s:Envelope/s:Body/*/d:XAddrs in Section 5.1 Hello.

/s:Envelope/s:Body/d:ProbeMatches/d:ProbeMatch/d:MetadataVersion

See /s:Envelope/s:Body/*/d:MetadataVersion in Section 5.1 Hello.

 

                6.2 Resolve

/s:Envelope/s:Body/*/a:EndpointReference

Endpoint Reference for the Target Service (see Section 3.1 Endpoint References).

 

 

                6.3 Resolve Match

/s:Envelope/s:Body/d:ResolveMatches/d:ResolveMatch/d:Types

See /s:Envelope/s:Body/*/d:Types in Section 5.1 Hello.

/s:Envelope/s:Body/d:ResolveMatches/d:ResolveMatch/d:Scopes

See /s:Envelope/s:Body/*/d:Types in Section 5.1 Hello.

/s:Envelope/s:Body/d:ResolveMatches/d:ResolveMatch/d:XAddrs

See /s:Envelope/s:Body/*/d:Types in Section 5.1 Hello.

/s:Envelope/s:Body/d:ResolveMatches/d:ResolveMatch/d:MetadataVersion

See /s:Envelope/s:Body/*/d:Types in Section 5.1 Hello.

 

 

Modified:

 

4.1 Hello

/s:Envelope/s:Body/d:Hello/a:EndpointReference

/s:Envelope/s:Body/d:Hello/d:Types

/s:Envelope/s:Body/d:Hello/d:Scopes

/s:Envelope/s:Body/d:Hello/d:XAddrs

/s:Envelope/s:Body/d:Hello/d:MetadataVersion

 

4.1.1 Target Service:

Its metadata changes (see /s:Envelope/s:Body/d:Hello/d:MetadataVersion above).

 

A Target Service MAY vary the amount of metadata it includes in Hello messages (or Probe Match or Resolve Match messages), and consequently, a Client (or a Discovery Proxy) may receive two such messages containing the same /s:Envelope/s:Body/d:Hello/d:MetadataVersion but containing

 

4.2 Bye

/s:Envelope/s:Body/d:Bye/a:EndpointReference

/s:Envelope/s:Body/d:Bye/d:Types

/s:Envelope/s:Body/d:Bye/d:Scopes

/s:Envelope/s:Body/d:Bye/d:XAddrs

/s:Envelope/s:Body/d:Bye/d:MetadataVersion

 

5.3 Probe Match

/s:Envelope/s:Body/d:ProbeMatches/d:ProbeMatch/d:Types

See /s:Envelope/s:Body/d:Hello/d:Types in Section 5.1 Hello.

/s:Envelope/s:Body/d:ProbeMatches/d:ProbeMatch/d:Scopes

See /s:Envelope/s:Body/d:Hello/d:Scopes in Section 5.1 Hello.

/s:Envelope/s:Body/d:ProbeMatches/d:ProbeMatch/d:XAddrs

See /s:Envelope/s:Body/d:Hello/d:XAddrs in Section 5.1 Hello.

/s:Envelope/s:Body/d:ProbeMatches/d:ProbeMatch/d:MetadataVersion

See /s:Envelope/s:Body/d:Hello/d:MetadataVersion in Section 5.1 Hello.

 

                6.2 Resolve

/s:Envelope/s:Body/d:Resolve/a:EndpointReference

Endpoint Reference for the Target Service (see Section 3.1 Endpoint References).

 

 

                6.3 Resolve Match

/s:Envelope/s:Body/d:ResolveMatches/d:ResolveMatch/d:Types

See /s:Envelope/s:Body/d:Hello/d:Types in Section 5.1 Hello.

/s:Envelope/s:Body/d:ResolveMatches/d:ResolveMatch/d:Scopes

See /s:Envelope/s:Body/d:Hello/d:Types in Section 5.1 Hello.

/s:Envelope/s:Body/d:ResolveMatches/d:ResolveMatch/d:XAddrs

See /s:Envelope/s:Body/d:Hello/d:Types in Section 5.1 Hello.

/s:Envelope/s:Body/d:ResolveMatches/d:ResolveMatch/d:MetadataVersion

See /s:Envelope/s:Body/d:Hello/d:Types in Section 5.1 Hello.