Issue 6385: No need for MIME reference (deployment-ftf)
Source: Zuehlke Engineering (Mr. Frank Pilhofer, fpilhofer2008(at)gmail.com)
Nature: Uncategorized Issue
Severity: 
Summary: The resolution for issue 5962 added references. This included a
reference to RFC 2045 (MIME) for the description of Base64 encoding.
At the same time, the resolution for issue 6024 makes use of Base64
implicit by using the XML data type xsd:base64Binary. Therefore,
there is no need having a normative reference to MIME.


Proposed resolution:


In section 4.1, Remove normative reference to MIME.

Resolution: 
Revised Text: 
Actions taken:
October 21, 2003: received issue
Discussion: 

End of Annotations:=====
ubject: Bug Fix Issues 
Date: Tue, 21 Oct 2003 10:10:59 -0400 
Thread-Topic: Bug Fix Issues 
Thread-Index: AcOX3SdG3qXagVVSRD23TCjkWg95ew== 
From: "Pilhofer, Frank" <fpilhofe@mc.com> 
To: <issues@omg.org> 
Cc: <deployment-ftf@omg.org> 
X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id h9LE6I2U018836 


Here are some new issues against the Deployment and Configuration
of Component-based Applications specification as amended by the
first vote. Section numbers are from the convenience document
ptc/03-10-01.


(1) No need for MIME reference


The resolution for issue 5962 added references. This included a
reference to RFC 2045 (MIME) for the description of Base64 encoding.
At the same time, the resolution for issue 6024 makes use of Base64
implicit by using the XML data type xsd:base64Binary. Therefore,
there is no need having a normative reference to MIME.


Proposed resolution:


In section 4.1, Remove normative reference to MIME.