11551 2010-12-14 18:44:17 +0000 EVD: need for an easy way to locate and retrieve event description files 2011-01-11 22:06:08 +0000 1 1 1 Unclassified WS-Resource Access Eventing LC PC All CLOSED REMIND http://lists.w3.org/Archives/Public/public-ws-resource-access-comments/2010Nov/0000.html hasProposal P2 normal --- 1 bob public-ws-resource-access-notifications dug public-ws-resource-access-notifications oldest_to_newest 43363 0 bob 2010-12-14 18:44:17 +0000 The WS-EventDescriptions spec does not specify/recommend/encourage any specific file extension for event descriptions. Without an agreed upon extension, the event descriptions could potentially be specified in an .xml file. That means when trying to find the definition for a QName of an event type, one would have to potentially go through all the .xml files (which can be very large) within one's scope of resolution to see which one contains event descriptions. This is a potential problem for the SCA Assembly spec [2] and other specifications/applications that may want to reuse event descriptions. A standard extension, for example, .evd, would also help wrt associating event description files with tools that work with those files. For example, appropriate editors. 2) The WS-EventDescriptions spec recommends the use of WS-MetadataExchange and WS-Policy for retrieving event description. This might be appropriate for applications that already use those specifications, but is an unnecessary burden for applications and specifications (such as SCA) that do not require Mex or WS-Policy. An additional mechanism similar to something like schemaLocation/wsdlLocation would be more useful, simpler, and would promote reuse of WS-EventDescriptions. 43364 1 bob 2010-12-14 18:46:23 +0000 Proposal is to define a mime type for event descriptions which would include a specified file extension. 43365 2 bob 2010-12-14 18:47:33 +0000 proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Dec/0019.html 43368 3 dug 2010-12-14 20:39:11 +0000 partial proposal: use mex:Location instead of defining a new pointer mechanism 43814 4 bob 2011-01-04 21:26:25 +0000 2011-01-04 proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2011Jan/0003.html accepted with the addition that a global change of name to id be performed so as to make the result consistent with application+xml It was agreed that the editor could implement the change after resolution