heppenheim producer-archive interface specification status of standardisation project main...

Heppenheim

Producer-Archive Interface Specification

Status of standardisation project

Main characteristics, major changes, items pending

2

PAIS – 01-05 October 2007

Contents

1. Objective

2. Basic principles

3. Main changes

4. Items pending

5. Conclusion

BOUCON:BOUCON:

3


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

4


Basic principles

5


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.

6


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).

7


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 …

8



■XFDU schema: Red Book, January 2007 packageHeader informationPackageMap dataObjectSection metadataSection behaviourSection

9



■XFDU schema: Red Book, January 2007 packageHeader informationPackageMap dataObjectSection metadataSection behaviourSection

■SIP to XFDU Mapping

10


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 ….

}

}

}}

11


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 04 October 05 Sept/Nov 06February 06 June 06

draft White Book versions

1 2 3 4 5/6

■September 2004: concept paper

August 07

7

12


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

13


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


■ 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■ 4.1.2 SIP Content Types Specification■ 4.1.3 SIP sequencing constraints specification■ 4.2 Concrete constraints on types of sips■ 4.2.1 SIP Content Types implementation■ 4.2.2 SIP Sequencing Constraints implementation

■ 5 SIP Model■ 5.1 Abstract SIP Model■ 5.2 Concrete SIP Implementation using XFDU■ 5.2.1 SIP XML schema for XFDU■ 5.2.2 Mapping abstract SIP to XFDU■ 5.2.3 SIP specialization

■ ANNEX A: Transfer Object and Collection Descriptors XML schema

■ ANNEX B : legend for XML figures■ ANNEX C : Informative references

14


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


■ 3.2 Collection Descriptor Specification


■ 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■ 4.1.2 SIP Content Types Specification■ 4.1.3 SIP sequencing constraints specification■ 4.2 Concrete constraints on types of sips■ 4.2.1 SIP Content Types implementation■ 4.2.2 SIP Sequencing Constraints implementation

■ 5 SIP Model■ 5.1 Abstract SIP Model■ 5.2 Concrete SIP Implementation using XFDU■ 5.2.1 SIP XML schema for XFDU■ 5.2.2 Mapping abstract SIP to XFDU■ 5.2.3 SIP specialization

■ ANNEX A: Transfer Object and Collection Descriptors XML schema

■ ANNEX B : legend for XML figures■ ANNEX C : Informative references

15


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?

16


Main changes: Descriptor

■ General structure

17



■ General structure

18



■ Identification

Changed name(and position)

19



■ Description

Changed name

Type definition

20



■ Relations

Type definition changed

21


■ Groups and Data Objects

Main changes

New hierarchical structure

22


■ Groups and Data Objects

Main changes

Name changed

Format reviewed

23


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)

24


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.

25


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)

26


Items pending: PAIS tutorial

1. Overview section1.1 PAIMAS view

2. Requirements for standardization2.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 Procedures4.2 Best practices

5. Conclusion

Annex A: “Complete example”■ Follow one project through all steps■ Full formal spec = MOT + Content Constraints +

Sequencing Constraints■ Several SipsAnnex B: More examples

Plan

27


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

28


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

29


heppenheim producer-archive interface specification status of standardisation project main...

Documents