RKrahl
commented
6 years ago When discussing the criteria for the obligation classification, please also consider the implications, what each of the classes mean:
An optional property means that any application MAY store the corresponding piece of information in the metadata. When processing third party metadata, an application may use this property if it is present, but it may not assume it to be present.
A recommended property is one that should be present in all records. Applications creating metadata SHOULD provide this information. Applications processing third party metadata may assume this property to be present in most records, but not in all.
A mandatory property is one that MUST be provided by all applications creating metadata. It essentially means that we will refuse the registration of a PIDINST and reject the submitted record as a whole if this property is not present. Applications processing third party metadata may rely on the presence of this property.
From discussions, I get the impression that we really need to discuss criteria for including properties and for the classification as mandatory, recommended, or optional, see for instance #4. In the Google Doc I did add a Discussion section, trying to formulate some of these criteria. Now I reviewed my formulations once again and propose to add them to the schema document.
This PR aims to be a place to incite the discussion on the criteria. So please jump in, join the discussion and comment on what I formulated. According to the discussions, mdifications may be pushed on the branch of the PR. If we reach consensus on the criteria, this PR may be merged into master.