ITEM_TABLE archetypes and Oceans Archetype Editor

Technical (archive)
1

Hi,

We are trying some GUI generation with a wide set of archetypes.
Now we are making some ITEM_TABLE test archetypes.

From the data_structure specification I understand that “Each row is encoded as a Cluster containing a number of Elements, each corresponding to
the value of a column in that row”, but when I create an ITEM_TABLE archetype with Oceans Archetype Editor I get a structure that not match the specification.

If I have a table with 3 rows and 2 columns I spect to see 3 clusters and two elements on each one, but I get this:

definition
ITEM_TABLE[at0000] occurrences matches {0..} matches { – tabla loca
rotated matches {False}
number_key_columns matches {|1|}
rows cardinality matches {0..1; unordered} matches {
CLUSTER[at0008] occurrences matches {0..1} matches { – row
items cardinality matches {4; unordered} matches {
ELEMENT[at0005] occurrences matches {0..1} matches { – row_head
value matches {
DV_CODED_TEXT matches {
defining_code matches {
[local::
at0004, – col1
at0006] – col2
}
}
}
}
ELEMENT[at0002] occurrences matches {0..1} matches { – popopopo
value matches {
DV_TEXT matches {}
}
}
ELEMENT[at0003] occurrences matches {0..1} matches { – lolololo
value matches {
DV_DATE_TIME matches {*}
}
}
ELEMENT[at0007] occurrences matches {0..1} matches { – ererer
value matches {
C_DV_QUANTITY <

}
}
}
}
}
}

I understand this structure, but is the inverse table of what the specification says and I think this way of encoding tables is not well documented.

My questions are:

  • am I correct?
  • how can I make a table that match the specifications with Oceans Editor?
  • is this a bug on the specs?

Thanks a lot,
Pablo Pazos Gutierrez