c. huc/cnes, d. boucon/cnes-silogic

38
C. Huc/CNES, D. Boucon/CNES-SILOGIC NSSDC Use case analysis NSSDC Use case analysis

Upload: roger

Post on 21-Jan-2016

48 views

Category:

Documents


0 download

DESCRIPTION

NSSDC Use case analysis. C. Huc/CNES, D. Boucon/CNES-SILOGIC. Contents. NSSDC Use Case presentation Model 1 Model 2 Conclusion. NSSDC Use Case Introduction. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: C. Huc/CNES, D. Boucon/CNES-SILOGIC

C. Huc/CNES, D. Boucon/CNES-SILOGIC

NSSDC Use case analysisNSSDC Use case analysis

Page 2: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 2

ContentsContents

NSSDC Use Case presentation

Model 1

Model 2

Conclusion

Page 3: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 3

The NSSDC USC-1 is based on a view of the NSSDC Version 3 Archival Information Package (AIP), which is also used as a Submission Information Package (SIP).

NSSDC is planning to use this particular AIP form to contain muliple data objects (files) along with metadata attributes.

The AIP package is an SFDU structure, with one LVO being a PVL object referred to as the NSSDC Attribute Object (AO).

This use case works back from an AIP to the data and metadata objects contained and referenced therein.

NSSDC Use CaseNSSDC Use CaseIntroductionIntroduction

Page 4: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 4

1. Package Header Attributes Object

2. Multi-stream attributes object

3. Directory Pathname to original Data Object

4. Attributes of corresponding Data Object prior to packaging

5. Attributes of corresponding Data Object after packaging

6. Supplementary attributes of Data Object after packaging

7. Binary Data Object stream

NSSDC Use CaseNSSDC Use CaseInformation ObjectsInformation Objects

Page 5: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 5

NSSDC Use CaseNSSDC Use CaseSIP ContentSIP Content

Z Label K Label PVL AO group label Package Header Attributes Object

PVL Multi-stream group label Multi-stream Attributes Object

PVL stream group label Stream Instance Pointer = 1 Directory Pathname Attributes of corresponding Data Object stream prior to packaging Attributes of corresponding Data Object stream after packaging Supplementary attributes of corresponding Data Object stream PVL stream group end label

PVL Multi-stream group end label PVL AO group end label

U Label Stream Instance Identifier =1 I Label Binary Data Object stream

1..n

1..n

1

2

3 4 5 6

7

Page 6: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 6

NSSDC-Use Case

NSSDC Use CaseNSSDC Use CaseModelsModels

NSSDC-Use Case MODEL 1

NSSDC-Use Case MODEL 2

This model considers the NSSDS package as a whole and as an elementary “Data Object”.

This model considers the science data files

as the granules of the model, and is made up of

a decomposition of the different

NSSDC package elements.

Page 7: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 7

Specification document provides a standard method to

• formally define the digital information objects to be transferred by a Producer to an Archive

• actually transfer these objects in the form of SIPs

ReminderReminder

Page 8: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 8

Formal Definition PhaseStep1: Descriptor Model definition

Step 2: Descriptor Instanciation

Step 3: Slip Model Definition

Step 4: MOT design

Step 5: SIP Model Definition

Transfer PhaseSlip Instanciation

Slips and SIPs transfer

NSSDC Use CaseNSSDC Use CaseGuidelines - stepsGuidelines - steps

Page 9: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 9

NSSDC Use CaseNSSDC Use CaseModel 1Model 1

ROOT

SPMS-00216-CO

SPMS-00216-PKG (N)

COLLECTION_DESCRIPTOR

DO_DESCRIPTORDO_DESCRIPTOR

SPMS-00217-CO

SPMS-00217-PKG (N)

Page 10: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 10

NSSDC Use Case - Model 1NSSDC Use Case - Model 1Step 1: Descriptor Model DefinitionStep 1: Descriptor Model Definition

NSSDC-SE-COLLECTION-DESCRIPTOR

NSSDC-PACKAGE-OBJECT-DESCRIPTOR

Page 11: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 11

Descriptor Model: attributes (meaning, syntax, defined occurrence) to:

– Identify the type of object described.– Define the relations between the objects described and the other

Model objects.– Describe the object content.– Give a name to the Slip Model to be delivered.

