Schema requirements around the Interest object

[kathryn-ods]

Currently interest.startDate is an optional field.

I think we should have some guidance that all interests SHOULD have a startDate (we currently say this can be rounded to nearest month or year if there's uncertainty about the exact date) and SHOULD have an endDate if the interest has ceased.

We might even want to make it a requirement that all interests MUST have a startDate. (This might open up another question of whether we require at least one interest in every relationship statement.)

[kd-ods]

The most we could go for here is a 'SHOULD' since there will be cases where the precise details of an interest are unknown.

This might open up another question of whether we require at least one interest in every relationship statement.

I think this is the important question to look at. It seems to me that it's not too big an ask to require at least one intererest per relationship. Since Interest.type can be 'unknownInterest' and directOrIndirect can be 'unknown'.

I don't think this is something that needs to be resolved for 0.4, though. Especially since we know that we have a chunk of work for the next release around Interest modelling.

I suggest we rename this issue 'Schema requirements around the Interest object' and remove from the 0.4 project.

[kathryn-ods]

I suggest we rename this issue 'Schema requirements around the Interest object' and remove from the 0.4 project.

Sounds good!