Next in thread → Next in month →

Re: [wsrf] Fw: Comments on RMD wd-09

From
Tim Banks <>
Date
2006-06-13T10:28:31+00:00
ID
Thread
Re: [wsrf] Fw: Comments on RMD wd-09
Dan,

I've marked up a version of the RMD spec with the changes I think are
needed to correct the examples in section 3.

The updates are stored here:
http://www.oasis-open.org/apps/org/workgroup/wsrf/download.php/18704/wsrf-ws_resource_metadata_descriptor-1.0-spec-wd-09%5Btb%20comments%5D.doc


Regards, Tim Banks.


Ian Robinson/UK/IBM@IBMGB wrote on 12/06/2006 17:35:57:

>
> As noted on the call, my #3 is a little wrong.
> The actual resolution text was:
> d) Make the EPR point at a new "DefinitionsRP" element that contains only
> the MDD of interest and carries a targetnamespace attribute - that is,
it's
> the same as the Definitions except that it has a "maxOccurs=1" for the
> child MDD elements.
>
> So 10.2 needs to constrain the content of a metadata resource RPDoc to
> having a Definitions/Metadata element with "maxOccurs=1".
>
>
> Tim's point on the call was that the example of the OperatingSystem
> portType on line 395 the text
> "Lines (68)-(74) contains the Property element describing the
> id:ResourceType resource property from the Identification portType. Lines
> (69)-(73) contain an additional set of ValidValues that the
id:ResourceType
> resource property may contain. "
> is misleading and should not talk about "additional set" of resource
props.
>
> Bryan also observed that line 921 says "specializes the
MetadataDescriptor"
> which is a hangover from when we had a more complex aggregation design.
> Bryan also oberved the References to other WSRF specs need to be updated.
>
>
> Regards,
> Ian
> ----- Forwarded by Ian Robinson/UK/IBM on 12/06/2006 17:16 -----
>

>              Ian

>              Robinson/UK/IBM

>
To
>              12/06/2006 16:30          wsrf

>
cc
>

>
Subject
>                                        Comments on RMD wd-09

>

>

>

>

>

>

>
>
>
> Dan,
> I have some comments on wd-09:
>
>
> #1
> Lines 1131:
> Comment contains an attribute:
>
>    metadataDescriptorLocation=”list of xsd:anyUri”?
>
>
> This attribute should be removed from the comment since the
> MetadataDescriptor element has no such attribute
>
>
> #2
>
>
> Line 1155:
>
>             <xsd:attribute name="wsdlLocation"
>                            type="wsrmd:PairsOfURIType" />
>
> The definition of the type wsrmd:PairsOfURIType has been removed and
needs
> to be put back.
>
> #3
> Section 10.2 needs to be more specific about the following:
> "The metadata WS-Resource MUST support the
> wsrf-rpw:GetResourcePropertiesDocument message exchange and MUST respond
to
> such a request by returning the MetadataDescriptor document that
describes
> the target WS-Resource."
>
> Specifically, per the resolution, the text needs to make it clear that
the
> resource property document returned should be have a root  Definitions
> element (since a standard MDD may have several <Definitions> elements and
> the RPDoc needs to describe precisely one.
>
>
>
> #4
> Could you also upload standalone versions of the WSDL and XSD to Kavi?
>
> Regards,
> Ian
Next in thread → Next in month →