#445 Conversion of ODD to HTML: Examples should be aware of element renaming

AMBER
closed-fixed
Stylesheets (1)
1(low)
2013-11-10
2013-03-14
James Cummings
No

Currently if I create an ODD which renames, let's say:
persName = psn
roleName = rn
forename = fn
surname = sn

the example for forename still comes out as:

<persName>
<roleName>Ex-President</roleName>
<forename>George</forename>
<surname>Bush</surname>
</persName>

It would be good if the examples could be parsed and any altIdents applied to each of the exemplum.

I recognise this is non-trivial and low urgency.

Discussion

  • Lou Burnard
    Lou Burnard
    2013-06-18

    I think this is part of a much more general problem to do with the examples in ODD. Almost any change to an ODD risks making an existing example misleading -- if for example an element included in it is removed from the schema. The only safe course is to provide new examples in your ODD. Of course you might generate them automatically if your only changes are to GIs, but I don't think it's reasonable to expect that of a generic ODD processor.

     
  • James Cummings
    James Cummings
    2013-11-09

    Agreed that it is a symptom of a larger problem, but simple element renaming should be able to be captured.

     
  • James Cummings
    James Cummings
    2013-11-09

    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,4 +1,3 @@
    -
     Currently if I create an ODD which renames, let's say: 
     persName = psn
     roleName = rn
    
    • Priority: 5 --> 1(low)
     
    • status: open --> closed-fixed
    • assigned_to: Sebastian Rahtz
     
  • duly implemented in odd2lite