[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: New public comment on MUWS Part 2
All,
This weekend I discovered a situation in MUWS Part 2 for which I just entered a public comment (at Vaughn’s request). This email will include both the public comment and some discussion regarding its resolutions: Please note, I raise an entirely new (but related) issue in my comments to the group.
The comment is: ********
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 is no MUWS1 definition of EndpointReference.
********* Comments to the group:
ANY THOUGHTS ON POINT #3?? Is this worth pursuing at the last minute? (Decision required by the 18th.)
Kirk Wilson
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]