Heppenheim Producer-Archive Interface Specification Status of standardisation project Main characteristics, major changes, items pending

PAIS – October Contents 1. Objective 2. Basic principles 3. Main changes 4. Items pending 5. Conclusion BOUCON:

PAIS – October Objective ■Implementation standard for Producer – Archive Interface  Conformity with the PAIMAS  Conformity with the XFDU ■Aimed mainly at Formal Definition and Transfer Phase with Validation

PAIS – October Basic principles

PAIS – October Basic principles - The Model of Objects for Transfer ■The Model of Objects for Transfer (MOT)  A Transfer Object is a structured and organized set of one or more Data Objects that are to be transferred to the Archive. (There may be multiple Transfer Objects of the same Transfer Object Type.)  Descriptors describe a Transfer Object Type or a Collection of Transfer Object Types.  Descriptors are related to each other by parent-child relationships, and specify relationships between the Data Objects corresponding to these types.  Descriptors are derived from one or more Models.  The set thus structured makes up the MOT.

PAIS – October Basic principles - SIP ■The Submission Information Packages (SIPs)  These are packets used for transferring data: a SIP must include one or more Transfer Objects.  All the components of a Transfer Object must be in the same SIP.  Packaging of SIPs is based on the XFDU packaging standard.  The standard provides a SIP Model (that will be mapped with the XFDU).

PAIS – October Basic principles – SIP and XFDU ■SIP schema  Attributes for the global information of a SIP:  sip_id  producer_id  project_id  sip_content_type_id  sip_sequence_number  Attributes corresponding to a Transfer Object:  descriptor_id  transfer_object_id  last_transfer_object  replacement_transfer_object  And also (Transfer Object group):  transfer_object_group_id, data_object_type_id, file_location …

PAIS – October Basic principles – SIP and XFDU ■XFDU schema: Red Book, January 2007  packageHeader  informationPackageMap  dataObjectSection  metadataSection  behaviourSection

PAIS – October Basic principles – SIP and XFDU ■XFDU schema: Red Book, January 2007  packageHeader  informationPackageMap  dataObjectSection  metadataSection  behaviourSection ■SIP to XFDU Mapping

PAIS – October SIP Global information sip_ID project_ID producer_ID sip_content_type_ID sip_sequence_number Transfer Object Identification and Status descriptor_ID transfer_object_ID … SIP.xsd Transfer Object Content transfer_object_group_ID data_object_type_ID … packageHeader environmentInfo #wildcard informationPackageMap #wildcard contentUnit extension ….. XFDU.xsd dataObjectSection mimeType … dataObject … file_location …. SIP XFDU.xml packageHeader environmentInfo sip_ID project_ID producer_ID sip_content_type_ID sip_sequence_number informationPackageMap descriptor_ID transfer_object_ID contentUnit extension transfer_object_group_ID ….. dataObjectSection mimeType … dataObject data_object_type_ID … file_location …. } } } }

PAIS – October PAIS main dates ■ November 2006: proposal for a draft Red Book ■ August 2007: current version #7  The PAIS standard includes the concepts definition and their implementation.  The tutorial (Green Book) will explain how to use the standard including examples. Main changes from the previous version? October 04October 05Sept/Nov 06February 06June 06 draft White Book versions 12345/6 ■September 2004: concept paper August 07 7

PAIS – October Main changes ■ Some changes in terminology  POT -> MOT  SIP grouping constraints -> SIP Content Types  Transfer Object Content ->Transfer Object group -> Transfer Object Component ? ■Changes in the Plan (Descriptors presentation, SIP section) ■Many changes in the Transfer Object Descriptor (hierarchical structure of the content) ■All sections completed (Overview, SIP Model, SIP mapping to FXDU) ■New XML schema for the SIP sequencing constraints

PAIS – October Main changes: PAIS content ■1. Introduction ■… ■2 Overview ■ 2.1 General framework ■ 2.2 Formally describing Data Objects for Transfer ■ 2.2 SIP creation and validation ■3 Descriptions of Producer Data ■ 3.1 Transfer Object Descriptor Specification ■ General and detailed description: abstract view + concrete implementation ■ 3.2 Collection Descriptor Specification ■ General and detailed description: abstract view + concrete implementation ■ 3.3 Specialization of the Descriptor Models ■ 3.4 Design of the MOT ■4 Description of constraints on types of SIPs ■ 4.1 Abstract Constraints on types of SIPs ■ SIP Content Types Specification ■ SIP sequencing constraints specification ■ 4.2 Concrete constraints on types of sips ■ SIP Content Types implementation ■ SIP Sequencing Constraints implementation ■5 SIP Model ■ 5.1 Abstract SIP Model ■ 5.2 Concrete SIP Implementation using XFDU ■ SIP XML schema for XFDU ■ Mapping abstract SIP to XFDU ■ SIP specialization ■ANNEX A: Transfer Object and Collection Descriptors XML schema ■ANNEX B : legend for XML figures ■ANNEX C : Informative references

