Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling of text contents not specified #9

Open
tsdh opened this issue Apr 1, 2014 · 0 comments
Open

Handling of text contents not specified #9

tsdh opened this issue Apr 1, 2014 · 0 comments
Assignees

Comments

@tsdh
Copy link

tsdh commented Apr 1, 2014

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants