Bug 341 - INPE-2 - change CIO to CDO
Summary: INPE-2 - change CIO to CDO
Status: RESOLVED CHANGE AGREED
Alias: None
Product: Audit and Certification of Trustworthy Digital Repositories
Classification: Unclassified
Component: Section 4 : Digital Object Management (show other bugs)
Version: Sept 2011
Hardware: No All
: Normal Editorial
Assignee: David Giaretta (david@giaretta.org)
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2022-01-26 15:27 UTC by David Giaretta (david@giaretta.org)
Modified: 2022-09-21 13:47 UTC (History)
3 users (show)

See Also:
Organisation of the submitter: INPE (submitted on behalf of Gerald Banon by David Giaretta)
Disposition of the suggested change:
Category of the suggested change: Updates needed for clarification
Due date:
Explanation of the reason for the suggested change:
“Content Information Object” is not one of the key terms defined in the OAIS Reference Model. Perhaps, in this context, the most closed key term should be “Content Data Object”?


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Giaretta (david@giaretta.org) 2022-01-26 15:27:32 UTC
From: Content Information Object

TO: Content Data Object
Comment 1 David Giaretta (david@giaretta.org) 2022-02-08 10:16:06 UTC
(In reply to David Giaretta from comment #0)
> From: Content Information Object
> 
> TO: Content Data Object

No - not Content Data Object.
Perhaps in these two instances change
FROM
"Content Information Object"
TO
"Content Information object"

since the former is not in the Glossary of OAIS.
Comment 2 Mark Conrad (mark.conrad.iso@gmail.com) 2022-02-08 15:33:50 UTC
Not sure which is the most recent version of ISO 16363. Would need to look at it to make any definitive statements. That said, here are some general comments:

1. Content Information Object is not equivalent to Content Data Object.

2. Changing from Content Information Object to Content Information object is too subtle of a change.

3. A clear justification  for the change from Content Information to Content Data Object in many places in the document is needed. I still do not understand why this change was needed.

If someone can point me to the current version of the document, I can make more specific comments.
Comment 3 David Giaretta (david@giaretta.org) 2022-02-15 13:06:56 UTC
(In reply to Mark Conrad from comment #2)
> Not sure which is the most recent version of ISO 16363. Would need to look
> at it to make any definitive statements. That said, here are some general
> comments:
> 
> 1. Content Information Object is not equivalent to Content Data Object.
> 
> 2. Changing from Content Information Object to Content Information object is
> too subtle of a change.
> 
> 3. A clear justification  for the change from Content Information to Content
> Data Object in many places in the document is needed. I still do not
> understand why this change was needed.
> 
> If someone can point me to the current version of the document, I can make
> more specific comments.

The link is https://public.ccsds.org/review/CCSDS%20652.0-P-1.1/652x0p11.pdf

Perhaps instead 
CHANGE
"Definitions of the Preservation Objectives applicable to each Content Information Object;" 
TO 
"Definitions of the Preservation Objectives applicable to each example of Content Information;"
Comment 4 David Giaretta (david@giaretta.org) 2022-09-21 13:47:09 UTC
Change made:
CHANGE
"Definitions of the Preservation Objectives applicable to each Content Information Object;" 
TO 
"Definitions of the Preservation Objectives applicable to each example of Content Information;"