OK, but there is only one data structure
<http://www.openehr.org/releases/AM/latest/docs/AOM2/AOM2.html#_c_string_class>:
constraint: List<String>
Are you saying you want another, separate string field?
On 07/04/2016 11:05, Bert Verhees wrote:
On 07-04-16 11:16, Diego Boscá wrote:
I don't see the problem of having just a list of strings and a regex
for C_String.
That is also my position, I don't know if it was clear, because, when
I explain too much, sometimes the message becomes unclear ;-)
So resuming:
There will, in my position, be two kind of constraints in a CString,
1) one is a single string, which will always be a regexpr,
2) and one is a list of strings will look like {"this","that"}, which
can also have one string, but in that case needs to be expressed as
{"string",...} the latter results in a list with one element in the
CString-constraint. (this is compatible with the odin-syntax).
The stringlist syntax (2) will never be processed as regexpression.
When we agree on this, we can drop the enclosing slashes for regexpr
in the single string (1), because a single string is always a
regexpression, so everything in this single string will be written as
a regexpression, always. Then we also do not need anymore to escape
the forward-slash "/" in the regexpression because the conflict with
the enclosing forward-slashes is gone
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
