OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-dd message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Issue 065 - WS-Discovery - Terminologies should not make normativetext like statements


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

 

From: Vipul Modi
Sent: Thursday, September 18, 2008 8:44 AM
To: Ram Jeyaraman
Subject: NEW Issue - WS-Discovery - Terminologies should not make normative text like statements

 

Please defer discussions on this issue until a time this issue is accepted and is assigned a number.

 

Description:

The terminologies section is for defining the terms used in the specification. They should not include normative statements. There are two definitions that are in question:

Discovery Proxy:  The definition of Discovery Proxy states that it is an optional component of the architecture. Definition should not make the normative statement. The compliance section already says that an endpoint may implement DP, TS, or Client.

 

Scope: The definition says that it “may be used”.  The “may” should not be part of the definition.

 

Proposed Resolution:

Discovery Proxy: An endpoint that facilitates discovery of Target Services by Clients. Discovery Proxies are an optional component of the architecture.

Scope: An extensibility point that may be allows used to organize Target Services to be organized into logical groups    

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]