PAIS – October Main changes: PAIS content ■1. Introduction ■… ■2 Overview ■ 2.1 General framework ■ 2.2 Formally describing Data Objects for Transfer ■ 2.2 SIP creation and validation ■3 Descriptions of Producer Data ■ 3.1 Transfer Object Descriptor Specification ■ General and detailed description: abstract view + concrete implementation ■ 3.2 Collection Descriptor Specification ■ General and detailed description: abstract view + concrete implementation ■ 3.3 Specialization of the Descriptor Models ■ 3.4 Design of the MOT ■4 Description of constraints on types of SIPs ■ 4.1 Abstract Constraints on types of SIPs ■ SIP Content Types Specification ■ SIP sequencing constraints specification ■ 4.2 Concrete constraints on types of sips ■ SIP Content Types implementation ■ SIP Sequencing Constraints implementation ■5 SIP Model ■ 5.1 Abstract SIP Model ■ 5.2 Concrete SIP Implementation using XFDU ■ SIP XML schema for XFDU ■ Mapping abstract SIP to XFDU ■ SIP specialization ■ANNEX A: Transfer Object and Collection Descriptors XML schema ■ANNEX B : legend for XML figures ■ANNEX C : Informative references

PAIS – October Main changes: Descriptors ■2 Descriptors:  Transfer Object Descriptor (TOD): set of characteristics describing a Transfer Object.  Collection Descriptor (no associated Data) : describes a collection of one or more Transfer Object Types or other collections. Descriptors are organized in parent-child relationships.  gives a coherent view of the Data to be transferred. ■Relationships between objects are described by ‘associations’ inside the Descriptor. ■General structure for the TOD?

PAIS – October Main changes: Descriptor ■General structure

PAIS – October Main changes: Descriptor ■General structure

PAIS – October Main changes: Descriptor ■Identification Changed name (and position)

PAIS – October Main changes: Descriptor ■Description Changed name Type definition

PAIS – October Main changes: Descriptor ■Relations Type definition changed

PAIS – October ■Groups and Data Objects Main changes New hierarchical structure

PAIS – October ■Groups and Data Objects Main changes Name changed Format reviewed

PAIS – October Items pending: PAIS red book version ■Many exchanges between the teams have  lead to a progressive convergence between NASA and CNES for the concepts and the terminology,  raised points that should be discussed this week. ■Other comments are expected (after distribution of the current version)

PAIS – October Items pending : SIP ■ Validation of the SIP Model. ■ Validation of the SIP mapping to XFDU part along with the current version of the XFDU standard.

PAIS – October Items pending: PAIS tutorial ■ Extract explanations and examples as a basis from the September 2006 PAIS version ■ Complete it to have an homogeneous tutorial (one practical example) ■ Proposed plan (from the previous meeting)

PAIS – October Items pending: PAIS tutorial 1. Overview section 1.1 PAIMAS view 2. Requirements for standardization 2.1 Transfer Object Descriptor  Explanation of RB material  Examples  Best practices 2.2 Collection Descriptor  Explanation of RB material  Examples  Best practices 2.3 SIP Content constraints  Explanation of RB material  Examples  Best practices 2.3 SIP Sequencing constraints  Explanation of RB material  Examples  Best practices 2.4 SIP mapping to XFDU  Explanation of RB material  Examples  Best practices 3. Tutorial sections (follow structure of RB) 4. Transfer and Validation 4.1 Procedures 4.2 Best practices 5. Conclusion Annex A: “Complete example” ■Follow one project through all steps ■Full formal spec = MOT + Content Constraints + Sequencing Constraints ■Several Sips Annex B: More examples Plan

PAIS – October Items pending: tool for the MOT design and transfer follow up ■ A prototype has been developed according to the current standard version and will be presented during this week ■ Implementation strongly linked to:  some PAIS descriptors attributes:  descriptor ID, title, descriptor Model (for the structure of MOT),  all identifiers (for the validation part),  the SIP schema attributes: all attributes (for the validation and transfer follow up),  the XFDU schema: attributes (mime type …) and extensions. important to agree on the standard Descriptors and the SIP Model to have a PAIS Red Book Version (stable version of the Descriptors) important to have a stable XFDU schema

PAIS – October We need ■Version for a PAIS proposed Red Book by a date tbd ■ First version of a tutorial ■Validate the prototype ■To be discussed: actions and planning

PAIS – October