Don't worry, I am thinking more in terms of weeks not years. But we do
have a spec that does what is needed, the debate is whether there is a
clearer way, and whether it is worth changing it. But - to make a
(possibly) breaking change, we need more than a couple of days to
reflect ...
- thomas
On 07/04/2016 20:12, Bert Verhees wrote:
On 07-04-16 17:44, Thomas Beale wrote:
well, we need to get this right for everyone. The current spec
works, but you are suggesting that it be changed to make it
'regex-only'; Diego I think is suggesting something else; but if we
were going to change it, we need to get input from openEHR tool
implementers, 13606 group, AML developers, CIMI...
That seems a long discussion to come, it will take years. I know that
kind of discussions. In 13606 they are in a renewal.
They are involving ISO also. The whole world is gonna have an opinion
about it.
The best way to stop innovation is standardization. I learned that
from one of your blogs.
But I understand your position, ADL 1.5 is part of an ISO standard, so
you need ADL 2.0 to have the same position
OK, I give up. Just leave it as it is.
We have a constraint, and that is a List<String>.
That List can contain, one or more regular expressions, which are
recognizable by enclosing forward-slashes, and the list can contain
one or more strings, which are recognizable because of not having
those forward slashes.
I can handle it in code, no problem, I just thought it was a stupid
idea to do it that way. But I am convinced, I cannot stand up against
the whole world.
I want the AOM to be ready soon, so, I stop arguing and do it this
way, it is not that important anyway. As long as all needed constructs
are supported it is good enough.
Have a nice day. It is really not important.
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
