Cory Casanave wrote: (01)
>Here is the document - I have no idea what the problem was.
>
> (02)
Just a quick look at the document suggests that the reqirements could be
met with a profile of the OASIS ebXML Registry standard (ISO 15000, part
3 and 4). (03)
For example the record capture service could be used to annote a record
with (04)
>1. The Record Capture Service shall provide the capability to populate
the Record_Creator_Unique_Identifier3 attribute when a DECLARED RECORD
is set > aside producing a populated Record_Creator_Unique_Identifier
attribute. (05)
A unique identifier representing the Creator, is automatically assigned
when a record is published (06)
>2. The Record Capture Service shall provide the capability to populate
the Record_Unique_Identifier attribute when a DECLARED RECORD is set
aside >
> producing a populated Record_Unique_Identifier attribute. (07)
A unique identifier representing the record, is automatically assigned
when a record is published if not provided by publisher. (08)
>3. The Record Capture Service shall provide the capability to populate
the Record_Capture_Date attribute using the SYSTEM DATE when a DECLARED
> RECORD is set aside producing a populated Record_Capture_Date attribute. (09)
The capture date is automatically assigned by registry upon publish (010)
>4. The Record Capture Service shall provide the capability to make
available for output all data populating the attributes created by the
Record Capture Use
> Case.4 (011)
All content and metadata may be accessed modulo access control by anyone. (012)
> PROVENANCE SERVICE (013)
The ebXML Registry provides a provenance information model and
supporting protocols to establish and manage provenance information
regarding managed information assets. (014)
> Functional Requirement(s)
> 1. The Provenance Establish Service shall provide the capability to
populate the Agency_Official_Name_Current1 attribute producing a
populated >
> Agency_Official_Name_Current attribute.
> 2. The Provenance Establish Service shall provide the capability to
populate the Agency_Official_Name_Current_Date attribute when the
> Agency_Official_Name attribute is populated using the SYSTEM DATE
producing a populated Agency_Official_Name_Current_Date attribute.
> 3. The Provenance Establish Service shall provide the capability to
populate the Agency_Official_Name_superordinate a…∞)_Current2 attribute
producing
> a populated Agency_Official_Name_(superordinate a…∞)_Current attribute.
> .... (015)
The ebXML Registry ifno model is extensible so all of above metadata
attributes can be supported. (016)
The remainder of the requirement look like apretty good fit. (017)
The federated features of the ebXML Registry allow multiple archive
stores to be searched seamlessly and to have inter-artifcat links
between them modulo access control. (018)
I wonder, seeing all this synergy, who should I explore the possibility
of creation of a new normative specification "ebXML Registry Repository
Profile for NARA-RMS" and using it as a standards-based answer to these
requirements? (019)
>-Cory
>
>
>
>>-----Original Message-----
>>From: soa-forum-bounces@xxxxxxxxxxxxxx [mailto:soa-forum-
>>bounces@xxxxxxxxxxxxxx] On Behalf Of Andrew S. Townley
>>Sent: Tuesday, April 04, 2006 7:10 AM
>>To: Service-Oriented Architecture CoP
>>Subject: Re: [soa-forum] SOA Demo - Records Management Option
>>
>>
>>Hi Cory,
>>
>>I'm having trouble getting the document. At the moment, I can't load
>>any pages from the OMG website. Would it be possible for someone to
>>send this to me off-list?
>>
>>Thanks,
>>
>>ast
>>
>>On Mon, 2006-04-03 at 19:51, Cory Casanave wrote:
>>
>>
>>>Last week there was a meeting with the records management community
>>>headed by NARA (National Archives) in support of turning the recently
>>>adopted records management requirements into a standard.
>>>
>>>
>>>
>>>As part of that meeting the idea came up of using records management
>>>as the core of the SOA Demo and we would like your thoughts on that
>>>option. The requirements for record management can be found here;
>>>http://www.omg.org/cgi-bin/doc?gov/2006-03-01
>>>
>>>
>>>
>>>This would be a very positive convergence of a government architecture
>>>effort, an upcoming standards effort and SOA. On the other hand, it
>>>is an area that is less understood by many than the buyer/broker
>>>/manufacturer demo and there are less solutions that could be
>>>integrated by the SOA.
>>>
>>>
>>>
>>>In any case, we will need to come to some resolution on the subject of
>>>the demo very soon. Your thoughts would be appreciated.
>>>
>>>
>>>
>>>Regards,
>>>
>>>Cory Casanave
>>>
>>>
>>>
>>>______________________________________________________________________
>>> _________________________________________________________________
>>>Subscribe/Unsubscribe/Config:
>>>
>>>
>>http://colab.cim3.net/mailman/listinfo/soa-forum/
>>
>>
>>>Shared Files: http://colab.cim3.net/file/work/soa/
>>>Community Portal: http://colab.cim3.net/
>>>Community Wiki: http://colab.cim3.net/cgi-
>>>
>>>
>>bin/wiki.pl?AnnouncementofSOACoP
>>--
>>Join me in Dubrovnik, Croatia on May 8-10th when I will be speaking at
>>InfoSeCon 2006. For more information, see www.infosecon.org.
>>
>>**************************************************************************
>>*************************
>>The information in this email is confidential and may be legally
>>privileged. Access to this email by anyone other than the intended
>>addressee is unauthorized. If you are not the intended recipient of this
>>message, any review, disclosure, copying, distribution, retention, or any
>>action taken or omitted to be taken in reliance on it is prohibited and
>>may be unlawful. If you are not the intended recipient, please reply to
>>or forward a copy of this message to the sender and delete the message,
>>any attachments, and any copies thereof from your system.
>>**************************************************************************
>>*************************
>> _________________________________________________________________
>>Subscribe/Unsubscribe/Config: http://colab.cim3.net/mailman/listinfo/soa-
>>forum/
>>Shared Files: http://colab.cim3.net/file/work/soa/
>>Community Portal: http://colab.cim3.net/
>>Community Wiki: http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP
>>
>>
>>------------------------------------------------------------------------
>>
>> _________________________________________________________________
>>Subscribe/Unsubscribe/Config:
>http://colab.cim3.net/mailman/listinfo/soa-forum/
>>Shared Files: http://colab.cim3.net/file/work/soa/
>>Community Portal: http://colab.cim3.net/
>>Community Wiki: http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP
>>
>> (020)
--
Regards,
Farrukh (021)
farrukh.najmi.vcf
Description: Vcard
_________________________________________________________________
Subscribe/Unsubscribe/Config: http://colab.cim3.net/mailman/listinfo/soa-forum/
Shared Files: http://colab.cim3.net/file/work/soa/
Community Portal: http://colab.cim3.net/
Community Wiki: http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP (01)
|