We already had that kind of premade patterns implemented in the
editor. You can even start creating an archetype with a pattern. But
that's got nothing to do with versioning ;D
2014-10-03 20:54 GMT+02:00 Bert Verhees :
> On 03-10-14 20:27, David Moner wrote:
>
>
>
>>
>>
>> I would incorporate also
org
>
>
> ___
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141003/ad6b6f6f/attachment.html>
--- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141003/5b777801/attachment.html>
ing list
> openEHR-clinical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141003/a639e053/attachment.html>
On 03-10-14 20:54, Bert Verhees wrote:
> To really annoy people, you can refuse to do a save, and force a "save
> as" with an incremented patch-number, also in the internal id.
You can also, when handling files, eat the previous version and save the
archetype with the new version, Except when you
sts.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
------ next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141003/40960b8f/attachment.html>
r.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141003/6c0029a9/attachment.html>
BCS Primary Health Care www.phcsg.org
>
> ___
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
http://www.linkedin.com/in/davidmoner
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia ? 46022 (Espa?a)
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141003/03aa2930/attachment.html>
On 03-10-14 19:26, Ian McNicoll wrote:
> Hi Bert,
>
> I agree that the V is redundant but if we drop it now we just give
> everyone a headache, particularly the tooling people.
>
> However, it would also offer a different solution to Sebastian
> Ionescu's problem. re idfferentiating
>
> i.e a lab
ts.openehr.org
>
--
Dr Ian McNicoll
office / fax +44(0)141 560 4657
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian at freshehr.com
Clinical modelling consultant freshEHR
Director openEHR Foundation
Honorary Senior Research Associate, CHIME, UCL
BCS Primary Health Care www.phcsg.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141003/601e4ce3/attachment.html>
CS Primary Health Care www.phcsg.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141003/7ab39da1/attachment.html>
as ids, as long as it can
translate properly between what it uses internally and what the outside
world uses.
- thomas
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141003/fdbd4fe8/attachment.html>
stinfo/openehr-clinical_lists.openehr.org
>
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
--
Dr Ian McNicoll
office / fax +44(0)141 560 4657
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian at freshehr.com
Clinical modelling consultant freshEHR
Director openEHR Foundation
Honorary Senior Research Associate, CHIME, UCL
BCS Primary Health Care www.phcsg.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141003/e7c7e94d/attachment-0001.html>
gt; Valencia ? 46022 (Espa?a)
> ___
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141003/28161d11/attachment-0001.html>
On 03-10-14 15:45, Thomas Beale wrote:
> the latest rules that Ian and Sebastian have worked out would mean
> that if there was 1.1.3 released, then the next version of that
> archetype if it goes back to development is 1.1.4-unstable, i.e. at
> least the patch number has to be incremented. It c
> Thanks for getting involved in this important discussion. I am on a
> plane and don't have ooportunity for a full answer but it is not as
> simple as u have suggested. Amongst other things You have to consider
> what happens to archetype numbering when the archetype has been
> published and
On 03/10/2014 14:32, Bert Verhees wrote:
>
>> Thanks for getting involved in this important discussion. I am on a
>> plane and don't have ooportunity for a full answer but it is not as
>> simple as u have suggested. Amongst other things You have to consider
>> what happens to archetype numbering
gt; In Danish they say "udgave", in Russian it is "??", in Hebrew:
> "", in Arabic: "", in Maori: "putanga" and in Chinese: "??"
>
> Wonderful tool, Google translate ;-)
-- next part --
An HTML a
On 03-10-14 11:01, Diego Bosc? wrote:
> it's also 'versi?n' in spanish ;)
Spanish is a Latin-language
;-)
>
> 2014-10-03 10:15 GMT+02:00 Bert Verhees :
>> On 03-10-14 01:36, Bert Verhees wrote:
>>> org.openehr:openehr-ehr-composition.something:1.0.0
>>
>> It seems wise to me to not regard the ve
me.upv.es
> http://www.linkedin.com/in/davidmoner
>
> Universidad Polit?cnica de Valencia (UPV)
> Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
> Valencia ? 46022 (Espa?a)
>
>
> ___
> openEHR-clinical mailing list
Hi Bert
Thanks for getting involved in this important discussion. I am on a plane and
don't have ooportunity for a full answer but it is not as simple as u have
suggested. Amongst other things You have to consider what happens to archetype
numbering when the archetype has been published and goe
o ITACA
http://www.ibime.upv.es
http://www.linkedin.com/in/davidmoner
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia ? 46022 (Espa?a)
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141003/15177336/attachment.html>
it's also 'versi?n' in spanish ;)
2014-10-03 10:15 GMT+02:00 Bert Verhees :
> On 03-10-14 01:36, Bert Verhees wrote:
>>
>> org.openehr:openehr-ehr-composition.something:1.0.0
>
>
> It seems wise to me to not regard the version-indication as a part of the
> archetypeId, the same for the namespace.
On 03-10-14 01:36, Bert Verhees wrote:
> org.openehr:openehr-ehr-composition.something:1.0.0
It seems wise to me to not regard the version-indication as a part of
the archetypeId, the same for the namespace.
The archetypeId is to indicate what the conceptual contents of the
archetype is about.
a the initial major version.
> >>
> >>
> >> well I think its a bigger danger, given the level of reuse of CKM
> >> archetypes, that the version ids wouldn't correct reflect the state of
> the
> >> archetypes. We could in theory revert everything that is not published
> to
> >> v0
> >> right now, and i guess that is breaking the rules for less time. But
> there
> >> are still some dozens of fully reviewed and published archetypes that
> have
> >> to retain their v1.x version anyway. So I think the only question is to
> do
> >> with the industry sprint archetypes. How about doing this:
> >>
> >> mark archetypes that have never been 'published' and are not in the
> >> industry
> >> sprint as v0.5.0
> >> mark the industry sprint archetypes as v1.0.0-unstable
> >> leave currently published archetypes on v1.x, i.e. where they are today.
> >>
> >> If I receive a copy of archetypes marked like that in say the GitHub
> >> mirror,
> >> or through a different CKM, I don't need any further education, it's
> >> obvious
> >> what's going on.
> >>
> >> - thomas
> >>
> >>
> >>
> >> ___
> >> openEHR-clinical mailing list
> >> openEHR-clinical at lists.openehr.org
> >>
> >>
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
> >>
> >>
> >>
> >>
> >> ___
> >> openEHR-technical mailing list
> >> openEHR-technical at lists.openehr.org
> >>
> >>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
> >>
> >>
> >> --
> >>
> >> Dr. Sebastian Garde
> >> Dr. sc. hum., Dipl.-Inform. Med, FACHI
> >> Ocean Informatics
> >>
> >> Skype: gardeseb
> >>
> >>
> >> ___
> >> openEHR-technical mailing list
> >> openEHR-technical at lists.openehr.org
> >>
> >>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
> >>
> >>
> >>
> >> ___
> >> openEHR-technical mailing list
> >> openEHR-technical at lists.openehr.org
> >>
> >>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
> >
> > ___
> > openEHR-clinical mailing list
> > openEHR-clinical at lists.openehr.org
> >
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
> >
> > ___
> > openEHR-clinical mailing list
> > openEHR-clinical at lists.openehr.org
> >
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>
> ___
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
--
*This e-mail message is intended exclusively for the addressee(s). Please
inform us immediately if you are not the addressee.*
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141003/63fba53f/attachment-0001.html>
25 matches
Mail list logo
