You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"aCollectionOf": {
"description": "If the entry type is a collection of other entry types, (e.g. a Dataset is a collection of Records), then this attribute must list the entry types that could be included. One collection type could be defined as included more than one entry type (e.g. a Dataset could include Individuals or Genomic Variants), in such cases the entries are alternative, meaning that a given instance of this entry type could be of only one of the types (e.g. a given Dataset contains Individuals, while another Dataset could contain Genomic Variants, but not both at once).",
"includedConcepts": {
"$ref": "../common/basicElement.json",
"type": "array"
}
},
"includedConcepts" here is something to be ignored by schemas, so basically equivalent
"aCollectionOf": {}
Best,
Dmitry
The text was updated successfully, but these errors were encountered:
This one is trickier , IMO, as it will break the current implementations.
The reason for includedConcepts was to make clear what the aCollectionOf attributes mean.
It could be redudant, but could not be removed now w/o a proper deprecation.
Could the alternative be considering aCollectionOf as an object that has only one property and ammend the spec like that w/o breaking changes?
Hi all,
There is invalid entryTypeDefinition.aCollectionOf property definition in the spec.
"includedConcepts"
here is something to be ignored by schemas, so basically equivalentBest,
Dmitry
The text was updated successfully, but these errors were encountered: