Meeting minutes
Roll call, select scribe, agenda
Bert: any topics missing?
Minutes of last call
Bert: hearing no objections
Action items
<Bert> actions
<simonstey> action-3
<trackbot> action-3 Bert Bos to Clarify which github space we can use W3C's github space or if we need something else -- due 2018-08-13 -- OPEN
<Bert> trackbot, close action 3
<trackbot> Sorry, Bert, I don't understand 'trackbot, close action 3'. Please refer to <http://
bert: Bert will create a git repo soon.
… trackbot, close action3
<trackbot> Sorry, AxelPollleres, I don't understand 'trackbot, close action3'. Please refer to <http://
<Bert> action 6?
<simonstey> close action-3
<trackbot> Closed action-3.
bert: close action 3
<simonstey> action-6
<trackbot> action-6 Michael Markevich to Draft something about Opera use case(s) -- due 2018-08-13 -- OPEN
<simonstey> action-7
<trackbot> action-7 Bert Bos to Add some overview of SPECIAL use case(s) -- due 2018-08-13 -- OPEN
<simonstey> action-8
<trackbot> action-8 Axel Polleres to Add some more starting point vocabulary stubs -- due 2018-08-13 -- OPEN
<simonstey> close action-8
<trackbot> Closed action-8.
bert: close action-8
<trackbot> Closed action-8.
<Bert> action-9
<trackbot> action-9 Axel Polleres to Include links to irc and minutes into the agenda next time -- due 2018-08-14 -- OPEN
<Bert> action-10
<trackbot> action-10 Axel Polleres to Organize a call later on 30th after the mydata session or on friday morning to sync with people jooining through the conference.... will contact organizers. -- due 2018-08-14 -- OPEN
bert: on 29th a dinner table for dinner table for "Semantic Interoparability" at Manala restaurant
… http://
<simonstey> trackbot, comment action-10 we'll have a dinner in the evening before the f2f meeting at mydata; on 29th a dinner table for dinner table for "Semantic Interoparability" at Manala restaurant (http://
<trackbot> Notes added to action-10 Organize a call later on 30th after the mydata session or on friday morning to sync with people jooining through the conference.... will contact organizers..
bert: our session is on 30th in the morning:
… https://
… on 30th afternoon https://
<simonstey> AxelPollleres: organizing an openspace session too
<simonstey> ... openspace session is after lunch, don't know which session it will be exactly though
bert: enough bandwidth given we will try to dial in the group for the open space session,
… https://
… there are 4 open space sessions yet, not yet sure what slot we get.
ACTION: axel to talk to Joss about Mydata open space session and maybe try to pre-fix a slot.
<trackbot> Created ACTION-16 - Talk to joss about mydata open space session and maybe try to pre-fix a slot. [on Axel Polleres - due 2018-08-28].
<simonstey> action-11
<trackbot> action-11 Axel Polleres to Reach out to industrial data spaces project (germany) and another austrian big data project (dma). -- due 2018-08-14 -- OPEN
<simonstey> action-12
<trackbot> action-12 Simon Steyskal to Look over requirements template -- due 2018-08-14 -- OPEN
<simonstey> https://
bert: https://
Simon: the template allows to vote on requirements in between calls.
ACTION: Axel to try to modify the rquirements teamplate and instantiate it for some of the items on https://
<trackbot> Created ACTION-17 - Try to modify the rquirements teamplate and instantiate it for some of the items on https://
<simonstey> action-13
<trackbot> action-13 Stefano Bocconi to Propose use case(s) for the decode project -- due 2018-08-14 -- OPEN
<simonstey> action-14
<trackbot> action-14 Axel Polleres to Ask hendrik for edition ieee 7012 -- due 2018-08-14 -- OPEN
<simonstey> https://
<simonstey> action-15
<trackbot> action-15 Eva Schlehahn to look over use cases template -- due 2018-08-14 -- OPEN
<Bert> Eva's e-mail on use case template
<simonstey> AxelPollleres: Ben and I will talk about our efforts
<Eva__ULD_> I sent my suggestions on the use case and on the requirements templates per email - so action done ;)
ACTION: Javier to update the use case template wrt. Eva's version
<trackbot> Error finding 'Javier'. You can review and register nicknames at <https://
Javier: we probably need first the use cases to discuss more about requirements
Axel: we should take the list from the workshop as starting points, see action above.
how to combine vocabularies
<Eva__ULD_> I think it might depend heavily on the use cases which kind of taxonomies and vocabularies we need
<harsh> Seems audio isn't working :(
<harsh> But I agree with Axel
Axel: maybe try typing? ☺
<harsh> My question was: in light of what we discussed, should we start listing concepts and properties from listed vocabularies we might find interesting
Axel: Can we agree that our goal is to work within one namespace and connect to it, instead of creating a coglomerate of voabularies?
simon: I don't think we should invent an own use case, if we have one vocab that covers all.
… we maybe only need a "best practices" document.
… in ORDL you can specify consent, but not it's components.
Axel: I think we could have a JSON-LD profile that describes the whole policies.
… and collect our core terms.
… single namespace we mape to or JSON-LD profile combining different namespaces, is not so relevant in the end, but coherend presentation of the terms we support and need.
Javier: Are we closing the use cases or are we calling for external use cases?
… so far they seem close to a couple of European projects.
<harsh> Perhaps we could have a cut-off line for use-cases, after which we turn those collected use-cases into requirements?
Axel: we need more use cases and should spread the word as far as we can.
<harsh> Issue would be a good idea
ISSUE: timeline/schedule, when should we stop collecting additional use cases?
<trackbot> Created ISSUE-1 - Timeline/schedule, when should we stop collecting additional use cases?. Please complete additional details at <https://
Axel: ISSUE-1: postponed until after Mydata
<trackbot> Notes added to ISSUE-1 Timeline/schedule, when should we stop collecting additional use cases?.
Axel: PROPOSED: next call 4 september, same time
+1: -)
<simonstey> +1
<Ramisa> +1
RESOLUTION: next call 4 september, same time.
+1: adjourned.