Closed goatsweater closed 6 months ago
Great—thanks again for clear and explicit descriptions and a MWE. I will open one or more PRs, either next week or the week after.
Working on #150, I notice another mismatch: the output SDMX-ML has the dimension FREQ in position 6, and TIME_PERIOD in position 7, which is reversed vis-à-vis the input. I'll also fix this.
I've noted a few dropped attributes when calling
to_xml()
on a structure message. Specifically:<common:AnnotationTitle>PRODUCT</common:AnnotationTitle>
)<structure:Dimension id="WHAT" position="1">
)(not implemented)
in xml, but is present in input (<Ref id="OBS_VALUE" />
)<structure:Attribute id="BASE_PER" assignmentStatus="Mandatory">
)This was found through manual inspect of a diff after round tripping a structure message file (
sdmx.read_sdmx()
->sdmx.to_xml(obj)
).Code to reproduce:
Diff the input vs the output. Attempting to read the output back in and run
compare()
crashes on me (XMLSyntaxError). I believe it is due to my use of a second language in the sample, but I haven't dug into that.Input file: