Problems running Release 1.0.1 of openEHR Java Reference Implementation

2009-10-02 Thread Paul Linehan
Hi to all from Trinity College Dublin,


I'm a student in the university and I'm starting to work on OpenEHR,
so please forgive me if my question(s) is/are newbie ones, or if
I've asked it in the wrong place, please redirect me.

I did check the mailing list archive and could find no discussion
about this problem.


I downloaded the file openehr_ref_impl_java-1.0.1.jar

from

http://www.openehr.org/wiki/display/projects/Java+Project+Download


However, when I tried to run it, I got this

==

@lg12x34:~/wSSproj$ java -jar openehr_ref_impl_java-1.0.1.jar

Failed to load Main-Class manifest attribute from
openehr_ref_impl_java-1.0.1.jar

@lg12x34:~/wSSproj$
===


Further information - java version



linehanp at lg12x34:~/wSSproj$ java -version

java version 1.6.0_02
Java(TM) SE Runtime Environment (build 1.6.0_02-b05)
Java HotSpot(TM) Server VM (build 1.6.0_02-b05, mixed mode)

linehanp at lg12x34:~/wSSproj$
=


Can anyone give me some pointers as to what I'm doing wrong please?


Should you require any further information, please let me know.


TIA and rgs,



Paul...


-- 
linehanp at tcd.ie

Mob: 00 353 86 864 5772



Problems running Release 1.0.1 of openEHR Java Reference Implementation

2009-10-02 Thread Bert Verhees
It is a library, you should write your own software to run it. There
should to be Junit-tests in the repository, you can look at them for
examples how to use the library

good luck
Bert

Op vrijdag 02-10-2009 om 10:45 uur [tijdzone +0100], schreef Paul
Linehan:
 Hi to all from Trinity College Dublin,
 
 
 I'm a student in the university and I'm starting to work on OpenEHR,
 so please forgive me if my question(s) is/are newbie ones, or if
 I've asked it in the wrong place, please redirect me.
 
 I did check the mailing list archive and could find no discussion
 about this problem.
 
 
 I downloaded the file openehr_ref_impl_java-1.0.1.jar
 
 from
 
 http://www.openehr.org/wiki/display/projects/Java+Project+Download
 
 
 However, when I tried to run it, I got this
 
 ==
 
 @lg12x34:~/wSSproj$ java -jar openehr_ref_impl_java-1.0.1.jar
 
 Failed to load Main-Class manifest attribute from
 openehr_ref_impl_java-1.0.1.jar
 
 @lg12x34:~/wSSproj$
 ===
 
 
 Further information - java version
 
 
 
 linehanp at lg12x34:~/wSSproj$ java -version
 
 java version 1.6.0_02
 Java(TM) SE Runtime Environment (build 1.6.0_02-b05)
 Java HotSpot(TM) Server VM (build 1.6.0_02-b05, mixed mode)
 
 linehanp at lg12x34:~/wSSproj$
 =
 
 
 Can anyone give me some pointers as to what I'm doing wrong please?
 
 
 Should you require any further information, please let me know.
 
 
 TIA and rgs,
 
 
 
 Paul...
 
 




License and copyright of archetypes

2009-10-02 Thread Stef Verlinden
Hi Erik,

I see your point and agree. My call for the -SA extension was based on  
the idea of reciprocity. So let's go for CC-BY.

Cheers,

Stef

(I sended this reaction earlier but for an unknown reason only to  
Eric. So now for the whole group. Although I still believe in the idea  
of reciprocity and would like to advocate for it, a license shouldn't  
become a hindrance for the broad usage of openEHR archetypes and/or a  
'paper tiger' as we call it in the Netherlands: don't create rules  
which you can't (or don't want to) follow up)

Op 14 sep 2009, om 12:14 heeft Erik Sundvall het volgende geschreven:

 Requiring SA in addition to BY might add value or it might mostly add
 complications and hard-to-interpet situations regarding what a
 derivative work is. Is data entered using the archetype a derivative  
 work?
 Is a template or screen-form based on the archetype a derivative work?
 Is a book using the archetype in an example a derivative work? A
 specialization of an archetype intended for top-secret medical
 research is most likely a derivative work, is that a problem or not?  
 It
 is issues like these that get companies uneasy regarding using things
 with SA-licencing-schemes (such as GPL) in some situations.

 Another question is if SA is necessary in an openEHR-based health
 record exchange system. If you want to exchange archetyped data you're
 probably in most cases requested to supply the used archetype too
 anyway.