Warnings

[jmcdaniels]

@zsmi do you know what these warnings want changed?

Error: Found a "assignable" element that is buried under stricken text: /PP[1]""/sec:Security_Requirements[1]""/sec:SFRs[1]"The indiv"/section[1]""/f-component[2]""/f-element[1]""/title[1]"The TSF s"/h:s[2]"that meet"/assignable[1]"list of s"

Warning: Detected an empty p element./PP[1]""/sec:Security_Requirements[1]""/sec:SFRs[1]"The indiv"/section[1]""/f-component[10]""/f-element[1]""/note[1]"In accord"/h:p[1]""

[jfisherbah]

The first one refers to FCS_CKM.1/DEK having "[assignment: list of standards]" inside of strikethrough. The warning is probably because we don't want the ST author (or any machine parser) to fill out that assignment with anything because it's struck through as a refinement. Probably the correct thing to do would be to replace the assignable with static text because we never actually intend for that assignment to get filled out (but the struck-out prompt itself should remain human-readable for accuracy w/r/t Part 2).

The second one refers to the <h:p/> element in the app note for FCS_COP.1/Hash. If using a paragraph break (i.e. half-line break) is desired, the best practice is to encase the whole paragraph in a p tag rather than adding a null one at the end. It is my understanding that the latter may be parsed in an unintended way by a browser since there is no universal agreement in HTML for how to render that.

[jmcdaniels]

Thanks Justin, there are a ton of these, if someone has time to fix them then please do. If I find some extra time I will try to fix, but they are non-essential so not going to worry about them if time is not found.