Issue 17271: Missing action in 6.4.2.2 when not including metadata (hdata-ftf) Source: MITRE (Mr. Jason Mathews, mathews(at)mitre.org) Nature: Revision Severity: Significant Summary: Section 6.4.2.2 (Adding new document) describes the case when including metadata in POST operation using "multipart/form-data", however, it does not describe when not including metadata. Here's text for the implied requirement: If POST does not include metadata then MUST POST with a Content Type conforming to the media type of the section. The body of the POST MUST contain the document of the new document. Document metadata in this case MUST be computed from the new document. This text or something like it must be inserted in this context: "It is to be treated as informational, since the service MUST compute the valid new metadata based on the requirements found in the HRF specification <INSERT HERE> The content media type MUST conform..." Resolution: Revised Text: Actions taken: March 26, 2012: received issue Discussion: End of Annotations:===== m: webmaster@omg.org To: Subject: Issue/Bug Report ******************************************************************************* Name: Jason Mathews Employer: MITRE mailFrom: mathews@mitre.org Terms_Agreement: I agree Specification: OMG hData RESTful Transport Section: 6.4.2.2 FormalNumber: dtc/2012-01-03 Version: 1.0 Doc_Year: 2012 Doc_Month: January Doc_Day: Day Page: 16 Title: Missing action in 6.4.2.2 when not including metadata Nature: Revision Severity: Significant CODE: 3TMw8 B1: Report Issue Description: Section 6.4.2.2 (Adding new document) describes the case when including metadata in POST operation using "multipart/form-data", however, it does not describe when not including metadata. Here's text for the implied requirement: If POST does not include metadata then MUST POST with a Content Type conforming to the media type of the section. The body of the POST MUST contain the document of the new document. Document metadata in this case MUST be computed from the new document. This text or something like it must be inserted in this context: "It is to be treated as informational, since the service MUST compute the valid new metadata based on the requirements found in the HRF specification The content media type MUST conform..."