This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Context of Use"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) (new) |
Frankoemig (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | "Context of Use" has been used in the context of HL7 as an equivalent of [[Realm]]. | + | "Context of Use" has been used in the context of HL7 as an equivalent of [[Realm]], but with a slightly different usage: During the discussion in Conformance it was made obvious, that this term has to fulfill additional requirements. This term has been used to reflect these. Unfortunately, they haven't been documented: |
| + | |||
| + | *An Affiliate may have to maintain different scenarios (use cases) which should be kept separate. | ||
| + | *Not every scenario can be kept within the borderlines of a country. | ||
| + | *A scenario may concern different Affiliates in parallel. We have (informally) agreed that one of these Affiliates is declared to be the steward (or the owner) of this scenario. Every change or addition to this "context of use" must be done by this Affiliate. | ||
| + | |||
| + | Pickup up these requirements lead to re-think about the definition of [[Realm]]. The latest discussions in MnM has shown that we can combine both when redefining [[Realm]] considering these requirements. | ||
| + | |||
| + | (In the end it doesn't matter how this child is called as long as the requirements are met.) | ||
Latest revision as of 19:19, 28 June 2006
"Context of Use" has been used in the context of HL7 as an equivalent of Realm, but with a slightly different usage: During the discussion in Conformance it was made obvious, that this term has to fulfill additional requirements. This term has been used to reflect these. Unfortunately, they haven't been documented:
- An Affiliate may have to maintain different scenarios (use cases) which should be kept separate.
- Not every scenario can be kept within the borderlines of a country.
- A scenario may concern different Affiliates in parallel. We have (informally) agreed that one of these Affiliates is declared to be the steward (or the owner) of this scenario. Every change or addition to this "context of use" must be done by this Affiliate.
Pickup up these requirements lead to re-think about the definition of Realm. The latest discussions in MnM has shown that we can combine both when redefining Realm considering these requirements.
(In the end it doesn't matter how this child is called as long as the requirements are met.)
