...
- Aakash commented about the excel sheet he sent to the mailing, which is a NIST breakdown for the normative sections of A, B and C, which can be used to further breakdown the guidelines into individual Shall / and Should / May statements.
Document shared by Aakash NIST 800-63 breakdown.xlsx
- Andrew Hughes commented that he converted the raw markdown from Github into DocBook structure (XML-based document structure). He plans to include structural elements into the 63B doc that will allow the group to toggle between "raw" and "Kantara" versions of the requirements. With this tool we can tag the text and publish it in whatever format and the presentation we would like, html, etc.
Richard asked if we need a an format, as we need to be able to manage our re-expression of NIST requirements in a readable form, and excel does not impose comprehension problems plus management difficulties. RW can take back to word. produce line number version to reviewers to look at
Version taken Directly from Github from NIST mark up files NIST. Andrew will convert the text to a file format DocBook, structured document has feature we need. We can do it in chapters. It creates a master doc. With the features we need. RW development tool. simple Statement for CSPs and Assessors that have to meet or determine they have met.