-
Key: RMS11-8
-
Legacy Issue Number: 14988
-
Status: open
-
Source: Prefeitura de Fortaleza ( Daniel Ruoso)
-
Summary:
As it is currently designed, the RecordPart requires the content to be stored as a hexBinary blob. This is very convenient to deal with non-XML data, but it's considerably limiting when dealing with XML data.
Considering the emergence of XML databases, if the content of the record part were stored as regular XML, I could perform a XQuery statement that could traverse both the RMS-related data as well as the record-specific data.
This is also aligned with the emergence of XMLSec (allowing digital signatures embedded in XML documents).
The simplest way to solve this issue (while providing backward compatibility) would be to provide a choice between "content" - which would still be the hexBinary blob - and a new "xmlContent" element - which would then be of the type "any" and then could store any arbitrary XML document.
-
Reported: RMS 1.0b1 — Tue, 19 Jan 2010 05:00 GMT
-
Updated: Fri, 6 Mar 2015 20:57 GMT
RMS11 — Content of RecordPart could be more XML friendly
- Key: RMS11-8
- OMG Task Force: Records Management Services V1.1 (RMS) RTF