ReminderReminder

Page 12: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 12

NSSDC Use Case - Model 1 NSSDC Use Case - Model 1 Step 1: Descriptor Model DefinitionStep 1: Descriptor Model Definition

NSSDC-SE_COLLECTION_DESCRIPTOR

Attribute_name (and value type)

Attribute_definition Attribute_occurrence and condition

Descriptor_type (Constant value)

NSSDC-SE-CO

Descriptor_ID(identifier)

Name of the NSSDC data collection 1..1

Title(text)

1..1

Parent_collection(identifier)

ROOT

Object_occurrence(form m..n)

1..1

Content(text)

1..1

Applicable_slip(identifier)

NONE (nothing to be transferred at this level)

Page 13: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 13

NSSDC Use Case - Model 1 NSSDC Use Case - Model 1 Step 1: Descriptor Model DefinitionStep 1: Descriptor Model Definition

NSSDC-PACKAGE_OBJECT_DESCRIPTOR

Attribute_name (and value type) Attribute_definition Attribute_occurrence and condition

Descriptor_type (Constant value) NSSDC-PKG-DO

Descriptor_ID (identifier) Name of the NSSDC package data

1..1

Title (text) 1..1

Parent_collection (identifier) 1..1

Object_occurrence (form m..n) 1..n

Content (text) 1..1

Applicable_slip (identifier Constant value) NSSDC-PKG-DO-slip

Size 1..1

Format_type Binary

Applicable_metadata_standard (Constant value) Pkg_object_schema.pvl

Packaging_standard (Constant value) SFDU

Page 14: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 14

NSSDC Use Case - Model 1 NSSDC Use Case - Model 1 Step 2: Descriptor InstanciationStep 2: Descriptor Instanciation

NSSDC-SE-collection-descriptor instance

There are many possible instances of this model because there are many different data collections,

Example:

Attribute_nameAttribute_value

Descriptor_type NSSDC-SE-CO

Descriptor_ID SPMS-00216-CO

Title Collection of Magnetometer data

Parent_collection root

Object_occurrence 1..1

Content Collection of the PRIMARY COLLECTION SPMS-00216 data

Applicable_slip NONE

Page 15: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 15

NSSDC Use Case - Model 1 NSSDC Use Case - Model 1 Step 2: Descriptor InstanciationStep 2: Descriptor Instanciation

NSSDC-PACKAGE_OBJECT_DESCRIPTOR INSTANCE

Attribute_nameAttribute_value

Descriptor_type NSSDC-PKG-DO

Descriptor_ID SPMS-00216-PKG

Title SPMS Magnetometer data object level 2

Parent_collection SPMS-00216-CO

Object_occurrence 1..n

Content Each package contains: SPMS-00216 data files accompanied by their metadata

Applicable_slip NSSDC_PKG-DO_slip

Size TBD

Format Type binary

Applicable_metadata_standard Pkg_object_schema.pvl

Packaging_standard SFDU

Page 16: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 16

NSSDC Use Case - Model 1 NSSDC Use Case - Model 1 Step 3: Slip Model DefinitionStep 3: Slip Model Definition

NSSDC-PKG-DO-slip

Page 17: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 17

Slip: A Data Object that conveys information related to another Data Object which is transferred between two entities.

This information will allow the addressee to identify, locate and if needed process the various transferred bit sequences which compose this Data Object.

ReminderReminder

Page 18: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 18

NSSDC Use Case - Model 1 NSSDC Use Case - Model 1 Step 3: Slip Model DefinitionStep 3: Slip Model Definition

NSSDC-TRANSFERRED-PACKAGE-OBJECT-SLIP

Attribute_name (and value type)

Attribute_definition Attribute occurrence and condition

Slip_ID (Identifier Constant value)

NSSDC-PKG-DO-slip

Object_ID (identifier) Object Identifier 1..1

Descriptor_ID (identifier)

Name of the NSSDC package data 1..1

Object_access (identifier)

Composit entity giving access to the various bit sequences in the storage service (see below), in case it’s different from Object_ID.

0..1

Last_object Enumerated (Yes, No)

Flag of last object delivered 1..1

Object_access (identifier)

File_name 1..1

Page 19: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 19

NSSDC Use Case - Model 1 NSSDC Use Case - Model 1 Step 4: MOT DefinitionStep 4: MOT Definition

