ISSUE-2: What skills are expected/required from our audience?
Audience skills
What skills are expected/required from our audience?
- State:
- CLOSED
- Product:
- SHACL Spec
- Raised by:
- Arnaud Le Hors
- Opened on:
- 2014-11-18
- Description:
- We've started discussing who the audience for Shapes is but have not discussed what skills the audience is expected to have.
We can assume general understanding of the basic RDF data model but what about RDFS, SPARQL, and OWL? Can we expect users of Shapes to be expert in these? Anything else?
See https://www.w3.org/2014/data-shapes/wiki/Issue_2:_Required_Skills_of_Audience - Related Actions Items:
- No related actions
- Related emails:
- ISSUE-2: Suggestion to close without action (from holger@topquadrant.com on 2015-07-28)
- Re: rdfdatashapestracker-ISSUE-2 (Audience skills): What skills is expected/required from our audience? (from holger@topquadrant.com on 2014-11-19)
- Re: rdfdatashapestracker-ISSUE-2 (Audience skills): What skills is expected/required from our audience? (from eric@w3.org on 2014-11-18)
- rdfdatashapestracker-ISSUE-2 (Audience skills): What skills is expected/required from our audience? (from sysbot+tracker@w3.org on 2014-11-18)
- Re: rdfdatashapestracker-ISSUE-2 (Audience skills): What skills is expected/required from our audience? (from lehors@us.ibm.com on 2014-11-18)
Related notes:
I believe the question is not only what skills we can expect, but rather how to attract people who do not have the necessary full skills without blocking out the advanced users. The approach suggested by SPIN is to have a high-level language based on Templates, where people just need to fill in the blanks, e.g. "cardinality", and then to have the full power of SPARQL for the more complex cases. We should not limit the usefulness of Shapes to the lowest common denominator only because not everyone knows SPARQL. And if not SPARQL, then what else?
Holger Knublauch, 18 Nov 2014, 23:02:02Resolution: Close ISSUE-2, it is no longer relevant.
http://www.w3.org/2015/07/30-shapes-minutes.html#resolution02
Display change log
