-
Notifications
You must be signed in to change notification settings - Fork 16
ResourceDiscovery: This patch adds a new resource discovery mechanism. #196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
The intention is to allow for a way to advertise the existence of resources at the OCM server. Signed-off-by: Micke Nordin <[email protected]>
{ | ||
"server": "OCM Server 1", | ||
"resources": [ | ||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe individual resources could be aligned to protocol in Discovery? E.g. when a resource is only available via webdav, webapp or some other protocol?
How do I know if I need to send a ShareRequest as in #194 ?
I tried fixing the merge conflict and line length, failed on the line length 😅 |
IETF-RFC.md
Outdated
* OPTIONAL: `rocrate` - an embedded JSON object following the | ||
[ROCRATE](https://www.researchobject.org/ro-crate/specification/1.1/data-entities.html) | ||
data-entities specification. | ||
* REQUIRED: `id` - the unique identifier of the resource at the OCM Server |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's nitpicking on my side, I think we should keep the names consistent across the endpoints.
The providerId
is from share creation
* REQUIRED: `id` - the unique identifier of the resource at the OCM Server | |
* REQUIRED: `providerId` - the unique identifier of the resource at the OCM Server |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@KrausMatthias yes, I think it should have name like resourceId
or something like that instead of providerId
and this is #196 😄
Co-authored-by: Mahdi Baghbani <[email protected]>
The intention is to allow for a way to advertise the existence of resources at the OCM server.