modelica / ssp-ls-traceability

Prototyping of an SSP Traceability Layered Standard
Other
11 stars 4 forks source link

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

Open localhorst87 opened 1 year ago

localhorst87 commented 1 year ago

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 commented 1 year ago

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.