Uploaded image for project: 'Technical Advisory Board'
  1. Technical Advisory Board
  2. TAB-356

2.2 Conformance Targets - ambiguity?

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: Basic Security Profile Version 1.1 CSPRD01
    • Fix Version/s: None
    • Component/s: Public reviews
    • Labels:
      None
    • Environment:

      Conformance

      Description

      2.2 Conformance Targets reads in part:

      *****
      Requirements' conformance targets are physical artifacts wherever possible, to simplify testing and avoid ambiguity.
      *****

      I'm not sure any of the conformance targets are "physical artifacts."

      Did you mean "XML markup artifacts?" Or something similar?

      I don't think "digital" artifacts avoids the problem because there are digital artifacts that aren't testable. Encrypted digital artifacts for example.

      The "whenever possible" language is problematic as well. When would any conformance target not be a markup artifact or processing of a markup artifact? Both of those should be testable. Yes? 3

        Attachments

          Activity

            People

            • Assignee:
              patrick Patrick Durusau
              Reporter:
              patrick Patrick Durusau
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: