Some issues that may be close to resolution

I believe the following tickets may be reasonably close to a resolution 
and could be tackled in one of the next meetings. Of course, there are 
several "larger" topics around, yet it is also unsatisfactory to have 
easy fixes unresolved. Meeting time is sparse, yet if too few people 
participate in the Proposals page or email discussion, how else can we 
ever resolve these issues...

- ISSUE-78 (abstract classes). Given the deleting of sh:ShapeClass, I 
don't see how I could veto dropping sh:abstract.

- ISSUE-96 (violation IDs). All open proposals include URIs for each 
constraint component, and these align with the mechanism used by the 
extension mechanism. Not sure what is holding us from closing this.

- ISSUE-105 (defined prefixes). I got the feeling from the minutes that 
everyone can at least live with the sh:prefix property, and it would 
help implementers if we could use this to make progress.

- ISSUE-123 (sh:directType). With Arthur's departure I don't get the 
feeling that there is much support for sh:directType left, so I believe 
we could have a strawpoll to just drop it.

- ISSUE-136 (property pair names): Several proposals have been made 
here, and I believe this is just a matter of picking some names.

See also: https://www.w3.org/2014/data-shapes/wiki/Proposals

Holger

Received on Wednesday, 6 April 2016 08:32:11 UTC