Schemas for a more fine-grained representation of services#62
Conversation
| "accessibility": { | ||
| "_instruction": "Add the accessibility of this deployed interface.", | ||
| "_linkedTypes": [ | ||
| "controlledTerms.ProductAccessibility" |
There was a problem hiding this comment.
only Accessibility now (since the schema can be also used for non-products)
There was a problem hiding this comment.
maybe we don't want to call this service deployment but rather deployment only? and also making the service optional? or did we say now everything with an interface is a service?
There was a problem hiding this comment.
hasPart for implemented configurations need to be covered in here: CommonCoordinateFrameworkVersion, AnatomicalAtlasVersion, ModelVersion (maybe include also LaunchConfiguration?)
There was a problem hiding this comment.
now solved through dependsOn and uses
| "type": "array", | ||
| "minItems": 1, | ||
| "uniqueItems": true, | ||
| "_embeddedTypes": [ |
There was a problem hiding this comment.
linkedType and besides DeployedInterface should also link to all researchProductVersions; either needs a distinct list of types or a new categegory for all RPVs and DeployedInterface
lzehl
left a comment
lzehl
left a comment
There was a problem hiding this comment.
@olinux @apdavison please check the updated uses and dependsOn and see if you agree
2 participants
(digital or physical).
Based on discussions with @lzehl and @olinux - see design document
Related: