On Friday, September 04, 2015 18:55:02 Ian McNicoll wrote:
> However, your use of 'proprietary' in this context is highly misleading,
> particularly as it applies to phrases like 'proprietary standards' or
> 'proprietary specifications'.
>
> I could equally use the phrase 'proprietary specificatio
Hi Bert,
My primary concern was to establish that the use of 'proprietary' in the
context of openEHR, particularly in the context of specifications /
archetypes but also in terms of governance, gives the impression (perhaps
unintended), that
a) the specifications and archetypes are licensed usin
Hi!
ND on the specification documents is not a big or urgent problem if there
are Apace 2 licenced computable artifacts like UML-files/descriptions of
all classes, ADL/AQL grammars, openEHR term lists/vocabularies and other
things needed for building actual systems. I believe that is already the
c
Hi Dave,
This has been fixed now - please have a look in case there are any problems.
Regards
Sebastian
On 03.09.2015 17:23, Sebastian Garde wrote:
Hi Dave and all,
This is the Java XML Serialiser generating XML from ADL on the fly in
the CKM.
The archetype editor is doing it "your" way as
Hi Ian, thanks for your answer.
I do not completely agree
> My primary concern was to establish that the use of 'proprietary' in the
> context of openEHR, particularly in the context of specifications /
> archetypes but also in terms of governance, gives the impression (perhaps
> unintended), th
Hi Ian, thanks for your answer.
I do not completely agree
> My primary concern was to establish that the use of 'proprietary' in the
> context of openEHR, particularly in the context of specifications /
> archetypes but also in terms of governance, gives the impression (perhaps
> unintended), th
Sorry for sending it twice, that was an accident
Bert
On 08-09-15 16:52, Bert Verhees wrote:
Hi Ian, thanks for your answer.
I do not completely agree
My primary concern was to establish that the use of 'proprietary' in the
context of openEHR, particularly in the context of specifications /
On 08/09/2015 21:55, Erik Sundvall wrote:
Hi!
ND on the specification documents is not a big or urgent problem if
there are Apace 2 licenced computable artifacts
like UML-files/descriptions of all classes, ADL/AQL grammars, openEHR
term lists/vocabularies and other things needed for building
8 matches
Mail list logo