This addresses #220 (and one of the dicoms in #327) by treating elements with a VR=UN and undefined VL as Sequences.
This pulls from work that I and @jabillings did previously (#235).
Some follow on changes may be needed to support this part of the spec CP:
If at some point an application knows the actual VR for an Attribute of VR UN (e.g. has its own applicable data dictionary), it can assume that the Value Field of the Attribute is encoded in Little Endian byte ordering with implicit VR encoding, irrespective of the current TransferSyntax.
This addresses #220 (and one of the dicoms in #327) by treating elements with a VR=UN and undefined VL as Sequences.
This pulls from work that I and @jabillings did previously (#235).
Some follow on changes may be needed to support this part of the spec CP: