-
Notifications
You must be signed in to change notification settings - Fork 2
Handling of text contents not specified #9
Copy link
Copy link
Open
Labels
Description
I just wanted to mention that the case description doen't specify how text contents should be handled. For example, test3.xml contains
<Instrument>
<Symbol>EK</Symbol>
<IDSource>1</IDSource>
<SecurityID>277461109</SecurityID>
</Instrument>According to the current case description, Symbol, IDSource, and SecurityID would become empty classes which doesn't make sense. Additionally, the XML metamodel in the case description isn't able to represent text contents.
For what it's worth, I use my own XML metamodel and generate classes which contain one Content field for them, i.e., I handle text contents as if it was an attribute with fixed name Content and the text being its initial value.
Reactions are currently unavailable