Issue 14996: Are effective and end dates required fields in the Party model? (rms-ftf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Name: Daniel Ruoso Company: Prefeitura de Fortaleza mailFrom: daniel@ruoso.com Notification: Yes Specification: RMS For the fields effectiveStartDate and effectiveEndDate in Role, that information might not be known at the time the record is first captured. Are these fields required? If not, how do I work around that? Resolution: Revised Text: Actions taken: January 20, 2010: received issue Discussion: End of Annotations:===== m: "Larry L. Johnson" To: "'Juergen Boldt'" Subject: RE: issue 14988 -- RMS FTF issue Date: Wed, 20 Jan 2010 15:31:51 -0500 X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcqZ8PqoNtjkRMY/TV+wXHx2VZrPGAAHj+1A X-ACL-Warn: { X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - capricorn.lunarpages.com X-AntiAbuse: Original Domain - omg.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - TethersEnd.com X-Source: X-Source-Args: X-Source-Dir: Hi Jü I promised Daniel Ruoso that I would enter this issue on his behalf. Can you take the contact data from below and use it for this one as well? Title: Are effective and end dates required fields in the Party model? Description: For the fields effectiveStartDate and effectiveEndDate in Role, that information might not be known at the time the record is first captured. Are these fields required? If not, how do I work around that? Thanks, Larry Larry L. Johnson Chair, OMG RMS Finalization Task Force http://gov.omg.org/gov-ftf-rms.htm mailto:rms-ftf@omg.org TethersEnd Consulting 2023 Cleveland St Clearwater, FL 33765-3107 V/F: 888-502-9847 V/F: 202-449-5637 http://www.TethersEnd.com/ -------------------------------------------------------------------------------- From: Juergen Boldt [mailto:juergen@omg.org] Sent: Wednesday, January 20, 2010 11:49 AM To: issues@omg.org; rms-ftf@omg.org Subject: issue 14988 -- RMS FTF issue From: webmaster@omg.org Date: 19 Jan 2010 16:12:56 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Daniel Ruoso Company: Prefeitura de Fortaleza mailFrom: daniel@ruoso.com Notification: Yes Specification: RMS Section: XSD FormalNumber: gov/2009-03-10 Version: 1.0 RevisionDate: May 2009 Page: 1 Title: Content of RecordPart could be more XML friendly Nature: Enhancement Severity: Significant test: 3qw8 B1: Report Issue Description: 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. Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org