Usage of simpleDate vs StartDate/EndDate under d:DataCollectionDate element.
If user wants to use SimpleDate (for a single event), this causes problems, as StartDate is currently mandatory in the profile. Alex suggested we have a new “either/or” constraint type for mandatory elements to handle this and will assess technical feasibility
Handling AnalysisUnit. Unlike TimeMethod/SamplingProcedure/ModeofCollection, AnalysisUnit does not have a r:Description/r:Content element so it is not clear how we will store both the codevalue AND the descriptive term. Wolfgang was to suggest a proposal for handling this. Outstanding action for Wolfgang, who will bring a proposal to the next meeting.
Next steps to move DDI3.2 profile towards publication
What further checks and validation need to be performed and by whom.
Original report on BitBucket by Darren Bell.
Agenda
Draft DDI3.2 profile (attached ) updated based on decisions made at meeting on 17-March-21 (see https://github.com/cessda/cessda.cmv/issues/119)
Remaining issues for clarification:
If user wants to use SimpleDate (for a single event), this causes problems, as StartDate is currently mandatory in the profile.
Alex suggested we have a new “either/or” constraint type for mandatory elements to handle this and will assess technical feasibility
Outstanding action for Wolfgang, who will bring a proposal to the next meeting.
Next steps to move DDI3.2 profile towards publication
What further checks and validation need to be performed and by whom.
Actions for next meeting