Closed goatsweater closed 8 months ago
Thanks for reporting this, especially for producing a specimen.
I would guess 2 different causes:
<com:Annotation>
elements are parsed to sdmx.model.common.Annotation
objects and stored on a stack. They—along with the other attributes like name, description, etc. localizations—are collected and attached to the Codelist
object only when the </str:Codelist>
end tag is reached. My guess is that they are mistakenly being scooped up at an earlier point, probably by the first AnnotableArtefact that is parsed after them, i.e. the single Code in this Codelist.I'll add a test and fix.
I never thought to check the first code. I just ran a full codelist and checked the first code for the top-level annotations and you are correct the annotations are ending up on the first code in the codelist.
I'm finding that when inspecting codelists from messages the annotations, valid to, and valid from dates are all empty. The services I'm working with are internal, so to demonstrate I've created a small sample message and code. Normally these messages originate from an internal deployment of iStat or .Stat.
This reads the below message, which has multiple annotations and valid to/from dates:
I was expecting all of these attributes to contain values as defined in the message.