There is no such content in this group
Posts
Reminder - Web Conference Today 30-May 14:00 UTC
Hi all, our meeting is ca. 3.5 hours from now. Here are the notes from the last meeting: https://www.rd-alliance.org/group/research-data-collections-wg/post/note... I converted the specification document to Markdown and added it on Github: https://github.com/RDACollectionsWG/specification Hope to see you in a bit, Frederik=1 | Add new comment
whoops
sorry for the suprious post ... have to love that autocorrect. But I suppose it could have been worse :-)0 | Add new comment
Notes from today's webconference. Next Call: 30 May 14:00 UTC
Discussion Notes: - For https://github.com/RDACollectionsWG/apidocs/issues/2 we either need to upgrade to OpenAPI 3.0, or change schema for GET /property to not define a return value, or leave it as is, returning the member item. We decided moving to Open API 3.0 is out of scope for now. Bridget will investigate whether we can leave it undefined. If not we will leave it as is. We will open separate issues for the future for the0 | Add new comment
Comments about the specifications
Dear all, as I will not be able to attend the meeting today, I'm pasting below my suggestions for the document with the specifications. Do you think it would be useful if I contribute with some description of the implementation/use case at GEOFON? All the best for the call today! *********************************************** * Why "Collection state" and subdivide in a 3-tuple? It could be better to remove this extra level. Does it match the JSON structure? No. * In JSON it is well organized: “id”, “capabilities” and4 | Add new comment
reminder - web conference tomorrow 9-May 14:00 UTC
Check the notes from last meeting to remind yourself of action items: https://www.rd-alliance.org/group/research-data-collections-wg/post/note... Hope to see you all there! Bridget1 | Add new comment
Notes from today's call; Next call 9 May 14:00 UTC
Notes from the session at P9 are posted on the wiki at https://www.rd-alliance.org/p9-meeing-notes response was generally very positive versioning discussion needs to be tackled by a wider audience and is mostly out of scope for this WG, other than what we have already Specific feedback on the API Specification have been turned into issues at https://github.com/rdACollectionsWG/apidocs/issues Discussion Notes:0 | Add new comment
reminder: Web Conference tomorrow
Hi everyone, Just a reminder that we have our web conference tomorrow at 14:00 UTC (10am EST, 16:00 CEST). I guess the agenda will include recapping the plenary activities, and making a concrete plan for the last 6 months of activity. Talk to you tomorrow! Bridget0 | Add new comment
After the plenary ....
... is of course before the next plenary ... ;-) I just came across the OASIS OData specification which seems to be a nice way of creating standardized, self-describing REST interfaces: http://www.odata.org/ Some of this stuff should be easy adoptable to our collections API, some would be harder, some makes no sense. What do you think? Best, Tom -- Dr. Thomas Zastrow Max Planck Computing and Data Facility (MPCDF) Gießenbachstr. 2, D-85748 Garching bei München, Germany3 | Add new comment
Re: RDA collection data model
Hello Juha, thank you for pointing this out - I believe that this would fit into the collections work in terms of extensions (of e.g. additional collection properties, or some elements for the controlled vocabs we foresee) by a user community, specific implementation, use case or similar. So may want to include a reference to this in the conceptual document we will put out along with the specification. Best, Tobias1 | Add new comment
Printed out ....
... the 2-pager is printed out, looking forward to see all of you tomorrow in Barcelona! -- Dr. Thomas Zastrow Max Planck Computing and Data Facility (MPCDF) Gießenbachstr. 2, D-85748 Garching bei München, Germany Tel +49-89-3299-1457 http://www.mpcdf.de0 | Add new comment