[Moims-dai] Response to rejection of SC234
Mark Conrad
mark.conrad at nara.gov
Mon Sep 10 16:10:23 UTC 2018
" All the components of the AIP would now be focused on the CDO which in my
view is the thing that we really want to focus most on preserving."
Representation Information is defined as: The information that maps a Data
Object into more meaningful concepts so that the Data Object may be
understood in ways exemplified by Preservation Objectives.
Without the Representation Information the CDO will become meaningless over
time. I believe that the previous versions of OAIS which made the Content
Information the original target of preservation are correct.
" But these other things are not the primary focus of long-term
preservation for this OAIS."
Representation Information has to be part of the primary focus of long-term
preservation. Without it, the CDO will become meaningless in the medium to
long term. The best time to gather the initial version of the RepInfo - as
we have discussed frequently - is at or near the time of creation of the
CDO.
"Any archive that was OAIS compatible before will remain OAIS compatible.
I.e. if you had fixity/provenance/… on Content Info (CDO+RepInfo) then you
have sufficient fixit/provenance/… on the CDO. "
This misses the point. You cannot have long term preservation without
RepInfo being part of the original target of preservation.
What is the harm of keeping Content Information as the original target of
preservation? I see a number of harms in making just the CDO the original
target of preservation. Unless there are compelling reasons to change the
original target of preservation - one of the core principles of OAIS - I
don't believe it should be changed.
My two cents.
Mark
On Mon, Sep 10, 2018 at 10:29 AM, John Garrett <garrett at his.com> wrote:
> Hi,
>
>
>
> First thanks to everyone for the many and robust comments and discussions
> generated by this thread. It has allowed for a lot of great discussions.
>
>
>
> However, we also need to finish the OAIS updates in the near term. We’re
> about 2 years in on actively working on these updates and started about 6
> months earlier than that when we set up the review site.
>
>
>
> Just to focus the discussion, although many issues were brought up, SC#222
> just changed the definition of PDI terms to refer them to the CDO rather
> than the Content Information (CDO+RepInfo).
>
>
>
> Some of my thoughts on this.
>
>
>
> All the components of the AIP would now be focused on the CDO which in my
> view is the thing that we really want to focus most on preserving.
>
>
>
> This does not mean that we don’t preserve other objects that are part of
> an AIP (that are there to help preserve the CDO). Doesn’t even mean that
> within the OAIS we don’t preserve other things that are not even in an
> AIP. But these other things are not the primary focus of long-term
> preservation for this OAIS.
>
>
>
> This does not prevent PDI like objects to be associated with any objects
> other than the CDO.
>
>
>
> Yes, it does change the definition that was in the previous 2 issues. But
> I don’t think that it will cause any previous users of the OAIS standard
> any problem. Going this direction is backwards compatible. Any archive
> that was OAIS compatible before will remain OAIS compatible. I.e. if you
> had fixity/provenance/… on Content Info (CDO+RepInfo) then you have
> sufficient fixit/provenance/… on the CDO.
>
>
>
> I’m traveling. Hopefully I will be able to connect to the call.
>
>
>
> Peace and joy,
>
> -JOhn
>
>
>
>
>
> *From:* MOIMS-DAI [mailto:moims-dai-bounces at mailman.ccsds.org] *On Behalf
> Of *Mark Conrad
> *Sent:* Tuesday, September 4, 2018 1:46 PM
> *To:* MOIMS-Data Archive Interoperability <moims-dai at mailman.ccsds.org>
> *Subject:* Re: [Moims-dai] Response to rejection of SC234
>
>
>
> I believe Don is correct about the applicability of PDI only to the
> Content Information (or the Content Data Object per SC 222). If you look at
> the current definitions for the PDI components, they apply to the Content
> Information (or the Content Data Object per SC 222).
>
>
>
> *Preservation Description Information (PDI*): The information which is
> necessary for adequate preservation of the Content Data Obect (sic) [JG1]
> <#m_-2012385482553399736_m_-264577622854671377__msocom_1> and which can
> be categorized as Provenance Information, Context Information, Reference
> Information, Fixity Information, and Access Rights Information.[JG2]
> <#m_-2012385482553399736_m_-264577622854671377__msocom_2>
>
> *Provenance Information*: The information that documents the history of
> the Content Data Object. This information tells the origin or source of
> the Content Data Object,[JG1]
> <#m_-2012385482553399736_m_-264577622854671377__msocom_1> any changes
> that may have taken place since it was originated, and who has had custody
> of it since it was originated. The Archive is responsible for creating and
> preserving Provenance Information from the point of Ingest; however,
> earlier Provenance Information should be provided by the Producer.
> Provenance Information adds to the evidence to support Authenticity.
>
> *Context Information*: The information that documents the relationships
> of the Content Data Object to its environment. This includes why the
> Content Data Object was created and how it relates to other Content Data
> Objects[JG1] <#m_-2012385482553399736_m_-264577622854671377__msocom_1>
>
> *Reference Information*: The information that is used as an identifier
> for the Content Data Object. It also includes identifiers that allow
> outside systems to refer unambiguously to particular Content Data Object.
> [JG1] <#m_-2012385482553399736_m_-264577622854671377__msocom_1>
>
> NOTE: An [JG2] <#m_-2012385482553399736_m_-264577622854671377__msocom_2> example
> of Reference Information is an ISBN.
>
> *Fixity Information*: The information which documents the mechanisms
> that ensure that the Content Data Object [JG1]
> <#m_-2012385482553399736_m_-264577622854671377__msocom_1> has not been
> altered in an undocumented manner.
>
> *Access Rights Information:* The information that identifies the access
> restrictions pertaining to the Content Data Object, [JG1]
> <#m_-2012385482553399736_m_-264577622854671377__msocom_1> including the
> legal framework, licensing terms, and access control. It contains the
> access and distribution conditions stated within the Submission Agreement,
> related to both preservation (by the OAIS) and final usage (by the
> Consumer). It also includes the specifications for the application of
> rights enforcement measures.
>
>
>
> Note that in each case the PDI and its components pertain to the Content
> Information (or the Content Data Object per SC 222). It does not apply to
> all Information Objects held by the OAIS. David, I believe that you
> submitted a Suggested Change, or maybe it was just an email thread, to
> apply the same preservation protocols to all information objects - not just
> Content Information. This suggestion was rejected by the group if I
> remember correctly.
>
> Given the above, I am inclined to agree with Don to reverse SC 222.
>
> Mark
>
>
> Mark Conrad
> NARA Information Services
>
> Systems Engineering Division (IT)
> The National Archives and Records Administration
> Erma Ora Byrd Conference and Learning Center
> Building 494, Room 225
> 610 State Route 956
> Rocket Center, WV 26726
>
> Phone: 304-726-7820
> Fax: 304-726-7802
> Email: mark.conrad at nara.gov
>
> _______________________________________________
> MOIMS-DAI mailing list
> MOIMS-DAI at mailman.ccsds.org
> https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20180910/17028e94/attachment.html>
More information about the MOIMS-DAI
mailing list