[CESG] SEA-R-2015-11-002 Request for CESG Review of the SANA re-engineering documents

[Shames, Peter M (312B)]

Dear Secretariat.

Please begin the process to create a poll for CESG and then CMC approval of the documents for the SANA Re-Engineering effort.  There are three documents involved in this:

  1.  SANA - Role, Responsibilities, Policies, and Procedures, CCSDS 313.0-y-1.1, revision
  2.  SANA Registry Management Policies, CCSDS 313.1-Y-0.1, proposed new policy
  3.  Procedures for SANA Registry Specification, CCSDS 313.2-Y-0.1, proposed new WG procedure

The drafts of the three documents are attached.  They have been formatted by the CCSDS Chief Tech Editor but they will need some final tweaks (minor language edits and figure alignment) before they can be sent out for review.

Thanks, Peter


==========================================================================

SEA-R-2015-11-002  Request for CESG Review of the SANA re-engineering documents
--------------------------------------------------------------------------------

The System Engineering Area,

CONSIDERING that:

The SANA Steering Group (SSG) has analyzed the set of registries in the SANA, and the related procedures, and identified a number of issues:

  1.  Overlapping organization and person registry definitions
  2.  No requirements for WG to re-use or extend existing registries where that is possible
  3.  Poorly specified registry structures (in some cases)
  4.  Lack of unique identifiers for registered objects

AND that:

The SSG has produced a revised SANA - Role, Responsibilities, Policies, and Procedures, CCSDS 313.0-Y-1.1 that remedies these issues; by specifically:

  1.  Adding references to key Enterprise Registries for Organizations, Persons, and Object Identifiers;
  2.  Describing the process for WG to follow in creating or modifying registries that working with the SANA Operator;
  3.  Adding a description of an Expert Group, such as the XML Expert Group, for registries that require such management;
  4.  Adding a specific requirement for on-line, programmatic, accessibility to SANA registries using HTTP/REST; and
  5.  Updating the SANA Considerations section and registry examples.

AND that:

The SSG has produced a draft SANA Registry Management Policies (RMP), CCSDS 313.1-Y-0.1, that further remedies these issues; by specifically:

  1.  Defining the key Enterprise Registries for Organizations, Persons, and Object Identifiers;
  2.  Defining the key Global Registries for OIDs, XML, and others;
  3.  Defining explicitly the information models for these different data types and the relationships among them;
  4.  Specifying in detail the design of these registries, how the databases relate, and policies for using, updating, and extending them;
  5.  Providing an explicit procedure for WG to follow in creating new registries that includes evalauation of existing ones; and
  6.  Providing a process for WG to propose additions or extensions rather than creating new, unique, registries.

AND that:

The SSG has produced draft Procedures for SANA Registry Specification, CCSDS 313.2-Y-0.1, that aligns with the SANA YB and the RMP by:

  1.  Providing WG chairs with a clear and simple procedure that they can use as a practical guideline;
  2.  Providing an overview of the WG workflow;
  3.  Providing a simple set of process steps for the WG chair to follow; and
  4.  Recommending working with the SANA Operator at the earliest opportunity.

AND RECOGNISING that:

The CCSDS Policies for publishing documents requires a CESG Poll and CMC approval for Yellow Books that are normative on CCSDS (Sec 6.1.6).

RESOLVES to request:

That the Secretariat create the necessary polls for the CESG, and then the CMC, to review, approve, and publish the three new and revised documents, CCSDS 313.0-Y-1.1, CCSDS 313.1-Y-0.1 and CCSDS 313.2-Y-0.1.

And NOTES that the related set of proposed updates to the SCID Blue Book, CCSDS 320x0b, will be processed separately by the SEA SSG and that any other documents relating to registries will be aligned with these new procedures when the documents are reviewed for re-confirmation, or sooner if the WG desires to do so.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20151116/14021177/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 313x0y11_working_markup-v1.doc
Type: application/msword
Size: 165376 bytes
Desc: 313x0y11_working_markup-v1.doc
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20151116/14021177/attachment.doc>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 313x1y01_markup-v1.doc
Type: application/msword
Size: 1052160 bytes
Desc: 313x1y01_markup-v1.doc
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20151116/14021177/attachment-0001.doc>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 313x2y0_working-SEA.doc
Type: application/msword
Size: 114176 bytes
Desc: 313x2y0_working-SEA.doc
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20151116/14021177/attachment-0002.doc>