openEHR artefact namespace identifiers

2011-04-08 Thread Diego Boscá
That we are very cautious about reference model version changes doesn't mean that any other organization does the same. Look at HL7 v2 v3 for example ;) 2011/4/8 Thomas Beale thomas.beale at oceaninformatics.com: On 07/04/2011 12:07, David Moner wrote: Dear Thomas, I agree with your general

openEHR artefact namespace identifiers

2011-04-07 Thread Thomas Beale
On 05/04/2011 19:16, David Moner wrote: Hello, I like that approach regarding namespaces, it will be needed sooner than later. Related to archetype identifiers there is another problem still to be solved. How they deal with RM evolutions? Current openEHR RM release is 1.0.2 but it can

openEHR artefact namespace identifiers

2011-04-07 Thread pablo pazos
...@oceaninformatics.com To: openehr-technical at openehr.org Subject: Re: openEHR artefact namespace identifiers On 05/04/2011 19:16, David Moner wrote: Hello, I like that approach regarding namespaces, it will be needed sooner than later

openEHR artefact namespace identifiers

2011-04-07 Thread David Moner
Dear Thomas, I agree with your general approach, but you miss two important things. 1. If openEHR spreads, you cannot expect that all implementations will be always up-to-date. That means that just upgrading the version number of the archetype will not be enough for a system to automatically

openEHR artefact namespace identifiers

2011-04-07 Thread Thomas Beale
On 07/04/2011 12:07, David Moner wrote: Dear Thomas, I agree with your general approach, but you miss two important things. 1. If openEHR spreads, you cannot expect that all implementations will be always up-to-date. That means that just upgrading the version number of the archetype will

openEHR artefact namespace identifiers

2011-04-07 Thread David Moner
2. Archetypes are not only for openEHR. We must always have in mind that other reference models can be used with their own life-cycle that could be not so fine-grained as in openEHR. For example, we are now creating HL7 CDA R2 archetypes but during this year it is expected CDA R3 to be

openEHR artefact namespace identifiers

2011-04-06 Thread Diego Boscá
Also, some of the restrictions of the identifier name seem arbitrary, like minimum number of characters or what characters can you put. 2011/4/6 David Moner damoca at gmail.com: Hello, I like that approach regarding namespaces, it will be needed sooner than later. Related to archetype

openEHR artefact namespace identifiers

2011-04-06 Thread michael.law...@csiro.au
openehr-technical at openehr.orgmailto:openehr-technical at openehr.org Date: Wed, 6 Apr 2011 01:51:05 +1000 To: For openEHR technical discussions openehr-technical at openehr.orgmailto:openehr-technical at openehr.org Subject: openEHR artefact namespace identifiers Hi, About a year ago Thomas

openEHR artefact namespace identifiers

2011-04-06 Thread Erik Sundvall
Hi! On Tue, Apr 5, 2011 at 17:51, Ian McNicoll Ian.McNicoll at oceaninformatics.com wrote: artefact identification proposals at http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/knowledge_id_system.pdf ... se.skl.epj::openEHR-EHR-EVALUATION.problem.v1 ...Then

openEHR artefact namespace identifiers

2011-04-05 Thread Ian McNicoll
Hi, About a year ago Thomas published a draft of some detailed artefact identification proposals at http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/knowledge_id_system.pdf to help with the rapidly approaching scenario of having to cope with similarly named artefacts