ROOT

SPMS-00216-CO

SPMS-00216-PKG (N)

SPMS-00217-CO

SPMS-00217-PKG (N)

Page 20: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 20

NSSDC Use Case - Model 1 NSSDC Use Case - Model 1 Step 5: SIP Model DefinitionStep 5: SIP Model Definition

A SIP may contain many packages (coming from different collections).

Attribute_name (and attribute value type)

Attribute_value Attribute occurrence and condition

SIP_ID(identifier)

Identifier of the transferred SIP

1..1

Descriptor_ID(identifier)

Descriptor identifier of the transferred information

objects

1..n

NSSDC_SIP_MULTI-FILE INSTANCE

Attribute_name Attribute_value Attribute occurrence and condition

SIP_ID SIP-00216-00217

Descriptor_ID SPMS-00216-PKG 1..n

Descriptor_ID SPMS-00217-PKG 1..n

Page 21: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 21

NSSDC Use Case - Model 1 NSSDC Use Case - Model 1 Transfer PhaseTransfer Phase

NSSDC_DATA_OBJECT_SLIP INSTANCE

Attribute_name Attribute_name

Slip_ID NSSDC-PKG-DO-slip

Object_ID DD000284

Descriptor_ID SPMS-00216-PKG

object_access File_name DD000284.dat

Last_object No

Page 22: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 22

NSSDC Use CaseNSSDC Use CaseModel 2Model 2

ROOT

SPMS-00216-CO

SPMS-00216-DO (N) NSSDC-PKG-DO (N)

COLLECTION_DESCRIPTOR

DO_DESCRIPTOR

SPMS-00217-CO NSSDC-PKG-Views

SPMS-00217-DO (N)

CCSCS-ADID-CO

ADID-DO (N)

Page 23: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 23

NSSDC Use Case - Model 2NSSDC Use Case - Model 2Step 1: Descriptor Model DefinitionStep 1: Descriptor Model Definition

NSSDC-SE-COLLECTION-DESCRIPTOR

NSSDC-PKG-VIEWS-COLLECTION-DESCRIPTOR

NSSDC-SE-OBJECT-DESCRIPTOR

NSSDC-PKG-OBJECT-DESCRIPTOR

Page 24: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 24

NSSDC Use Case - Model 2 NSSDC Use Case - Model 2 Step 2: Descriptor Model DefinitionStep 2: Descriptor Model Definition

NSSDC-SE-OBJECT_DESCRIPTOR Attribute_name (and value type) Attribute_definition Attribute_occurre

nce and condition

Descriptor_type (Constant value) NSSDC-SE-DO

Descriptor_ID (identifier) Name of the NSSDC science data type 1..1

Title (text) 1..1

Parent_collection (identifier) 1..1

Object_occurrence (form m..n) 1..n

Content (text) 1..1

Applicable_slip (identifier Constant value) NSSDC-data-object-slip

Size 1..1

Format_type Binary

AO_metadata_description Each data object will be accompanied by metadata including : - the data object identifier,The start date, The stop date, …

AO_metadata_schema AO_metadata.pvl

Page 25: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 25

NSSDC Use Case - Model 2 NSSDC Use Case - Model 2 Step 1: Descriptor Model DefinitionStep 1: Descriptor Model Definition

NSSDC-PKG-OBJECT_DESCRIPTOR

Attribute_name (and value type) Attribute_definition Attribute_occurrence and condition

Descriptor_type (Constant value) NSSDC-PKG-DO

Descriptor_ID (identifier) Name of the NSSDC package data 1..1

Title (text) 1..1

Parent_collection (identifier) 1..1

Object_occurrence (form m..n) 1..n

Content (text) 1..1

Applicable_slip (identifier Constant value) NSSDC-PKG-DO-slip

Size 1..1

Format_type ASCII

File1_metadata_schema (Constant value) Pkg_header_metadata.pvl

File2_metadata_schema Multi_stream_metadata.pvl

Page 26: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 26

NSSDC Use Case - Model 2 NSSDC Use Case - Model 2 Step 2: Descriptor InstanciationStep 2: Descriptor Instanciation

NSSDC-SE-OBJECT_DESCRIPTOR INSTANCEOne instance for each science data collection.

