Hi Dmitry, as a side conceptual note, the openEHR IM is not a persistence
model, and the XSDs are a way to express instances of the IM.?
The XSDs would require some refactoring work to express an specific persistence
model for the Information Model, like simplifying some datatypes of
from my LG Mobile
-- Original message--
From: Dmitry Baranov79104301700 at yandex.rumailto:79104301...@yandex.ru
Date: Thu, Apr 16, 2015 04:06
To: For openEHR technical discussions;
Subject:Re: OpenEHR and Oracle XML DB problems
Hi Bert,I give up. The problem appears in 12c as well
On 15-04-15 23:11, Thomas Beale wrote:
On 15/04/2015 17:28, Bert Verhees wrote:
On 15-04-15 17:19, Dmitry Baranov wrote:
Sorry Bert ) I had to explain that Oracle 11 is a business
requirement, not a hardware limitation.
Just do it, and then it should run fine, although you have to
change
Hi Bert,
I give up. The problem appears in 12c as well.
And people agree that it is an Oracle bug.
https://community.oracle.com/message/13008017
You should always follow the standard in your analyses, before you
declare one product buggy and another not.
I see in that message that there was
In fact, JSON-Schema is only lacking a more detailed typing system to
replace ADL :)
2015-04-16 9:29 GMT+02:00 Thomas Beale thomas.beale at oceaninformatics.com:
On 16/04/2015 06:46, Bert Verhees wrote:
I think it is a stupid rule in the XML-Schema standard.
I just hit this in doing the
On 16-04-15 09:06, Dmitry Baranov wrote:
Hi Bert,
I give up. The problem appears in 12c as well.
And people agree that it is an Oracle bug.
https://community.oracle.com/message/13008017
You should always follow the standard in your analyses, before you
declare one product buggy and another
On 16-04-15 09:29, Thomas Beale wrote:
e still need some kind of schema for XML docs/ messages, but I would
not even think of making any persistence be based on XML, especially
not XML schema. Probably Relax NG would have been the better one for
messages etc.
Keep XML at the boundaries,
Hi there,
there might be good reasons (as mentioned here) to not like XML but its
mature and rich technology stack (XSLT, XPath/XQuery, Schematron,
RelaxNG), available tooling (Mapforce, XML Spy...) and support (Most
major database vendors...) makes it a working solution in many
use-cases. I
I regret that I cannot post the XML Schema and XML-instances I use, because
they are not of my IP. But they are structured in another way, more dedicated
to efficiency.
XML schema is intellectual property, I agree, but why might you or somebody
else not to provide community with a couple
On 16-04-15 10:42, Dmitry Baranov wrote:
I regret that I cannot post the XML Schema and XML-instances I use, because
they are not of my IP. But they are structured in another way, more
dedicated to efficiency.
XML schema is intellectual property, I agree, but why might you or somebody
else
I can generate random sample instances from current archetypes for you
if you need them. Generated data may not make much sense as it only
tries to follow the archetype constraints, but it should be enough for
application testing and benchmark
2015-04-16 10:42 GMT+02:00 Dmitry Baranov baranovda
Diego,
that'll be great.
Hope that OpenEHR github owners will provide us with an instance samples
repository some day or other :)
I can generate random sample instances from current archetypes for you
if you need them. Generated data may not make much sense as it only
tries to follow the
Indeed, it would be a great thing. The reason it doesn't exist so far,
is that to be useful we need synthesised data sets that have some
realistic statistical spread of values. Since we are talking at multiple
levels - not just vital signs measurements, but covariance of all kinds
of
On 16-04-15 11:13, Thomas Beale wrote:
Indeed, it would be a great thing. The reason it doesn't exist so far,
is that to be useful we need synthesised data sets that have some
realistic statistical spread of values. Since we are talking at
multiple levels - not just vital signs
Hi Thomas,
do we really need realistic data sets? At least in the beginning, many
programmers that are new to openEHR would already be happy with some
valid data instances.
If anyone likes to do such a synthesier: Katrin Dentler has done some
work on patient data generation
Hi Birger,
Thanks for link to Katrin's work.
Regards
Seref
On Thu, Apr 16, 2015 at 10:32 AM, Birger Haarbrandt
birger.haarbrandt at plri.de wrote:
Hi Thomas,
do we really need realistic data sets? At least in the beginning, many
programmers that are new to openEHR would already be happy
Had to make this a separate discussion about the data synth to
distinguish it from the Oracle XML DB problems.
If you have access to primary data, e.g. the usual Pat_ID, Timestamp,
Code, Value, you can create very simple generative models by training a
neural network to generate sequences with
As part of NHS Code4Health, we should be able to expose a number of
realistic composition instances, kindly donated by system vendors.
On my Todo list :)
Ian
Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email: ian at freshehr.com
twitter: @ianmcnicoll
Hi everyone,
According Bert experience
(https://www.linkedin.com/groups/Choice-OpenEHR-persistence-layer-144276.S.208531138),
one must not try to adopt OpenEHR model to relational storage since almost all
popular database engines able to process native XML.
So I'm experimenting with Oracle
On 15-04-15 15:47, Dmitry Baranov wrote:
Hi everyone,
According Bert experience
(https://www.linkedin.com/groups/Choice-OpenEHR-persistence-layer-144276.S.208531138),
one must not try to adopt OpenEHR model to relational storage since almost
all popular database engines able to process
Sorry Bert ) I had to explain that Oracle 11 is a business requirement, not a
hardware limitation.
Just do it, and then it should run fine, although you have to change the
XML-Schemas (a bit) before registering them to Oracle. I already
explained to you before what and why.
I remember your
On 15-04-15 17:19, Dmitry Baranov wrote:
Sorry Bert ) I had to explain that Oracle 11 is a business requirement, not a
hardware limitation.
Just do it, and then it should run fine, although you have to change the
XML-Schemas (a bit) before registering them to Oracle. I already
explained to
22 matches
Mail list logo
