[Sea-sa] Completely revised RASDS++ v2.0 draft

[Shames, Peter M (US 312B)]

Dear SAWG RASDS enthusiasts,

I have just finished hacking my way through the entire RASDS++ draft v2 document.  What has emerged from this, at least in my eyes, is a pretty, new, shiny object.  An Information Object, in fact, of type CCSDS Recommended Practice (draft).

I’ve just uploaded the 11Jan24 draft to the CCSDS CWE, at: https://cwe.ccsds.org/sea/docs/Forms/AllItems.aspx?RootFolder=%2Fsea%2Fdocs%2FSEA%2DSA%2FDraft%20Documents%2FRASDS%20Revisions%202020%2FRASDS%20revisions%20draft%20documents&FolderCTID=0x012000F83FD93BEFF45E4FB5D1769B01CA762F&View=%7BA709F322%2D0E67%2D45C7%2D932D%2DCB78C55CE268%7D

All of the agreed structural and document flow changes to Sections 1-12 have been made.  Almost every figure has been updated.  New text has been added and some old text excised.  Every section has a security piece and the handling of security in RASDS++ is described.  It is (somewhat) trimmer and a lot clearer.  I believe that Section 1-12 are now in pretty good shape and that it is worthy of a read through.  So I am asking that some of you put on your green, editorial, eye shades, sharpen your pencils, and give this a go.  Or use Word with Track Changes on, I’m not of a mind to be fussy if I get your support, in any form.

Still to be done:

  1.  Address any lower level comments that were overlooked in the rush to get this major restructuring done.
  2.  Recover (or re-create) any figures that were borrowed from earlier versions and for which we no longer have originals.
  3.  Perform any needed surgery to the various Annexes that remain (please review and comment).
  4.  Resolve any remaining issues marked in the text.
  5.  Review and update the references .
  6.  Update the Acronym list.
  7.  Update the Terminology list.

This sounds like a lot, and it will still take some time to complete, but I think we are in pretty good shape overall.  Anyone wish to step up and contribute by taking on any of items 5-7?  That would be a huge help.  LMK, I’d really appreciate the help.

However, from my PoV, the best thing any of you, particularly the newbies, could do is to read through the document and tell those of us who are editing it if it makes sense, is clear, is well structured, and, hopefully, useful for the task of systems architecting.

Please.

It’s out there and I’d really like to get some fresh eyes on it.  Soon.

In fact, I’d really like it if any of you who are willing to contribute to pushing this document over the finish line would signal me as to what you plan to do.  Even reading one chapter thoroughly and providing feedback would be a help.

Thanks, Peter

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sea-sa/attachments/20240112/f4b5b74a/attachment.htm>