Skip to Navigation | Skip to Content

Ref_impl_Java mailing list archives

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: findMatchingRMClass

  • To: "List for the development team for the reference implementation of openEHR in Java language and technologies." <ref_impl_java@openehr.org>
  • Subject: Re: findMatchingRMClass
  • From: "Bert Verhees" <bert.verhees@rosa.nl>
  • Date: Sun, 27 Jul 2008 22:08:28 +0200 (CEST)

> <br>
> I am interested to know what you are using this type matching method
> for - I have never had to write anyhting like this - in our parser
> software, we always know what the type of the object is a priori.<br>
> <br>

There are some untyped dADL-files in the java-project, and I was 
wondering
if I should support them, this because I want to stay as close as 
possible
to the java-reference implementation.
But supporting them took me already several days, and was unreliable (in
my case), so I stopped (for now) supporting them, it is very easy to 
work
around (just put the types in it).

Although, there is a problem. Because want to use dadl as a format for
data-transport, for example from an application to the orm layer (also
passing the rm-builder to create RM-types)
This is OK, when I have everything under control, but I want the kernel 
I
am writing also to be connectible to software (GUI's, other
data-entry-machines) from third parties, and I want them to use DADL, 
but
in that case, the spec, which does not require types is working against
me. So if this point could be changed in the spec, I would be happy, but
if it cannot, then I have to live with it (and add an extra 
restriction).

Bert

_______________________________________________
Ref_impl_java mailing list
Ref_impl_java@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/ref_impl_java