I was referring (hinting) to our (openEHR) row/result-set or whatever that type-name we will have in our specification (because we should have those types specified, including json-schema, xsd).
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| AQL - the simplest possible question? | 34 | 1666 | 7 September 2023 | |
| Practical approach to FOLDER OPTs | 36 | 1024 | 14 November 2022 | |
| EHRs with different system_id in the same server? | 39 | 1084 | 7 November 2024 | |
| Aql teaser 1 for implementers | 32 | 1034 | 30 March 2020 | |
| Safety features in AQL: subject | 104 | 2476 | 28 November 2019 | |
| AQL to retrieving data for an element with cardinality 0..* | 50 | 1353 | 6 December 2022 | |
| [EHRbase] Storing and querying data without an standalone archetype | 39 | 925 | 17 April 2024 | |
| How accurately do we model "copied" data? | 42 | 1484 | 27 August 2025 | |
| Missing rule in AOM 1.4 for non-unique sibling nodeIds | 42 | 968 | 8 April 2024 | |
| Aql: clarify types supported by relational operators | 23 | 974 | 19 February 2020 |