Open kd-ods opened 6 months ago
Actually, I'm not sure that my assumptions above about the current situation are right. This code is using information from the replacesStatements field.
@codemacabre - When you have some time to investigate... could you let us know how the visualiser currently handles changing information about the same node/edge?
(This will help inform the decision regarding OO Register data not rendering in the visualiser.)
Current situation
At the moment, all data is rendered according to the specification here.
No account is taken of fields like
Interest.endDate
,replacesStatements
or field values likeInterest.share.exact
: 0 which indicate that information has changed over time, or that an interest is NOT present at a given time.This means that when data represents change over time, it will either not be parsed (see this OO Register/visualiser issue) or it may be visualised in a confusing way: it may look like a snapshot in time, but actually historical information is layered over current information.
With BODS 0.4 there will be clearer requirements regarding how to represent changing beneficial ownership over time.
What to do
We need to consider how the visualiser should handle data that represents change over time, both in BODS 0.4 and prior versions of the standard.
The minimal requirements is probably: have the visualiser explicitly represent information at a given point of time.