Does XMLSerializer (java) create archetype slots with too much extra information?

2012-01-04 Thread Sam Heard
Hi Diego

This was the result of some overzealous efforts in the past (designed to
make XML look verbose :-). The discussion has been about the fact that
Occurrences does not need an includelower/upper and unbounded is not
necessary as it can never be a constraint statement.

The expression is new to me...

Sam


 -Original Message-
 From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
 bounces at openehr.org] On Behalf Of Diego Bosc?
 Sent: Wednesday, 4 January 2012 1:18 AM
 To: For openEHR technical discussions
 Subject: Does XMLSerializer (java) create archetype slots with too much
 extra information?
 
 This is a simple question: Why does a simple archetype slot like this
 (ADL)
 
 allow_archetype ELEMENT[at0001] occurrences matches {0..*} matches {
 -- Archetype slot
 include
 archetype_id/value matches {/.*/}
 }
 
 ends up like this?
 
 children xsi:type=ARCHETYPE_SLOT
 rm_type_nameELEMENT/rm_type_name
 occurrences
   lower_includedtrue/lower_included
   upper_includedfalse/upper_included
   lower_unboundedfalse/lower_unbounded
   upper_unboundedtrue/upper_unbounded
   lower0/lower
 /occurrences
 node_idat0001/node_id
 includes
   tag /
   string_expressionarchetype_id/value matches
 {/.*/}/string_expression
   expression xsi:type=EXPR_BINARY_OPERATOR
 typeBOOLEAN/type
 operator2007/operator
 precedence_overriddenfalse/precedence_overridden
 left_operand xsi:type=EXPR_LEAF
   typeSTRING/type
   item xsi:type=xsd:stringarchetype_id/value/item
   reference_typeCONSTANT/reference_type
 /left_operand
 right_operand xsi:type=EXPR_LEAF
   typeString/type
   item xsi:type=C_STRING
 pattern.*/pattern
   /item
   reference_typeCONSTANT/reference_type
 /right_operand
   /expression
 /includes
 
 I'm not complaining about the ultra-verbose occurrences (surely can be
 improved, but there was already a discussion about this on this
 mailing list).
 I don't get the point of putting the 'expression' tags on this case.
 It's like putting the same thing twice.
 Is the 'operator' tag supposed to be understandable?
 ___
 openEHR-technical mailing list
 openEHR-technical at openehr.org
 http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical





Does XMLSerializer (java) create archetype slots with too much extra information?

2012-01-03 Thread Diego Boscá
This is a simple question: Why does a simple archetype slot like this (ADL)

allow_archetype ELEMENT[at0001] occurrences matches {0..*} matches {
-- Archetype slot
include
archetype_id/value matches {/.*/}
}

ends up like this?

children xsi:type=ARCHETYPE_SLOT
rm_type_nameELEMENT/rm_type_name
occurrences
  lower_includedtrue/lower_included
  upper_includedfalse/upper_included
  lower_unboundedfalse/lower_unbounded
  upper_unboundedtrue/upper_unbounded
  lower0/lower
/occurrences
node_idat0001/node_id
includes
  tag /
  string_expressionarchetype_id/value matches
{/.*/}/string_expression
  expression xsi:type=EXPR_BINARY_OPERATOR
typeBOOLEAN/type
operator2007/operator
precedence_overriddenfalse/precedence_overridden
left_operand xsi:type=EXPR_LEAF
  typeSTRING/type
  item xsi:type=xsd:stringarchetype_id/value/item
  reference_typeCONSTANT/reference_type
/left_operand
right_operand xsi:type=EXPR_LEAF
  typeString/type
  item xsi:type=C_STRING
pattern.*/pattern
  /item
  reference_typeCONSTANT/reference_type
/right_operand
  /expression
/includes

I'm not complaining about the ultra-verbose occurrences (surely can be
improved, but there was already a discussion about this on this
mailing list).
I don't get the point of putting the 'expression' tags on this case.
It's like putting the same thing twice.
Is the 'operator' tag supposed to be understandable?