Attribute_nameAttribute_value

Descriptor_type NSSDC-SE-DO

Descriptor_ID SPMS-00216-DO

Title SPMS data object level 2

Parent_collection SPMS-00216-CO

Object_occurrence 1..n

Content Each file contains: SPMS-00216 datA and is accompanied by a metadata file

Applicable_slip NSSDC_data_object_slip

Size TBD

Format Type Binary

AO_metadata_description Each data object will be accompanied by metadata including : - the data object identifier,-The start date,-The stop date,-.

AO_metadata_schema AO_metadata.pvl

Page 27: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 27

NSSDC Use Case - Model 2 NSSDC Use Case - Model 2 Step 2: Descriptor InstanciationStep 2: Descriptor Instanciation

Attribute_name Attribute_value

Descriptor_type NSSDC-PKG-DO

Descriptor_ID NSSDC-SE-PKG

Title Science data files package

Parent_collection NSSDC-PKG-Views-CO

Object_occurrence 1..n

Content Each package contains: descriptive metadata

Applicable_slip NSSDC_PKG-DO_slip

Size TBD

Format Type ASCII

File1_metadata_schema Pkg_header_metadata.pvl

File2_metadata_schema Multi_stream_metadata.pvl

NSSDC-PKG-OBJECT_DESCRIPTOR INSTANCE

Page 28: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 28

NSSDC Use Case - Model 2 NSSDC Use Case - Model 2 Step 3: Slip Model DefinitionStep 3: Slip Model Definition

NSSDC-data-object-slip

NSSDC-PKG-DO-slip

Page 29: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 29

NSSDC Use Case - Model 2 NSSDC Use Case - Model 2 Step 3: Slip Model DefinitionStep 3: Slip Model Definition

NSSDC-TRANSFERRED-DATA-OBJECT-SLIP

The elementary science data files and their metadata package are linked via the specific attribute Related_Package_Object_ID.

Attribute_name Attribute_definition Attribute occurrence and

condition

Attribute_value_type

Slip_ID Slip type identifier 1..1 IdentifierConstant value =

NSSDC_data_object_slip

Object_ID Identifier distinguishing on object instance from another 1..1 identifer

Descriptor_ID Descriptor identifier corresponding to this TYPE of object

1..1 identifier

Object_access Composit entity giving access to the various bit sequences in the storage service (see below).

2..2 identifier

Extraction_software Name of the software used to reconstruct the digital object from the bit sequences. (not used in this example Use Case.)

0..1 identifer

AO_metadata_filename Name of the metadata file associated to Object_ID 1..1 identifier

Related_Package_Object_ID

Identifier of the package metadata linked to this Object_ID

1..1 identifier

Last_object Flag of last object delivered 1..1 Enumerated (Yes, No)

Page 30: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 30

NSSDC Use Case - Model 2 NSSDC Use Case - Model 2 Step 3: Slip Model DefinitionStep 3: Slip Model Definition

NSSDC-TRANSFERRED-PACKAGE-OBJECT-SLIP

Attribute_nameAttribute_definition Attribute

occurrence and

condition

Attribute_value_type

Slip_ID Slip type identifier 1..1 IdentifierConstant value =

NSSDC_PKG_DO_slip

Object_ID Identifier distinguishing on object instance from another

1..1 identifer

Descriptor_ID Descriptor identifier corresponding to this TYPE of object

1..1 identifier

Object_access Composit entity giving access to the various bit sequences in the storage service.

2..2 identifier

Page 31: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 31

NSSDC Use Case - Model 2 NSSDC Use Case - Model 2 Step 4: MOT DesignStep 4: MOT Design

ROOT

SPMS-00216-CO

SPMS-00216-DO (N) NSSDC-PKG-DO (N)

SPMS-00217-CO NSSDC-PKG-Views

SPMS-00217-DO (N)

CCSCS-ADID-CO

ADID-DO (N)

Page 32: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 32

NSSDC Use Case - Model 2 NSSDC Use Case - Model 2 Step 5: SIP Model DefinitionStep 5: SIP Model Definition

A SIP may contain many packages, coming from different collections.

Attribute_name (and attribute value type)

Attribute_value Attribute occurrence and condition

SIP_ID (identifier) Identifier of the transferred SIP 1..1

