[MOIMS-NAV-EXEC] SANA Registry Mockup for Navigation Standards Annexes

[Marc Blanchet]

Hello,
  thanks for the mockup. Registries have been made up to now to hold 
simple data (numbers, strings) in a database. There were not intended to 
have rich format with graphics, equations, etc… Therefore, the 
question is not about a mockup in html, as we are not delivering the 
registries as html pages. We also provide an API therefore the data also 
has to be correctly formatted and defined for API access.
  We will be looking into this. In the mean time, we can support basic 
entries and then update the entries as we are adding more rich format 
objects.

  BTW, if you want to meet, one of us will be at the next CCSDS meeting 
on thrusday and friday.

Marc.

On 3 Mar 2018, at 12:20, Berry, David S (3920) wrote:

> Marc & Company:
>
> As you may recall, the SANA Operator and the CCSDS Navigation Working 
> Group teleconferenced on 31-Jan-2018 regarding our identification of 
> the need to define certain kinds of data that could usefully be placed 
> in a SANA registry instead of in formal, infrequently updated 
> documents. Such data is currently defined in a variety of annexes to 
> CCSDS Blue Books authored by the CCSDS Navigation WG. During our 
> teleconference we informally proposed a registry for the purpose of 
> migrating information in these annexes to a Local/WG Registry under 
> the auspices of the SANA.
>
> Per the process documented in the "Procedures for SANA Registry 
> Specification" CCSDS 313.2-Y-1, we now formally propose such a 
> registry as there is no current registry that meets the identified 
> need or can be adapted to meet the need. Our proposed registry name is 
> "CCSDS Navigation Standards Normative Annexes", but this is not a hard 
> requirement. We are open to a different name if there is a better one 
> based on your expertise with the registry system.
>
> In order to better illustrate our concept, I have attached a mockup of 
> the proposed registry in Unix tar file format. It is similar in 
> structure and function to those of some existing annexes, e.g., the 
> CCSDS Glossary registry https://sanaregistry.org/r/glossary or the 
> Roles registry https://sanaregistry.org/r/roles . You can "install" 
> the mockup by issuing the command "tar xvf SANA-annex-mockup.tar" from 
> the unix command line. The top page of the registry in the mockup is 
> "index.html"; if you display this in a browser it will link to the 
> other pages in the mockup. NOTE: There are a lot of "pictures" here, 
> i.e., not active links as are available in an actual registry, but I 
> think it serves to show the nature of our concept. It is also only a 
> subset of the actual entries in any of the given annexes; again, to 
> illustrate the concept, only a small subset was selected for each of 
> the lower level registries. I manufactured OID numbers, but the one 
> level that would be assigned by SANA I indicated with an "X".
>
> We are hoping that this mockup serves to illustrate our concept, and 
> how closely it conforms to the nature and purpose of some existing 
> registries in the SANA. We are still working to finalize our planned 
> content, and hope to get a "green light" to move forward from the SANA 
> Operator in the near future. From 313.2-Y-1 I understand that we may 
> need to create a CCSDS Yellow Book to document this new registry; when 
> we have approval from the SANA Operator we will proceed to create such 
> a resource.
>
> Please advise your thoughts on our proposal...
>
> Best Regards,
> David Berry
> Chair, CCSDS Navigation WG
>
> P.S.:  There is one of our lower level registries that may be more 
> appropriate as material to be added to the CCSDS Glossary, 
> specifically, the "Attitude & Spacecraft Conventions" registry. I have 
> placed this one at the end of our list of registries due to this 
> different nature. All of the other lower level registries contain 
> values for keywords in our standards, but this last one has material 
> that is more oriented towards a glossary of terms.