# Parsing TEXT

**Category:** [Technical (archive)](https://discourse.openehr.org/c/technical-archive/156)
**Created:** 2006-08-21 14:40 UTC
**Views:** 2
**Replies:** 0
**URL:** https://discourse.openehr.org/t/parsing-text/14200

---

## Post #1 by @thomas.beale

just catching up\.\.\.\.
> Newton Aird wrote:
>
> &nbsp;&nbsp;&nbsp;&nbsp;Hi,
> &nbsp;&nbsp;&nbsp;&nbsp;I am trying to figure out what should be the correct production in
> &nbsp;&nbsp;&nbsp;&nbsp;the AOM for the following ADL code\. What bothers me most is the
> &nbsp;&nbsp;&nbsp;&nbsp;TEXT matches \{\*\} construct\.
>
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ELEMENT\[at0002\] matches \{    \-\- Accident or
> exposure
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;value matches \{
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TEXT matches \{\*\}
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\}
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\}
>
> &nbsp;&nbsp;&nbsp;&nbsp;I have seen this used quit a bit in the sample archetypes, but I
> &nbsp;&nbsp;&nbsp;&nbsp;dont thing the parsed object model from the java parser is correct
> &nbsp;&nbsp;&nbsp;&nbsp;since it makes it a CComplexObject leaf node with RMTypenam of
> &nbsp;&nbsp;&nbsp;&nbsp;TEXT\. From the specification I know that CComplexObject should
> &nbsp;&nbsp;&nbsp;&nbsp;only be inner nodes in the AOM\. I have queried the online
> &nbsp;&nbsp;&nbsp;&nbsp;documentation and found references to TEXT in the 1\.2 adl, but
> &nbsp;&nbsp;&nbsp;&nbsp;nothing in 1\.4 that describes what TEXT matches \{\*\}\.
>
> &nbsp;&nbsp;&nbsp;&nbsp;I was inclined to assume it should be DvText constrained with the
> &nbsp;&nbsp;&nbsp;&nbsp;regular expression /\*/\.
>

Put another way, the general pattern

TYPE\_NAME matches \{\*\}

is how to constrain an object to be of a certain type, but not constrain
the value in any way
> Hi Newton,
>
> &quot;TEXT matches \{\*\}&quot; basically says a DvText object will be created for
> this node and there is no constraint on the actual value\. So what&#39;s
> produced from the parser is correct\.
>
> But for String constraints cADL has its own syntax\. So the ADL should
> be something like the following to be more correct\. Then a CString
> node will be created instead\.
>
> &nbsp;&nbsp;&nbsp;ELEMENT\[at0002\] matches \{ \-\- A\.\.
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;value matches \{/\*/\}
> &nbsp;&nbsp;&nbsp;\}
>
> See part 4\.4\.1 of ADL speficiation for more information\.
>

\- thomas

---


**Canonical:** https://discourse.openehr.org/t/parsing-text/14200
**Original content:** https://discourse.openehr.org/t/parsing-text/14200