Hello,
I’m trying to add support for ITEM_TABLE in the Java Archetype Editor and I have looked at the only archetype I’ve found that contains a data structure like this. It is openEHR-EHR-OBSERVATION.tendon_babinski_reflexes.v1.adl and it can be found here http://oceaninformatics.biz/archetypes/. When I compared the attributes for the ITEM_TABLE in the data structures specifications (found here http://svn.openehr.org/specification/TRUNK/publishing/architecture/rm/data_structures_im.pdf) with the ones that existed in the archetype I saw that the attributes had nothing in common. Maybe someone can explain to me how the ITEM_TABLE look like once and for all 
The archetype looks like this:
ITEM_TABLE[at0003] matches { – structure
//// COMMENT: The attributes below adhere to the ITEM_TABLE that you get when you create a table structure in the Ocean Archetype Editor, but I haven’t seen any of these three attributes specified anywhere. I would be glad if anyone could point them out to me.
rotated matches {True}
number_key_columns matches {|1|}
rows cardinality matches {0..1; unordered} matches {
CLUSTER[at0050] occurrences matches {0..2} matches { – row
items cardinality matches {7; ordered} matches {
//// COMMENT: This first element has a CODED_TEXT which contains coded terms that are represented as columns in the Ocean Archetype Editor.
ELEMENT[at0012] occurrences matches {0..1} matches { – row_head
value matches {
CODED_TEXT matches {
code matches {
[local::
at0011, – Left
at0013] – Right
}
}
}
}
//// COMMENT: This element and all succeding elements are represented as rows in the Ocean Archetype Editor.
ELEMENT[at0004] occurrences matches {0..1} matches { – Biceps
value matches {
ORDINAL matches {
value matches {
…
}
}
}
}