Spec issue list - prioritization attempt

I’ve attempted to prioritize the issue list (for discussion on next TC call):

Red is highest priority.

Yellow medium priority.

Green should be set to resolved or closed.

• Issue 0018: Normalized Notification Mechanism

Jeff - Symptoms delivery would seem to be out-of-scope for the normative spec. We aren't limiting symptoms content to a particular event format (WEF, etc). Not to say we couldn't include examples in a primer.

Recommend closing.

• Issue 0023: Syndrome keywords for semantic matching against Symptom

Jeff - Seems like an implementation detail, ie: to improve performance.

Recommend closing.

• Issue 0030: Scope as a 1st Class Attribute

Jeff - Symptoms are scoped by subject/reporter. Seems like an "executor" might be a good scoping attribute for Prescription.

Recommend leaving open, but bringing up-to-date (as language is outdated).

• Issue 0043: Signature Composition/Decomposition and Partial matches How to represent preventative actions

Jeff - Decomposition of single XQuery signature could prove difficult for Catalog Editors. This might be implementation detail, a Catalog editor may render entirely different pattern representation (google search pattern) which is stored independently with reference to the normative XQuery.

Recommend leaving open for additional discussion.

• Issue 0044: Syndrome resolution triggers