You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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...
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.
I wonder if it makes sense to align subelements of
ContentType
,ClassificationEntry
andAnnotation
?In the STC namespace the complexType of
ContentType
andClassificationEntry
allows mixed content (text AND other sub elements), whereas in the SSC namespace this is not the case forAnnotation
, which leads to the result that XML-subelements MUST be defined in theAnnotation
element. Imho this brings in unnecessary complexity for Annotation...See the comparison
The text was updated successfully, but these errors were encountered: