On 01/02/2012 07:25, Erik Sundvall wrote:
On Tue, Jan 31, 2012 at 14:42, Thomas Beale
thomas.beale at oceaninformatics.com
mailto:thomas.beale at oceaninformatics.com wrote:
Erik,
which file do you mean here? Where is this alias?
Oh, never mind, it was just a sidetrack, focus
Erik,
I suspect the only tools using this are the Ocean Template Designer in its
Operational Template XML output which extends the release 1.0.x AOM. This
is only the second time I have presented this proposal, last time we had
this same discussion it got no traction.
The CKM uses the Ocean OPT
Hi Erik,
No problem with your RDF approach but I agree with Thomas that the purpuse
of view directives. (or more generally, program directives) is very
different from annotations. XML Schema separates these two concepts.
Ocean has reused annotations in the template designer for these kind of
Heath
From: openehr-technical-boun...@openehr.org
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of Thomas Beale
Sent: Monday, 30 January 2012 11:52 PM
To: openehr-technical at openehr.org
Subject: pass_through and implementation directives in general
On 30/01/2012 03:16, Heath
Hi!
Ok, if implementation experience says it is better to have separate
sections for human readable annotations and machine-targeted program
directives then I guess that is a good approach. Are there any tools that
support this now?
If going for an RDF-like URI based approach for program
On 31/01/2012 11:15, Erik Sundvall wrote:
Hi!
Ok, if implementation experience says it is better to have separate
sections for human readable annotations and machine-targeted program
directives then I guess that is a good approach. Are there any tools
that support this now?
well not
On 31/01/2012 00:16, Heath Frankel wrote:
Hi Thomas,
I think you're going too far with this controlled key and syntax
approach. The important thing at this point is we get a structure
that we can start using to get more experience with. Although my
proposal was a simple property value
On 31/01/2012 13:12, Erik Sundvall wrote:
Hi!
On Tue, Jan 31, 2012 at 13:44, Thomas Beale
thomas.beale at oceaninformatics.com
mailto:thomas.beale at oceaninformatics.com wrote:
If going for an RDF-like URI based approach for program
directives or implementation_directives then
On 30/01/2012 03:16, Heath Frankel wrote:
Hi Pablo,
If I understand correctly, the pass_through attribute is only for data
displaying on a screen (as you mention the use for data grouping or
collapsing). If that's right, I don't think that should be part of the
generic template
Please rewind to
http://www.openehr.org/mailarchives/openehr-technical/msg05530.html and the
followup messages in that thread.
Using an RDF like URI-based approach still seems to be an option. No
registering hassle or new sections in adl, just alternate use of the
existing annotation section.
//
Hi Erik,
your examples are:
annotations =
[/data/items[at0003.7]/items[at0010]] =
items =
[GUI-show-if] = $smoker -- Other annotation name examples:
GUI-hide-if ...
[some other annotation] = whatever
...with RDF-like annotations, some additional examples (and a wildly
11 matches
Mail list logo
