This thread follows on from an audio conference between @mariana, @josefkreitmayer, @gandhiano, @jnardi and @mattw on 2016-03-17. Notes on that conference can be found at https://text.allmende.io/p/SEE_LOD_talks. I’m also drawing the attention of @benb from REL (see his related thread ), @almereyda, @colmjunior to this thread.
The main topic under discussion was the use of DCAP-SSE and the ESS Global vocabulary, created by the ESS Global task-force.
The Institute for Solidarity Economics (that’s where I work) has already committed to the use of DCAP-SSE and the ESS Global vocabulary. We see the path ahead as an iterative process: when we come up with a requirement that we don’t know how to satisfy with the current DCAP and vocabulary, then we will review it with @mariana, and see how best to deal with it. I expect that this will lead either to us getting better informed about how to use the existing DCAP, or adding some new predicates and objects, which may or may not be included in a future version of the DCAP or vocabulary.
During the audio conference, it seems that there are others in the community who are interested in using the work of ESS Global, and that @mariana is happy to continue the development of the DCAP and vocabulary to cover new requirements for data within the SSE. The more of us involved in this process, the better the coverage, the better the work can be shared, and the better interoperability will be achieved.
Areas of work
- Do the narratives and movements, that already contribute to TransforMap fit into the narrative of Social and Solidarity Economy?
- Functional requirements and use-cases not covered by the current work of ESS Global.
- Technical specifications.
- Technical validation issues. Currently, @mattw is traking these in github. e.g. https://github.com/p6data-coop/ise-linked-open-data/issues/3 and https://github.com/p6data-coop/ise-linked-open-data/issues/4.
- Technical implementation of the DCAP and ESS Global vocabulary. I know, for example, that @mariana and her team have been having problems with purl.org.
I’d be infavour of setting up a github to capture this work. Any other suggestions? Maybe some of the wider TransforMap discussions belong on this discourse, but I think that technical specs, use-cases, functional requirements, issues, could all be done well on github. @mariana, is there already something in existence within the ESS Global task-force that would be good for this work (I hate creating new things unnecessarily!)
Perhaps I am jumping ahead too quickly, because I am very enthusiastic about this work I’d love to know how you all think about this next step with ESS Global. Do you want to be involved in this work?