8290 2009-11-13 23:30:08 +0000 MEX: "Requirements" section confusing and unnecessary 2010-03-17 11:20:13 +0000 1 1 1 Unclassified WS-Resource Access MetadataExchange FPWD All All CLOSED REMIND hasProposal P2 normal --- 1 gilbert.pilz gilbert.pilz dug public-ws-resource-access-notifications oldest_to_newest 29563 0 gilbert.pilz 2009-11-13 23:30:08 +0000 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. 31288 1 bob 2010-01-27 18:27:11 +0000 proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/0161.html 31289 2 bob 2010-01-27 18:30:06 +0000 Resolved as proposed option Nr 2 with the addition of to the end of bullet #2: , or an HTTP reachable resource. 31308 3 dug 2010-01-28 04:53:46 +0000 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. 33643 4 bob 2010-03-17 11:20:13 +0000 resolved on 2010-01-27 with proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/0161.html with the addition to the end of bullet #2: ", or an HTTP reachable resource.