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: [OMod] Another try at "magic bullet"

Igor and all,

What about the following proposal. Based on all discussions so far I get a
sense this could be agreeable to everyone for both our 0.5 and 1.0

MUWS defines in its "identity" category:

- ResourceID[1]: anyURI - unique ID of the resource managed.

MOWS defines in its "identification" category:

- EndpointReference[1]: styleTBD - [a WSDL (1.1 or 2.0) "service" element
containing only one endpoint] OR [a wsa:EndpointReference element] OR [a
complex type that includes each of the above as choices and possibly some
other], whichever the working group decides to use for endpoint reference.
This is a separate issue, discussed in the Uplat area. We can postpone for a
bit the decision on what endpoint reference format we use, but this should
be consistent with the endpoint reference format we use for MUWS (for
example to express participants in relationships). This property represents
one way to access the resource but doesn't preclude the existence of
multiple descriptions of the resource.

- EndpointDescriptions[0..n]: xsd:anyURI - a list of URIs pointing to
descriptions of the resource. The different descriptions can be of the same
or of different types (e.g. WSDL1.1, WSDL2.0, UDDI tModel...)



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