This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Talk:ControlAct level batching"
Jump to navigation
Jump to search
Robert grant (talk | contribs) |
Rene spronk (talk | contribs) (add response) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | I'm having trouble understanding the use case. If I query for a history of prescriptions then it appears that the batch can only return those with the *same* control act metadata, vis: "The container is designed to permit batching of multiple payloads that have the same administrative data (e.g. ControlAct author, etc), whilst allowing error information to be returned for individual items." It seems likely to me that the query response could be incomplete, because some of the requested data would have had different author/overseer/dataenter/information recipient, and therefore could not returned under the same wrapper. Is this correct? And how do I know if a query response is incomplete?[[User:Robert grant|Robert grant]] | + | I'm having trouble understanding the use case. If I query for a history of prescriptions then it appears that the batch can only return those with the *same* control act metadata, vis: "The container is designed to permit batching of multiple payloads that have the same administrative data (e.g. ControlAct author, etc), whilst allowing error information to be returned for individual items." It seems likely to me that the query response could be incomplete, because some of the requested data would have had different author/overseer/dataenter/information recipient, and therefore could not returned under the same wrapper. Is this correct? [[User:Robert grant|Robert grant]] 14:02, 31 Jan 2006 (CST) |
| + | :Good question - the assumption is that mostly the participations on the second-level controlAct will be the same as the partcipations of the root-level controlAct. If not (because of the inheretance mechanism) some partcipations could be specified at the second-level controlAct to overrule the inhereted participation. [[User:Rene spronk|Rene spronk]] 06:11, 1 Feb 2006 (CST) | ||
| + | |||
| + | ---- | ||
| + | |||
| + | And how do I know if a query response is incomplete?[[User:Robert grant|Robert grant]] 14:02, 31 Jan 2006 (CST) | ||
| + | :You don't, you can only check that the interaction is valid from a schema persepctive. The NHS uses some special new classes associated with the root-level controlAct to convey additional information such as the number of second-level controlActs. It has yet to be determined if & how we need to support that kind of information. The current content shows that using a 2-level controlAct mechanism fits with event-replay which is a known v2 use-case. [[User:Rene spronk|Rene spronk]] 06:11, 1 Feb 2006 (CST) | ||
Latest revision as of 12:11, 1 February 2006
I'm having trouble understanding the use case. If I query for a history of prescriptions then it appears that the batch can only return those with the *same* control act metadata, vis: "The container is designed to permit batching of multiple payloads that have the same administrative data (e.g. ControlAct author, etc), whilst allowing error information to be returned for individual items." It seems likely to me that the query response could be incomplete, because some of the requested data would have had different author/overseer/dataenter/information recipient, and therefore could not returned under the same wrapper. Is this correct? Robert grant 14:02, 31 Jan 2006 (CST)
- Good question - the assumption is that mostly the participations on the second-level controlAct will be the same as the partcipations of the root-level controlAct. If not (because of the inheretance mechanism) some partcipations could be specified at the second-level controlAct to overrule the inhereted participation. Rene spronk 06:11, 1 Feb 2006 (CST)
And how do I know if a query response is incomplete?Robert grant 14:02, 31 Jan 2006 (CST)
- You don't, you can only check that the interaction is valid from a schema persepctive. The NHS uses some special new classes associated with the root-level controlAct to convey additional information such as the number of second-level controlActs. It has yet to be determined if & how we need to support that kind of information. The current content shows that using a 2-level controlAct mechanism fits with event-replay which is a known v2 use-case. Rene spronk 06:11, 1 Feb 2006 (CST)
