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

##any consistency between ContentType, ClassificationEntry and Annotation #59

Open
localhorst87 opened this issue Apr 17, 2023 · 1 comment
Assignees
Milestone

Comments

@localhorst87
Copy link

I wonder if it makes sense to align subelements of ContentType, ClassificationEntry and Annotation?

In the STC namespace the complexType of ContentType and ClassificationEntry allows mixed content (text AND other sub elements), whereas in the SSC namespace this is not the case for Annotation, which leads to the result that XML-subelements MUST be defined in the Annotation element. Imho this brings in unnecessary complexity for Annotation...

See the comparison

<ssc:Annotation type="...">
    <unnecessarySubelement> arbitrary annotation </unnecessarySubelement>
</ssc:Annotation>

<stc:Content> arbitrary content </stc:Content>
@pmai
Copy link
Collaborator

pmai commented Aug 2, 2023

I think this is a good point, but is more an issue against SSP itself, as it defines the ssc:Annotation type; given that FMI switched to mixed content in FMI 3.0 (2.0 was still non-mixed, like SSP 1.0), SSP 2.0 should also likely switch. I'll transfer the issue to the SSP development repo.

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

3 participants