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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsdm message

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


Subject: RE: [wsdm] [Omod] minutes of the extra call on Thu, Nov 13, 4-5 EST


Title: [Omod] extra call on Thu, Nov 13, 4-5 EST

AGENDA
1. Roll.  
BryanM, Alexando, Fred
 
ISSUE 9: UML models: need to reconcile WS-Manageability and WSMF expressed similarily
Have to start the model and throw in the props/ops/events/metadata per each manageability 'category'.
http://lists.oasis-open.org/archives/wsdm/200310/msg00067.html

Bryan's input: http://lists.oasis-open.org/archives/wsdm/200311/msg00028.html  

We will be discussing every category (subsections of section 3 in MOWS spec), fill out the prop/op/evt list and represent it in a UML with accompanying text.

The first is Identification.

Discussed whether to group properties in data types e.g. EndpointIdentification or just list them as part of the capability model itself. Decided to list them in the capability model as this is merely definition of the sematics for now and it may be properly rendered into XML Schema at the later time.

After a very lengthy discussion we came to the following set of Idenitification properties

  1. endpointIdentifier[1] : xsd:anyURI {ro, const} - a URI of a WSDL component representing (describing) the endpoint being managed
  2. endpointName[1] : xsd:NCName {ro, const} - a name of the WSDL component representing the endpoint being managed. This name is unique among endpoints in the realm of the serviceName + targetNamespace.
  3. serviceName[1] : xsd:NCName {ro, const} - a name of the WSDL component representing the service which endpoint belongs to. This name is unique among services in the reals of the targetNamespace.
  4. targetNamespace[1] : xsd:anyURI {ro, const} - a namespace in which WSDL components such as an endpoint and the service are defined. According to WSDL both service and its endpoints must be defined in the same targetNamespace.
  5. endpointVersion[0..1] : xsd:string {ro, const} - an optional string representation of a version of the endpoint being managed. This could be used to query change management systems, presented to human users, etc.

BryanM had a concern that endpointIdentifier URI is a mix of other properties and therefore the information is duplicated.

Igor: there are use cases when this information could be used in queries and conditions (e.g. XPath in BPEL). Also there is no one mandatory way how to represent the enpointIndetifier URI. W3C TAG listed more than 10 possible choices. In general it is a bad practice to assume URI schema and try to parse infrormation from there. The best so far was to represent information in XML and use it that way.

Bryan/Fred/Igor discussed it and so far we seem to be good with the above set of properties. We agreed to carry on with it onto discussing other categories.

THE IDENTIFICATION IS CLOSED, for those who did not attend this call :)

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788



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