...
- Andrew commented that he converted the 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. With this tool we can tag up the text and publish it in whatever presentation format we would like, html, etc. We It creates a master document so we can do it in chapters.
Richard asked if we need a spreadsheet format, as the DocBook said that what Andrew showed provides us the potential to manage our re-expression of NIST requirements in a more convenient readable form, and excel has comprehension problems plus management difficulties. He . He asked Andrew to take the document and turn it back to word and produce a line number version for reviewers to look at. Andrew clarified that the version was taken directly from Github, from NIST mark up files and was not taken from word format.
Richard Also, Richard stressed that what Andrew introduced it is a development tool where we can put simple statement statements for CSPs and Assessors that have to meet or determine they have met.
Richard questioned why we want to keep the NIST text if we want to drive a set of criteria of our own. But we arrive we can retain relationship with the original text. Original and Put how we choose drive RW Focus on Creating a criteria