Hi John, Sorry for the delay in getting back to you. I just downloaded the most recent version of Prot?g? (Prot?g? 3.1), and can open an OWL files Isabel specifies directly in Prot?g?. File->New Project In the "Create New Project" window check the "Create from Existing Sources" checkbox. Click "Next" Then paste the URL Isabel specifies in the text box. It may throw an exception, but the file appears to open. -russ _____
From: John Silva [mailto:[email protected]] Sent: Monday, August 22, 2005 9:29 AM To: Hamm, Russell A. Subject: Re: FW: RFC - CR-000150 - express language etc as a String Russell, Do you know of a stylesheet or similar that would allow presenting OWL XML in some kind of graphical (SVG?) or tablular relationship diagram? This would help folks (like myseld) internalize what the OWL structure means. I remember finding a paper a couple of years back that trying to demonstrate the OWL concepts as UML diagrams (though it admitted that it wasn't completely able to do so).: http://hcs.science.uva.nl/usr/Schreiber/docs/owl-uml/owl-uml.html This helped me to understand somw of the OWL relationships in something that I was already familiar with (UML). Something similar for presenting OWL XMLs (ontologies) would be helpful too. [Again, this might be an FAQ; maybe there are already OWL presentation tools that do this that I'm just not aware of.] Thanks in advance, John Silva "Hamm, Russell A." Sent by: owner-templates at lists.hl7.org 08/21/2005 08:56 PM Please respond to "Hamm, Russell A." <Hamm.Russell at mayo.edu> To templates at lists.hl7.org cc Subject FW: RFC - CR-000150 - express language etc as a String Classification Forwarding to the Templates list...very good discussion and examples. -russ _____ From: owner-openehr-technical at openehr.org [mailto:[email protected]] On Behalf Of Isabel Rom?n Sent: Sunday, August 21, 2005 4:51 AM To: openehr-technical at openehr.org Subject: Re: RFC - CR-000150 - express language etc as a String I'm agree with the idea of an archetype ontology. In fact and archetype is an ontology, and the concepts reused in different archetypes can be part of the ancestor-archetype... I tried something similar, only an experiment, when I expressed demographic archetypes in owl, but it was very centered in demographics. This was the very, very, simple ontology I used to represent some useful concepts of archetypes I need for demographics: <http://trajano.us.es/~isabel/EHR/basearquetipo.owl> http://trajano.us.es/~isabel/EHR/basearquetipo.owl This could be named the ancestor-archetype for demographics, very simple of course... And this was the person archetype: <http://trajano.us.es/~isabel/EHR/person.owl> http://trajano.us.es/~isabel/EHR/person.owl all this using the openEHR ontology <http://trajano.us.es/~isabel/EHR> http://trajano.us.es/~isabel/EHR All these are in owl but could be expressed in ADL too. Regards Isabel Rom?n <http://trajano.us.es/~isabel> http://trajano.us.es/~isabel ----- Original Message ----- From: <mailto:[email protected]> Gerard Freriks To: <mailto:openehr-technical at openehr.org> openehr-technical at openehr.org Sent: Sunday, August 21, 2005 9:31 AM Subject: Re: RFC - CR-000150 - express language etc as a String My ideas about this are: - coding systems never will be stable. - the way to handle change in OpenEHR (and CEN En13606) is via archetypes. - select a coding system and produce a 'ancestor archetype' that uses codes from a specific coding system. - over time a new 'ancestor-archetype' will be produced using a new version of the specific coding system or a new coding system altogether. - the question now is how to handle interoperability. The answer is the use for an 'archetype ontology'. One we miss at this moment. - having this 'archetype ontology' makes it possible to define synonyms, anti-nyms, etc, and make semantic interoperability possible. - for it to work properly we need: 'ancestor archetypes', that can be inserted in Templates an archetype ontology an 'archetype editor' that is able to not only produce archetypes and templates but also assemble ancestor archetypes and normal archetypes into templates but also constrain each of them further. Gerard Freriks ps: I use sometimes the term 'proto-archetype' for the 'ancestor-archetype' -- -- Gerard Freriks, MD Convenor CEN/TC251 WG1 TNO Quality of Life Wassenaarseweg 56 Leiden PostBox 2215 22301CE Leiden The Netherlands T: +31 71 5181388 M: +31 654 792800 On 20-aug-2005, at 22:45, Rong Chen wrote: I agree. We need to have this indirection to handle changes. Even if we are certain that these codes will not change in the future and we feel the need to hardcode them in the software, some enumeration type instead of string type should be used to implement them since string is not type safe. ************************************************ You are currently subscribed to templates at lists.hl7.org as john.silva at philips.com To unsubscribe from this list, send a blank email to leave-templates-21924E at lists.hl7.org To access the Archives of this list, go to: http://lists.hl7.org/read/?forum=templates To access your List Server profile and subscriptions, go to: http://%%site.domainname%%/read/login -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20050823/8063bd57/attachment.html>
