Most properties in UCO are optional. Setting minCount = 1 is enforced by SHACL makes a property required. This constraint will create problems in use cases in which a property is known to have existed but the value is not available.
Requirements
Requirement 1
Allow adopters to create an object when the existence of an object is known but an associated property is not known.
Risk / Benefit analysis
The proposed change allows adopters to decide which property is needed, except when it is ontologically necessary.
Benefits
Allow adopters to decide which property is needed.
Risks
The submitter is unaware of risks associated with this change.
Competencies demonstrated
Adopter creates an object when the existence of an object is known but an associated property is not known.
Solution suggestion
Change minCount to 0 from 1 on the following properties:
This is proposed as a FastTrack change
Background
Most properties in UCO are optional. Setting minCount = 1 is enforced by SHACL makes a property required. This constraint will create problems in use cases in which a property is known to have existed but the value is not available.
Requirements
Requirement 1
Allow adopters to create an object when the existence of an object is known but an associated property is not known.
Risk / Benefit analysis
The proposed change allows adopters to decide which property is needed, except when it is ontologically necessary.
Benefits
Allow adopters to decide which property is needed.
Risks
The submitter is unaware of risks associated with this change.
Competencies demonstrated
Adopter creates an object when the existence of an object is known but an associated property is not known.
Solution suggestion
Change minCount to 0 from 1 on the following properties:
Coordination
develop