This wiki has undergone a migration to Confluence found Here
Proposal: create a query mechanism which specifies templates for the response
Revision as of 12:19, 11 August 2010 by Rene spronk (talk | contribs) (New page: ==Summary== *If the receiver of a query is some sort of archive (e.g. an EHR, or a Datamart) which could potentially respond to a query using a response structure that is extremely rich in...)
Summary
- If the receiver of a query is some sort of archive (e.g. an EHR, or a Datamart) which could potentially respond to a query using a response structure that is extremely rich in detail: how does one [the party that sends the query] "limit" the response to a certain more minimalistic subset?
- This proposal seeks to add a new attribute (see discussion section for the class in which it should be added) of type SET<II> to allow the query placer to specify a list of templateIds the response model should be compliant with.
Rejected Alternatives
- The current dynamic model requires that each and every Trigger Event (and hence: Interaction) have exactly one static response model. Thus, if we had 7 level-of-richness templates for a response model, we'd have to define 7 query interactions [all with the exact same static model] and 7 response interactions.
Discussion
- See Harmonization: add QuerySpec.responseTemplateId attribute, this effectively reopens that old discussion.