Descriptor_ID (identifier) Descriptor identifier of the transferred information objects

1..n

NSSDC_SIP_MULTI-FILE INSTANCEThis SIP can contain a number of science data files from the SPMS-00216 or SPMS-00217 collections, with their associated metadata package.

Attribute_nameAttribute_value Attribute occurrence

and condition

SIP_ID SIP-00216-00217

Descriptor_ID SPMS-00216-DO 1..n

Descriptor_ID SPMS-00217-DO 1..n

Descriptor_ID NSSDC-SE-PKG 1..m

Page 33: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 33

NSSDC Use Case - Model 2 NSSDC Use Case - Model 2 Transfer Phase: Transfer Phase:

NSSDC-TRANSFERRED-PACKAGE-OBJECT-SLIP INSTANCE

Attribute_name Attribute_name

Slip_ID NSSDC_PKG_object_slip

Object_ID DD000284_PKG

Descriptor_ID SPMS-00216-PKG

Object_access File_name DD000284_pkghdr.pvl

path « unknown » ???

Object_access File_name DD000284_multi_stream.pvl

path « unknown » ???

NSSDC_DATA_OBJECT_SLIP INSTANCEAttribute_name Attribute_name

Slip_ID NSSDC_data_object_slip

Object_ID DD000284_F0001

Descriptor_ID SPMS-00216-DO

object_access File_name DD000284_F0001.dat

path « unknown » ???

object_access File_name DD000284_F0001.pvl

path « unknown » ???

Last_object FALSE

Related_Package_Object_ID DD000284_PKG

Page 34: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 34

One Use Case: not only one model design. Each model has advantages and disadvantages.

– Choice of Descriptors and attributes

Associate transfer information via Slip reference in Descriptors?

– Descriptors and Slips – Independant?

– Only Descriptors and SIPs?

How should we implement and transfer SIPs?

….

ConclusionConclusion

Page 35: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 35

ConclusionConclusion

Reach an Agreement on

– Concepts (Descriptors, Slips, SIPs, sequencing constraints),

– Process.

Page 36: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 36

Page 37: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 37

General principlesGeneral principlesOverall viewOverall view

Formal Definition Phase

Transfer Phase

Transferred Objects in SIPs

4 Specialised Descriptor Models MOT

Des

crip

tor

Sl i

p

Type of Object

Relations in the Model

Transfer information

Object Description

Object

Model of Objects to be Transferred:

SIPs definition

Data Objects, Complementary Data ObjectsCollections, Complementary Collections

4 Generic Descriptor Models

Specialisation

SIPs

OBJECT_IDTRANSFERRED_DO_FILESLAST_OBJECTTRANSFERRED_METADATA_FILES

1 Generic Slip Model

Instantiated Slips and

APPLICABLE_SLIP

Instantiated Descriptor Models

Page 38: C. Huc/CNES, D. Boucon/CNES-SILOGIC

CCSDS Meeting, 12/04/05 Specification for the Formal Definition and Transfer Phase 38

General principlesGeneral principlesOverall viewOverall view

Generic Descriptor Model

Generic Slip Model

Specialised Descriptor Model

Specialised Slip Model

Instantiated Descriptor Instantiated Slip

Attribute = DESCRIPTOR_ID

……

Attribute = APPLICABLE_SLIP

Attribute = SLIP_MODEL_IDAttribute = OBJECT_IDAttribute = DESCRIPTOR_ID……Attribute = TRANSFERRED_FILE

Attribute = DESCRIPTOR_ID

……

Attribute = APPLICABLE_SLIP

DESCRIPTOR_ID = WIND_WAVES_TNR_L2_DATA

……

APPLICABLE_SLIP = TNR_L2_DO

Attribute = SLIP_MODEL_ID = TNR_L2_DO

Attribute = OBJECT_IDAttribute = DESCRIPTOR_ID……Attribute = TRANSFERRED_FILE

SLIP_MODEL_ID = TNR_L2_DO

OBJECT_ID = Wind_waves_tnr_l2_20040610

DESCRIPTOR_ID = WIND_WAVES_TNR_L2_DATA

……TRANSFERRED_FILE = Wind_waves_tnr_l2_20040610.dat

Wind_waves_tnr_l2_20040610.xml

Wind_waves_tnr_l2_20040610