Implement relaton-ccsds for www.ccsds.org Standards

[ronaldtse]

CCSDS is the SDO on space standards.

CCSDS publishes the following types of standards:

• CCSDS Recommended Standards (Blue Books)
• CCSDS Recommended Practices (Magenta Books)
• CCSDS Informational Reports (Green Books)
• CCSDS Experimental Specification (Orange Books)
• CCSDS Record documents (Yellow Books)

Then they have retired documents called:

• CCSDS Historical designation (Silver Books)

Metadata of all publications is available from this page (set to "Show ALL") (only missing retired documents):

• https://public.ccsds.org/Publications/AllPubs.aspx

Silver Books are available from:

• https://public.ccsds.org/Publications/SilverBooks.aspx

Now, being a "Silver Book" we need to work out what type of document it originally was. Luckily, the CCSDS identifiers tell us exactly what type of document it was.

e.g.

• "CCSDS 100.0-G-1-S" the "G" indicates that it was a "Green Book", i.e. "Informational Report".
• "CCSDS 101.0-B-1-S" is a "B" so it was a "Blue Book", i.e. "Recommended Standard".

The metadata of each entry includes:

• PubId: CCSDS 141.1-M-1
• Title: Atmospheric Characterization and Forecasting for Optical Link Operations
• Document type: Magenta Book
• Issue number / Edition: 1
• Publication date: 2022-01
• Description: This Recommended Practice provides a set of recommendations to facilitate interagency collection of atmospheric data and characterization of atmospheric parameters that affect space-to-ground free-space optical communications.
• Working Group: SLS-OPT
• Document link: https://public.ccsds.org/Pubs/141x1m1.pdf

Some Blue Books have links to ISO:

• ISO Equivalent: 15887 (i.e. "ISO 15887"), with link

Some documents are Corrigenda:

• PubId: CCSDS 123.0-B-2 Cor. 2
• Issue Number: 2 Cor. 2
• We need to create a relation back to the document to be corrected (i.e. "CCSDS 123.0-B-2")

Some documents require patent licensing:

• IPR: Patent Licensing. (with https link)

CCSDS documents are further grouped into Areas:

• Space Internetworking Services (SIS)
• Mission Ops. And Information Management Services (MOIMS)
• Spacecraft Onboard Interface Services (SOIS)
• System Engineering (SE)
• Cross Support Services (CSS)
• Space Link Services (SLS)

The area of a document can be known by the responsible Working Group. e.g. "MOIMS-NAV" means the "MOIMS" area in the "NAV" working group.

The full list of working groups is available here: https://cwe.ccsds.org/default.aspx

Within each area there are:

• Working Groups (WG)
• Birds of a Feather (BOF)
• Special Interest Groups (SIG)

Groups (above Areas):

• CCSDS Management Council (CMC)
• CCSDS Engineering Steering Group (CESG)

Areas:

• Systems Engineering Area (SEA)
  • Systems Architecture Working Group (SEA-SA)
  • Security Working Group (SEA-SEC)
  • Delta-DOR Working Group (SEA-D-DOR)
  • Time Management Working Group (SEA-TIME)
• Mission Operations and Information Management Services Area (MOIMS)
  • Data Archive Interoperability Working Group (MOIMS-DAI)
  • Navigation Working Group (MOIMS-NAV)
  • Spacecraft Monitor and Control Working Group (MOIMS-SM&C)
  • Mission Planning & Scheduling Working Group (MOIMS-MP)
• Cross Support Services Area (CSS)
  • Service Management Working Group (CSS-SM)
  • Transfer Services Working Group (CSS-CSTS)
  • Cloud Computing Birds of a Feather (CSS-CLOUD)
• Spacecraft Onboard Interface Services Area (SOIS)
  • Application Support Services Working Group (SOIS-APP)
  • Onboard Wireless Working Group (SOIS-WIR)
  • Subnetwork Services Working Group (SOIS-SUBNET)
• Space Link Services Area (SLS)
  • RF Modulation Working Group (SLS-RFM)
  • Space Link Coding and Synchronization Working Group (SLS-C&S)
  • Data Compression Working Group (SLS-DC)
  • Space Link Protocols Working Group (SLS-SLP)
  • Space Data Link Layer Security Working Group (SLS-SEA-DLS)
  • Optical Communications Working Group (SLS-OPT)
• Space Internetworking Services Area (SIS)
  • Motion Imagery and Applications Working Group (SIS-MIA)
  • Delay Tolerant Networking Working Group (SIS-DTN)
  • Voice Working Group (SIS-VOICE)
  • CCSDS CFDP Revisions Working Group (SIS-CFDPV1)

What we need to do:

• Create relator-model-ccsds to encode these items
• Create pubid-ccsds to parse these pubids
• Create and build a relaton-data-ccsds repository to make these documents citable.

[ronaldtse]

Users are:

• https://github.com/metanorma/iso-14812/issues/5
• https://github.com/geolexica/isotc204-glossary/issues/17

[CAMOBAP]

Boilerplate was generated to add CI

[andrew2net]

@ronaldtse do we need to store in our data-model full area names, i.e. "Mission Operations and Information Management Services", or just an abbreviation, i.e. "MOIMS"?

[andrew2net]

Some Blue Books have links to ISO:

@ronaldtse how should we process the ISO links? Are they relations? If they are, what type are the relations? Maybe they are link. If so, what type are they?

[ronaldtse]

@ronaldtse do we need to store in our data-model full area names, i.e. "Mission Operations and Information Management Services", or just an abbreviation, i.e. "MOIMS"?

Yes, because the reading software would likely not have this information, and become unable to render the name.

Some Blue Books have links to ISO:

@ronaldtse how should we process the ISO links? Are they relations? If they are, what type are the relations? Maybe they are link. If so, what type are they?

(Remember historic items "Silver Books" can also be "retired Blue Books" and therefore have an ISO equivalent)

These ISO documents are Blue Books adopted by ISO, meaning that they are the Relaton adoptedBy:equivalent relationship (https://www.relaton.org/specs/model/relations/).

[andrew2net]

@ronaldtse It seems the spec https://www.relaton.org/specs/model/relations/ diverges from the grammar. I think we can use adoptedAs in this case, do we? What does equivalent means in adoptedBy:equivalent?

[ronaldtse]

The Relaton model is the authoritative source. The grammar is supposed to derive from it.

"equivalent" means it is a document that is meant to do the same thing. Yes, the Relaton relations of adoptedFrom or adoptedAs (different directions) are the correct relations.

[andrew2net]

@ronaldtse I'm sure we need only one direction adoptedAs since the relation to another dataset. See example.

[ronaldtse]

@andrew2net yes only one direction: CCSDS standard "adoptedAs" ISO standard. Thanks. Can we close this now?

[andrew2net]

Yes, closing.

[ronaldtse]

Thank you @andrew2net !