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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsdm-comment message

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


Subject: Public Comment


Comment from: kirk.wilson@ca.com

Name: Kirk WIlson
Title: Architect, Office of CTO
Organization: CA, Inc
Regarding Specification: MUWS Part 2

In section 4.1.2.2 of MUWS Part 2, the sequence for the Participant child includes (starting with line 1175):

    <muws1:ManageabilityEndpointReference/> *
    <muws1:ResourceId/> ?
    . . .
    {any} *

The explanation of the any makes reference to the MOWS defined EndpointReference element for use when the participant is a Web Service (rather than a WSDM resource).  The example that accompanies this pseudo schema in fact uses the mows:EndpointReference element (beginning line 1254).   

However, in section 4.2.2, the sequence of Participant is presented as (starting with line 1376) 

  <muws1:ManageabilityEndpointReference/> *
  <muws1:EndpointReference/> *
  <muws1:ResourceId/> ?
  . . .

Now we have a muws1:EndpointReference inserted into the sequence.  The schema of MUWS Part 2, RelationshipParticipantType (beginning line 1760) supports this sequence rather than the one in 4.1.2.2.  Unfortunately, there does not appear to be a MUWS1 definition of EndpointReference!!





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