I am okay with these suggested changes. I would note that if we make the change from Status to State in 5.1.2.1 then we should also change the text in various places (e.g., 5.1.3) that talks about "status" to use "state" instead. Allen Luniewski IBM WebSphere Cross Brand Services IBM Silicon Valley Laboratory 555 Bailey Ave. San Jose, CA 95141 408-463-2255 408-930-1844 (mobile) Steven Newhouse <Steven.Newhouse@ microsoft.com> To Sent by: OGSA-DMI <ogsa-dmi-wg@ogf.org> ogsa-dmi-wg-bounc cc es@ogf.org Subject [ogsa-dmi-wg] Proposed 02/05/2008 11:03 Specification Changes PM All, I know we've just tried to close the document down... but I've been doing a bit of coding and have some suggested changes and documentation errors from the implementation to date. Hope these seem sensible. Steven Changes 4.2.1.2.1 - Change the names in the DEPR (same semantics but clearer meaning) AvailableProtocols --> DataLocations Protocol -> Data (Attributes: Name -> Protocol & url -> DataUrl 4.2.1 requestDataTransferInstance -> GetDataTransferInstance 4.2.2 getFactoryAttributesDocument -> GetFactoryAttributesDocument 4.3 Add a fault: NoDataLocationsInEpr Change NoTransferProtocolAggrementFault -> NoSourceSinkProtocolMatchFault 5.1.2.1 (& 5.2.7.1.1) Change Status element to State element 5.2 Capitalise first letter of each state change operation 5.2.4 In the text we have a restart operation. In the state diagram we have a resume operation and a resumed event. Something needs to be rationalized here! Personally I prefer changing to the resume operation - restart to me has a different meaning (going back to the beginning) while resume starts mid-transfer after coming out of the suspended state. 5.2.6 getStatus -> GetState Editorial Errors 4.1.1.1 - cross referencing errors 5.1.1.1 - ditto 5.1.4.1 5.2.6.1 -- ogsa-dmi-wg mailing list ogsa-dmi-wg@ogf.org http://www.ogf.org/mailman/listinfo/ogsa-dmi-wg
