This resource doesn't seem ready for normative.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Unresolved

      Given the number of serious issues identified, is seems hard to believe that this system has seen serious production use. How many production systems have successfully mapped existing legacy audit information to this resource and interoperably exchanged it? (Systems designed from scratch to use this resource don't count.) Have those systems actually been conformant and mapped all terminologies with extensible bindings? (Ignoring the warnings about extensible and not mapping every code that possibly can be - regardless of how non-exact match - also doesn't count.)

      Even if significant use has been seen, given the number of significant changes needed, I'm not sure that pushing to normative after fixing them is wise without time for more implementation experience.

      (Comment 38 - imported by: Ron G. Parker)

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Lloyd McKenzie, Ron Parker
            Watchers:
            2 Start watching this issue

              Created:
              Updated: