[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Groups - TC Call minutes - 2011 07 25.docx uploaded
Most discussion today around concept of Types Registry. o Purpose: Metadata (provided on behalf of SymptomEmitter and Practitioner) to assist in building Syndromes and Protocols. o Should other types be included (SyndromeType & ProtocolType)? Effectively, the Catalog is the place where SyndromeType & ProtocolType are defined. Maybe the Catalog could also be the place where SymptomType & PrescriptionType are defined?? o Should Symptom/PrescriptionType definitions be optional? Without these definitions it would be difficult to author a Syndrome & Protocol, but not impossible. One could do manual analysis of the Symptom Store to understand the content & arguments schema. Ideally the SymptomEmitter and Practitioner would provide these types, but (again) not required. o What does definition look like? SymptomType Type Content schema (xml schema) PrescriptionType Type Argument schema (xml schema) -- Mr. Jeffrey Vaught The document named TC Call minutes - 2011 07 25.docx has been submitted by Mr. Jeffrey Vaught to the OASIS Symptoms Automation Framework (SAF) TC document repository. Document Description: View Document Details: http://www.oasis-open.org/committees/document.php?document_id=42993 Download Document: http://www.oasis-open.org/committees/download.php/42993/TC%20Call%20minutes%20-%202011%2007%2025.docx PLEASE NOTE: If the above links do not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser. -OASIS Open Administration
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]