In that respect: what was the outcome of the OHF in Germany, in which  
an openEHR component proposal should be made?

Cheers,

Stef
------------------
Agenda for OHF meeting, Friday Oct 13th 2006   8:00 am - Noon


Location:
   Neckar Forum (Best Western Premier Hotel Park)
   Grabbrunnenstr. 19, 73728
   Esslingen Germany


Chair: Grahame Grieve


1. Introductions & Welcome (10 min)


2. Agenda review (5 min)


3. OHF Project Review (30 min)


4. OHF Q&A, OHF & Europe (30min)


5. Component update - WADO (Yossi) (15min)


6. break (20 min)


7. OpenEHR component proposal (75 min)
    some specific questions which will be considered:
     - how do OpenEHR components relate to other components?
     - what support for development does Eclipse offer?
       + what will be useful for OpenEHR?
     - what does it mean to be "in eclipse"?
     - how much OpenEHR related code is welcome in Eclipse?
       + how much should be in Eclipse?
     - what about non-java OpenEHR code?


8. Architecture & HSSP Services (45 min)
    - discussion of OHF architectural planning


9. Meeting Summary & Planning for next meeting (5min)




Op 10-jul-2007, om 9:00 heeft Yampeku het volgende geschreven:

> Well, in fact OHF is EPL not GPL
>
> http://www.eclipse.org/legal/eplfaq.php
>
> 2007/7/10, Ignacio Valdes <ivaldes at hal-pc.org>:
>> With little investigation into this and perhaps opening my mouth
>> prematurely, it sounds like Microsoft's answer to IBM's Open
>> Healthcare Framework (OHF) initiative. OHF is GPL I believe.
>>
>> -- IV
>>
>> On 7/9/07, Andrew Patterson <andrewpatto at gmail.com> wrote:
>>>> Open-source or just "open"? What are the licensing arrangements  
>>>> for the
>>>> Microsoft/NHS Common Health Interface controls? Obviously they  
>>>> depend on
>>>> the Microsoft .NET platform (do they also work with Mono?), but are
>>>> there additional licensing restrictions or limited access to the  
>>>> Common
>>>> Health Interface controls themselves?
>>>
>>> This is what I had to sign up to when I registered ages ago.. in  
>>> brief,
>>> no to open source (3.4.2.3.4) and no to mono (3.4.1) - I presume  
>>> this
>>> is the same site from which the common control stuff would
>>> come.
>>>
>>> https://www.cui.nhs.uk/Pages/NHSCommonUserInterface.aspx
>>>
>>> ---
>>> 3.4 Use Rights
>>> 3.4.1 Use: You may install the software on any number of devices to
>>> design, develop and test your programs that run on a Microsoft  
>>> Windows
>>> operating system.
>>> 3.4.2 Distributable Code: The software contains code that you are
>>> permitted to copy and distribute in programs you develop if you  
>>> comply
>>> with the terms below:
>>> 3.4.2.1 Right to Use and Distribute. The code and text files listed
>>> below are "Distributable Code". You may:
>>> 3.4.2.1.1 REDIST.TXT Files. Copy and distribute the object code form
>>> of code listed in REDIST.TXT files;
>>> 3.4.2.1.2 Sample Code: Modify the source code form of Sample Code  
>>> for
>>> the sole purpose of designing, developing and testing your programs,
>>> and copy and distribute the object code form of your modified files;
>>> 3.4.2.1.3 Development Code: Modify the source code form of  
>>> Development
>>> Code for the sole purpose of designing, developing and testing your
>>> programs, and copy and distribute the object code form of your
>>> modified files;
>>> 3.4.2.1.4 Third Party Distribution: Permit distributors of your
>>> programs to copy and distribute the Distributable Code in object  
>>> code
>>> form as part of those programs; and
>>> 3.4.2.1.5 Use by End Users: Permit end users of your programs to use
>>> the Distributable Code as part of your programs.
>>> 3.4.2.2 Distribution Requirements. For any Distributable Code you
>>> distribute, you must:
>>> 3.4.2.2.1 add significant primary functionality to it in your  
>>> programs;
>>> 3.4.2.2.2 only invoke the software via interfaces described in the
>>> software documentation;
>>> 3.4.2.2.3 distribute Distributable Code included in a setup program
>>> only as part of that setup program without modification;
>>> 3.4.2.2.4 require distributors and end users to agree to  
>>> distribution
>>> or use terms that contain the same restrictions and disclaimers  
>>> as are
>>> set out in this agreement;
>>> 3.4.2.2.5 display your valid copyright notice on your programs; and
>>> 3.4.2.2.6 indemnify, defend, without limitation and hold harmless  
>>> the
>>> Secretary of State for Health and its suppliers, including Microsoft
>>> Limited and its affiliated companies ("Microsoft"), from any claims,
>>> including any applicable lawyers' fees, related to the  
>>> distribution or
>>> use of your programs.
>>> 3.4.2.3 Distribution Restrictions. You may not:
>>> 3.4.2.3.1 alter any copyright, trademark or patent notice in the
>>> Distributable Code;
>>> 3.4.2.3.2 use the Secretary of State for Health's or Microsoft's
>>> trademarks in your programs' names or in a way that suggests your
>>> programs come from or are endorsed by the Secretary of State for
>>> Health or Microsoft;
>>> 3.4.2.3.3 include Distributable Code in malicious, deceptive or
>>> unlawful programs; or
>>> 3.4.2.3.4 modify or distribute the source code of any Distributable
>>> Code so that any part of it becomes subject to an Excluded  
>>> License. An
>>> Excluded License is one that requires, as a condition of use,
>>> modification or distribution, that:
>>> (a) the code be disclosed or distributed in source code form, or
>>> (b) others have the right to modify it.
>>> _______________________________________________
>>> openEHR-clinical mailing list
>>> openEHR-clinical at openehr.org
>>> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
>>>
>> _______________________________________________
>> openEHR-clinical mailing list
>> openEHR-clinical at openehr.org
>> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
>>
>
>
> -- 
> Diego Bosc? Tom?s <diebosto at fis.upv.es>
>                               <yampeku at gmail.com>
> Grupo IBIME
> Instituto ITACA - Universidad Polit?cnica de Valencia
> Edificio 8G
> Camino Vera s/n
> 46022 VALENCIA (Spain)
> tel: +34 963 875 277
>
> http://ibime.upv.es
>
> _______________________________________________
> openEHR-clinical mailing list
> openEHR-clinical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical



Reply via email to