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

Maybe de-wrap annotations and potentially other collection elements. #14

Open
pmai opened this issue Sep 15, 2023 · 1 comment
Open
Assignees
Milestone

Comments

@pmai
Copy link
Collaborator

pmai commented Sep 15, 2023

FMI 3.0 did go to some lengths to de-wrap collections of elements, i.e. instead of

  <Connectors>
    <Connector ...>
    <Connector ...>
  </Connectors>

you would have

  <Connector ...>
  <Connector ...>

without a wrapper. While FMI 3.0 did this for many elements, it did not do so for the annotations.

For SSP we might or might not want to move in this direction,

The benefit is the reduced XML size and more readable content, since the wrapper is really for the most part redundant.

The disadvantage is that this would move SSP 2.0 much farther from 1.0, which while not fully backward compatible can probably still be read by the same parser (i.e. you can construct a 2.0 parser that easily reads 1.0, whereas with this structural change, you probably would maintain two separate parsers).

@pmai pmai added this to the 2.0-alpha.1 milestone Sep 15, 2023
@pmai pmai self-assigned this Sep 15, 2023
@pmai
Copy link
Collaborator Author

pmai commented Sep 15, 2023

Personally I would not go for this for 2.0, due to the change impact, and our timeline constraints, and the need to also reflect this in SSP Traceability, ideally.

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

No branches or pull requests

1 participant