[MOIMS-NAV-EXEC] Request for CCSDS Navigation Standards Normative Annex Registry
Berry, David S (3920)
David.S.Berry at jpl.nasa.gov
Tue Aug 28 21:37:39 UTC 2018
Hi Julien:
Thanks for your response.
Regarding the "Orbit Centers" registry, I understand now about the "References" column. As long as it's OK to have it blank, there is no problem retaining the column. I think you can now finish the "Orbit Centers" registry.
Regarding the "References" registry, I see it in the list of Candidate Registries on the beta site. I guess what would need to be done is to take the references in the file attached here and populate rows in the "References" registry with that information, then associate the references to the rows in the Time Systems registry (for example). Some of the references in our attached file are already in your "References" registry because they are CCSDS documents. Am I understanding this mechanism correctly?
I don't know if Dan Oltrogge's suggestion of housing the actual documents in the SANA is possible or not, but it would be less subject to an ongoing maintenance requirement if you had the actual document instead of just a link to it (which could be easily broken).
I seem to remember there were a few CCSDS documents at the top of the candidate registry you created, but they are not there anymore (?). I think these would be good to have because each Navigation WG registry might be applicable to different CCSDS documents.
For your consideration,
David
On 8/27/18, 7:44 AM, "Space Assigned Numbers Authority" <info at sanaregistry.org> wrote:
David,
We currently have two choices for references. Either we keep them in the
file on top of the registry or we associate them with entries in the
registry.
In the second case (the one of item 2) we need indeed to associate
references with rows but we may have entries without references.
We would need to create a special case for orbit centers registry if we
remove references because references are included in all registries
(except for meta registries in which we hide the column) but we can keep
it empty.
Best regards,
Julien Bernard
Space Assigned Numbers Authority
On 8/24/18 7:24 PM, Berry, David S (3920) wrote:
>
> Julien:
>
> Thanks for the quick updates. I'm not sure I completely understand your statement on item 2 below... "We would need the references to be associated to each entry of the registry in that case." Does that mean we would need to cite a reference for every row in the table? I suppose that's possible. If this is true then I would recommend removing the "References" column from the Orbit Centers Registry.
>
> BTW, we will be sending an additional installment of registries to be included in the "CCSDS Navigation Standards Normative Annexes" registry in the next few weeks.
>
> Thanks again!
> David
>
>
>
>
> On 8/24/18, 12:11 PM, "Space Assigned Numbers Authority" <info at sanaregistry.org> wrote:
>
> Hello David,
>
>
>
> Thanks for your feedback.
>
>
>
> 1. Fixed.
>
>
>
> 2. We have a reference registry that may include your references and be
>
> used to populate the column. We would need the references to be
>
> associated to each entry of the registry in that case.
>
>
>
> 3. Fixed/updated.
>
>
>
> You can get the updated version at
>
> https://beta.sanaregistry.org/r/navigation_standard_normative_annexes.
>
> I used some references chosen randomly (from your list of technical
>
> references) in the time systems entry.
>
>
>
> Best regards,
>
> Julien Bernard
>
> Space Assigned Numbers Authority
>
>
>
> On 8/23/18 4:50 PM, Berry, David S (3920) wrote:
>
> > Hello Julien:
>
> >
>
> > Thanks very much for your email! I see there is good progress... Here is some feedback.
>
> >
>
> > 1. On the top level ("Contents"), capitalize "Registry" in column 4. I'm not sure if we need the "References" column 5, although I see a similar structure in the CCSDS Glossary Registry ( https://sanaregistry.org/r/glossary ) and it's in the mock-up I sent too. You do have the applicable references listed at the top of each sub-registry, so maybe at the top level it's not necessary (?).
>
> >
>
> > 2. In the Time Systems Registry, I think it's OK to remove the two files. We will have the relationships diagram in our Green Book document. Several of the entries in the "Technical References" will apply to this Registry. I wonder if it would be possible to add an additional registry called "Technical References", where each entry in the registry is one of the lines in the "Technical References" file? Then we could populate the "Reference" column in the Time Systems registry with one or more applicable numbers that refer back to the "Technical References" registry? Let me know if I have not conveyed this idea understandably. This way you would not need to keep a file.
>
> >
>
> > 3. In the Orbit Centers Registry, it's not an issue that the color coding could not be supported. I think what you did by putting the corresponding text in a column is fine. In column 6 (Examples), the title has the French spelling... change to "Example". I think "Body Type" is a good column heading for column 7. For column 8, I would add "Mission" to form "Mission Category" as the column heading. For now, the "References" column can remain blank. I suggest removing the "Files: Technical References" from this registry.
>
> >
>
> > Thanks Again Julien!
>
> > David
>
> >
>
> >
>
> >
>
> >
>
> > On 8/22/18, 2:30 PM, "Space Assigned Numbers Authority" <info at sanaregistry.org> wrote:
>
> >
>
> > Hello David,
>
> >
>
> >
>
> >
>
> > We added your material (only a quick overview, not all the data) on our
>
> >
>
> > beta website
>
> >
>
> > (https://beta.sanaregistry.org/r/navigation_standard_normative_annexes).
>
> >
>
> > Could you please review it and come back to us with your
>
> >
>
> > suggestions/remarks?
>
> >
>
> > Some remarks/questions from our side:
>
> >
>
> > - we did not have a way to support the colors and full lines of text
>
> >
>
> > from orbit centers so we added them as columns. What would be the
>
> >
>
> > appropriate title for these columns ?
>
> >
>
> > - on your mock-up you had links to technical references documents in
>
> >
>
> > the registry files. Depending on what you plan to do with the
>
> >
>
> > references, we may directly add the references to the relevant registry
>
> >
>
> > entries instead of providing a file.
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > Best regards,
>
> >
>
> > Julien Bernard
>
> >
>
> > Space Assigned Numbers Authority
>
> >
>
> >
>
> >
>
> > On 6/21/18 10:15 AM, Space Assigned Numbers Authority wrote:
>
> >
>
> > > Hello David,
>
> >
>
> > >
>
> >
>
> > > Thanks for providing us your data. We will come back to you as soon as
>
> >
>
> > > possible if we have any question.
>
> >
>
> > >
>
> >
>
> > > In order to include equations in the registry you can use a format among
>
> >
>
> > > LaTeX, MathML and AsciiMath.
>
> >
>
> > >
>
> >
>
> > > Best regards,
>
> >
>
> > > Julien Bernard
>
> >
>
> > > Space Assigned Numbers Authority
>
> >
>
> > >
>
> >
>
> > > On 2018-06-19 20:11, Berry, David S (3920) wrote:
>
> >
>
> > >>
>
> >
>
> > >> P.S.: I intended to also inquire about any requirements you have for representing equations on the SANA... we have some material that is best presented as equations, and want to make sure that we use the proper format. Julian indicated at our meeting in Gaithersburg that this may be something the SANA team has solved.
>
> >
>
> > >>
>
> >
>
> > >> Regards,
>
> >
>
> > >> David
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> > >> On 6/19/18, 5:08 PM, "Berry, David S (3920)" <david.s.berry at jpl.nasa.gov> wrote:
>
> >
>
> > >>
>
> >
>
> > >> Hello SANA...
>
> >
>
> > >>
>
> >
>
> > >> This email represents the first increment of material that the CCSDS Navigation WG would like to register with the SANA. Once the registries for the material are created, we will be able to start modifying documents to remove annexes that currently contain this material, and refer customers to the SANA for values for the associated keywords. We have discussed this concept with you on a conference call in January 2018 and then discussed with Julian Bernard at the CCSDS Spring Meetings in early April 2018.
>
> >
>
> > >>
>
> >
>
> > >> At this time we are submitting material for a "Time Systems" registry and an "Orbit Centers" registry (attached). We envision a high level registry that is composed of a set of lower level, detailed registries. I have attached a screen print of how the high level registry could be organized, as well as a mock-up of the full structure envisioned; this mock-up was previously provided so you may have already downloaded it and looked at it. The Time Systems and Orbit Centers represent lower level registries number 1 and number 7 of the full set of 8 planned registries. I have also attached a screen shot of a mock-up of how we think the material can best be organized on the SANA. The Working Group is still completing the detail for the remaining registries, and will provide them as we complete them.
>
> >
>
> > >>
>
> >
>
> > >> Please advise if you have any questions, and thanks very much for your support!
>
> >
>
> > >>
>
> >
>
> > >> Regards,
>
> >
>
> > >> David Berry
>
> >
>
> > >> Chair, CCSDS Navigation WG
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> >
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: references.pdf
Type: application/pdf
Size: 83034 bytes
Desc: references.pdf
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180828/c5c46615/attachment.pdf>
More information about the MOIMS-NAV-EXEC
mailing list