OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

saf message

[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?  
	Content schema (xml schema)
	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:

Download Document:  

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]