Skip to content

Handling of text contents not specified #9

@tsdh

Description

@tsdh

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.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions