Dear All,
Please browse:
http://www.openehr.org/wiki/display/spec/XML+Schemas
Where we are trying to tighten up and rationalize the OpenEHR XML
Spec/Schemas. It is a Wiki so feel free to edit, discuss etc.etc.
In short, the usage of XML will grow it should be consistent,compact
and as
Rong Chen wrote:
Hi Adam, Heath
The attribute in question, original_author is an attribute of Class
RESOURCE_DESCRIPTION from rm.common.resource package. According to the
specs (common_im.pdf), the type is HashString,String NOT a string
and the invariant on it is Original_author_valid:
Byte Order Marks
What is the default CharSet for OpenEHR ADL?
ASCII? UTF-8?
I ask because ADL itself does not anywhere declare a character set we
have had a number of adl files which have failed (either to be opened or
to be transformed into XML) in each occasion the reason has been the
Thomas Beale wrote:
Adam Flinton wrote:
Preferably in Eclipse UML2...?
If so does it then include the archetypes class model as well?
*The UML for the forthcoming openEHR template model is online in the
latest AOM draft (some changes to AOM of ADL 1.4 vintage) and Templates
Thomas Beale wrote:
Sam Heard wrote:
Hi Adam
I take this point and in that case I would suggest that resulting
issue to discuss is:
Should we drop the class name from the Archetype Slot in ADL and just
use the regex? There does not appear to be any reason in the AOM to
include the
it up in
parentheses:
openEHR-EHR-CLASS_NAME\.(REGEX_EXPRESSION)
Then it should work.
Adam Flinton wrote:
... thus it needs to be split by a regex pre-processor
then each sub statement needs to have the
openEHR-EHR-CLASS_NAME
appended to it then put through the regex engine
Peter Gummer wrote:
Thomas Beale wrote:
I also agree with Adam. A regex should be able to be used over a
population of strings (identifiers in this case) and have the effect of
filtering out what you want. ...
Practically speaking this does not change the specifications, but I
Sam Heard wrote:
Hi Adam
I know Tom has talked to you about this. I was involved in the
original discussions about this many years ago and many points of view
were expressed. The issue is that, as you know, the CLASS is specified
in the slot definition and there is a regex for the
Thomas Beale wrote:
Adam Flinton wrote:
Dear All,
I have been poking about the openEhr site looking for something which
definitively says what an archetype is, preferably in a computable form.
is there a UML model/adl/XML schema which is downloaded which is the
definative/normative
Dear All,
Given we have a lot of archetypes which are then further versioned etc
moving archetypes from one version to another can become a real pain
based on their inherited content.
i.e. if B.v1 specializes A.v1 then it includes the content of A.v1
If we then create an A.v2 wish to create
Dear All,
I have raised 2 changes wrt archetypes (wrt regex'es and superclass
content in subclasses) a thought occurred which had been troubling me
for a while which is:
Where exactly are these changes made/agreed to etc?
i.e. wrt say HL7 (or other std orgs I have been involved with (e.g.
Sam Heard wrote:
Hi Adam
This is another example of the approach to be as specific as possible.
The exclude statement can be used to exclude specific archetypes and
the Include ALL in this case means that all others are allowed. If the
Exclude ALL statement is added to an archetype, it
Williamtfgoossen at cs.com wrote:
In a message dated 13-6-2008 19:10:07 W. Europe Daylight Time,
sam.heard at oceaninformatics.com writes:
We are getting into dangerous options here: include all and exclude
all in a time series where 'all' definitely changes both with respect
to
Thomas Beale wrote:
Andrew Patterson wrote:
Sam, without putting words in Adams mouth, I think he was asking about
the precedence of include/exclude sections. It is a common problem is
coming up with rule system like this - for instance one can look at the
allow/deny pattern of the
A) Given an ADL how long does it take to create an object from the ADL?
B) Is there anyway within that code to then write out the XML ?
C) Has there been any forwards movement on starting with an XML
getting to the same object ( possibly then writing out the ADL)?
Hi Adam,
Parsing
Greg Caulton wrote:
If you are familiar with Maven, the best way is to check out the latest
version from the trunk and build from source. You could also download jars
from the continuous integration server from here
http://openehr.cambiosys.org/continuum. Just click the component and follow
Greg Caulton wrote:
--
Message: 2
Date: Sun, 04 May 2008 21:40:23 +0200
From: Bert Verhees bert.verhees at rosa.nl
Subject: Re: Data-entry for OpenEhr
To: For openEHR technical discussions openehr-technical at openehr.org
Message-ID: 481E1127.6060805 at rosa.nl
Dear All,
I am still mulling over how to validate openEhr messages (wrt testing)
how to create Xforms etc.
3 separate questions
A) I noticed this:
http://www.openehr.org/wiki/display/dev/Data+type+widgets
Has any progress been made?
B) Is there a datatype for rich text (e.g. XHTML
Dear All,
Is there an easy way to create or does anyone have any messages in XML?
i.e. if one has a template or archetype is there any way to create an
example of the message which would be sent using that archetype/template?
Our message checking s/w in our Integration Center uses XPath, XSLT
Thilo Schuler wrote:
Sorry, still don't get it completely.
What do you mean by use directly in HL7? Do you refer to HL7 CDA
only or to any HL7 message? Could you please provide a little more
detail how MOF would help with that.
Thanks. Thilo
I am looking at it more from the EMF/EMOF
Heath Frankel wrote:
Adam,
Indeed however there are ways of persisting a model they require at
the end of the day a recognizable document design/format.
I have already noted how using text children of an element to use a
value vs a std value attribute in the archetype xml inflates the
Peter Gummer wrote:
My reply was really just an attempt at humour, Colin. Even with really long
tag names, you don't get a 1:3 ratio; not even 1:2, I think.
And of course OPENEHR_ELEMENT_NAMES_ARE_NOT_REALLY_LONG_ANYWAY ;-)
- Peter
The key difference though is that I came to the
Colin Sutton wrote:
With a compression algorithm, the difference may be negligible.
Heath's first example is smaller than the second when zipped due to the
repeated strings.
Of course, the result may be quite different for a larger sample where
value= is repeated.
even larger should
Thomas Beale wrote:
Adam Flinton wrote:
Other limitations on using XML - it's a no-show for enterprise scale
databases
or information processing. All that wasted space starts to count when you
have
to buy two ?20,000 high availability RAID disk arrays instead of one
Tim Cook wrote:
[extracted from the thread Archetype documentation using XML + XSLT]
Tim Cook wrote:
ADL does semantically describe the AOM.
No reason why XML could not.
It can suffice for anything from a webform (e.g. XForms) to a vector
graphic (e.g.
Tim Cook wrote:
Hi Adam,
On Fri, 2008-04-18 at 11:55 +0100, Adam Flinton wrote:
Stepping outside of well supported standards increases maintenance
requirements much much more.
Well, I am not certain I would say much much more but in any case there
are reasons why new
In a reply wrt On Information and Interoperability I have noted that
there is a move underway to try produce an HL7 model (via EMF/MOF) for
use in our /OHT eclipse tooling.
Has anyone looked at an AOM/MOF mapping?
If so any thoughts?
E.g. were one to want to sit down do some Eclipse OpenEHR
Peter Gummer wrote:
Adam Flinton wrote:
I have already noted how using text children of an element to use a value
vs a std value attribute in the archetype xml inflates the file sizes.
So you aren't convinced by Thomas's objection that putting the values in XML
attributes
Sam Heard wrote:
Dear All
After discussions with users and in consideration of the range of
platforms now being implemented, it would seem appropriate to move to
a multiplatform documentation process for openEHR artefacts. The
important specific documentation to consider are for
Peter Gummer wrote:
sam.heard signatureSam Heard wrote:
What we need is an XSL Script that consumes XML archetypes ...
Hi Sam,
XSLT is ok in small doses, but it becomes unmaintainable for anything
complex. Other approaches share the advantages claimed at
Heath Frankel wrote:
Peter,
The key is that by using XSLT we don't need to use one particular software
component and as you say, everyone can execute an XSLT script in their
chosen environment where the output should be almost the same.
We have done many XSL transformations from AOM XML and
the
publishing mech the (JSF+EJB3) vocab server out too.
Adam
Adam Flinton wrote:
Sam Heard wrote:
Dear All
After discussions with users and in consideration of the range of
platforms now being implemented, it would seem appropriate to move to
a multiplatform documentation process
Sam Heard wrote:
Dear All
After discussions with users and in consideration of the range of
platforms now being implemented, it would seem appropriate to move to
a multiplatform documentation process for openEHR artefacts. The
important specific documentation to consider are for
Other limitations on using XML - it's a no-show for enterprise scale
databases
or information processing. All that wasted space starts to count when you
have
to buy two ?20,000 high availability RAID disk arrays instead of oneand
plus
the bandwidth wastage when there are
Tim Cook wrote:
On Thu, 2008-04-17 at 16:29 +0100, Adam Flinton wrote:
umm...where to even startoh yes how about...
You left out the fact that XML cannot semantically reproduce an object
model.
XML is a form of text markup. It is more analogous to the English
Gerard Freriks wrote:
The crux might be in the text in red.
Everything can be made to work.
A floating boat made out of match stick. Yes it is possible,
Gee they'll be making boats bridges out of iron steel next.
but not the bet engineering choice.
Perhaps XML is not the best choice in
Adam Flinton wrote:
Yaywe're public
http://www.openhealthtools.org/index.htm
Recent News http://www.openhealthtools.org/news.htm
*Forge Project Repository Goes Live*
https://www.projects.openhealthtools.org/servlets/ProjectList
Open Health Tools software repository
https
Ime Asangansi wrote:
Hi Lisa, Thilo et al,
Really appreciate your comments... I have the impression that much
still has to be done about Xforms...
OpenMRS is based on infopath for now, so I am now looking at
archetypes as form templates (.xtp files). These are relatively
reusable form
Dear All,
I have build a complete publishing system for OpenEHR.
It ends up in part with a bunch of href's in an HTML page e.g. if it
finds errors then it creates a link to the file in the relevant working
copy.
2 points:
A) Wrt .adl I can set the filetype etc in windows when I clik on a
Any idea of saving space has to be done on the basis of a study of high
volumes of representatively diverse data. Saving 10 bytes is not
interesting, but saving 10Gb/minute in a large data processing system
is. I will go out on a limb and say that 'style' has no place in good
to provide XML as
a relatively stable output.
Excellant
More in line.
Adam Flinton wrote:
Dear All,
I am wondering about transforms as I move along to a complete
build/release system for a repository of archetypes.
A) Is there an XML - ADL transform?
We have one - you can do
Thomas Beale wrote:
Adam Flinton wrote:
I reserve my views wrt attributes vs text() however that would do on
the proviso of a bit of testing with many tools as it used to be
patchily supported by different tools.
I accept that was a few years back things may well have improved.
So
-bounces at openehr.org [mailto:openehr-technical-
bounces at openehr.org] On Behalf Of Thomas Beale
Sent: Monday, 10 December 2007 7:34 AM
To: adam.flinton at nhs.net; For openEHR technical discussions
Subject: Re: Suggestion wrt XML Archetypes Templates
Adam Flinton wrote:
I reserve my
Lisa Thurston wrote:
Hi Adam and all
I think there might have been some misunderstanding regarding the
problem you raised. Yes Oxygen and XmlSpy will add unpredictable
whitespace characters into an element when pretty printed and resaved.
The problem is that the XML tools don't know they
Dear All,
I am wondering about transforms as I move along to a complete
build/release system for a repository of archetypes.
A) Is there an XML - ADL transform?
B) Are the HTML docs presently transformed from the ADL or XSLT'ed from
the XML?
C) Same as (B) but for the CSV files.
What I
Thilo Schuler wrote:
Hi
As I assume not everybody interested in openEHR GUIs has set watches
for the relevant pages in the openEHR wiki, I would like to point to a
rather lengthly comment of mine:
Chunlan Ma wrote:
Dear Adam,
I totally understand the XML issues that you described in your previous
email. However, this problem doesn't exist if you use oXygen xml
editor. I
just downloaded Altova XMLSpy 2008. I opened an archetype XML file using
XMLSpy 2008 and did pretty-print and then
Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety. Benjamin
Franklin 11 Nov 1755
On Nov 30, 2007, at 4:15 PM, Adam Flinton wrote:
**
This message may contain confidential
Gerard Freriks wrote:
Thanks.
But I'm curious in:
Why?
Why is you solution more safe?
A) You are definitively bookending the string.
This is exactly the same as you do within the ADL e.g.
[at0002] =
description = *
text = Procedure
Ian McNicoll wrote:
Just for info, I have the latest version of XMLSpy 2008 and cannot
reproduce the problem with Pretty-printing adding whitespace to
element values. Although XMLspy rather nicely word breaks long text
lines and indents appropriately, none of this whitesapce appears to be
Thomas Beale wrote:
Adam Flinton wrote:
To quote from the oxygen xml page above:
Although writing documents with no indentation is a perfectly
acceptable practice, it makes editing difficult and is error prone. It
also makes the identification of exact error positions difficult
Heath Frankel wrote:
Adam,
i) The present situation/structure is dangerous.
You need to get a better tool, Oxygen never splits an element value over
multiple lines or adds whitespace. A tool that automatically does this is
dangerous. I used to use XMLSpy and never experienced
/structure is dangerous.
ii) Pretty-print is the norm even the ADL is pretty printed and has
adopted a similar method to cope.
iii) The solution simplifies the XML in terms of both processing and
human readability.
iv) The solution shrinks the file sizes.
Yours
Adam Flinton
Dear all,
Has anyone got the email addresses etc of the authors of the LiU
Archetype Editor?
I would like to get in touch with them as I may be able to help with the
code.
Adam
**
This message may contain confidential
54 matches
Mail list logo
