This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8290 - MEX: "Requirements" section confusing and unnecessary
Summary: MEX: "Requirements" section confusing and unnecessary
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: MetadataExchange (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Gilbert Pilz
QA Contact: notifications mailing list for WS Resource Access
Keywords: hasProposal
Depends on:
Reported: 2009-11-13 23:30 UTC by Gilbert Pilz
Modified: 2010-03-17 11:20 UTC (History)
1 user (show)

See Also:


Description Gilbert Pilz 2009-11-13 23:30:08 UTC
Section 2.1 "Requirements" attempts to outline the requirements behind WS-MEX, presumably to aid in a better understanding of the spec. Unfortunately this section fails to accomplish that goal. The relationship between the requirements and the spec-defined entities (XML elements, SOAP messages) is unclear. For example, "Support future versions of known metadata formats". How is this requirement satisfied? Other requirements are vague ("Leverage other Web service specifications . . .") or make use of ill-defined terms (". . . metadata-driven message exchange").

We could attempt to re-write this section to correct these flaws but, since this section really isn't necessary, that seems like more effort than it is worth.

Proposal: remove Section 2.1.
Comment 2 Robert Freund 2010-01-27 18:30:06 UTC
Resolved as proposed option Nr 2 with the addition of
to the end of bullet #2: , or an HTTP reachable resource.
Comment 3 Doug Davis 2010-01-28 04:53:46 UTC
the link doesn't show the that some text has been deleted, the resulting
text needs to look like:

 This specification intends to meet the following requirements:

    *   Define an encapsulation format for metadata.
    *   Treat the metadata about a Web service endpoint as [WS-Transfer] resources, or as an HTTP reachable resource.
    *   Define a bootstrap mechanism for retrieving metadata.
    *   Support future versions of known metadata formats.
    *   Allow new metadata formats to be added. 
Comment 4 Robert Freund 2010-03-17 11:20:13 UTC
resolved on 2010-01-27 with proposal at with the addition to the end of bullet #2: ", or an HTTP reachable resource.