...
- Andrew commented that he converted the raw markdown from Github into DocBook structure mark up files from NIST that are available in Github to DocBook format (XML-based document structure) and has the features we need. 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 up the text and publish it in whatever presentation format and the presentation we would like, html, etc. We can do it in chapters.
Richard asked if we need a an spreadsheet format, as we need to be able to the DocBook provides us the potential to manage our re-expression of NIST requirements in a more convenient readable form, and excel does not impose has comprehension problems plus management difficulties. RW can take He asked Andrew to take the document and turn it back to word . and produce a line number version to for reviewers to look at Version taken Directly at. Andrew clarified the version was 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
Richard stressed that what Andrew introduced it is a development tool where we can put simple statement for CSPs and Assessors that have to meet or determine they have met.
...