Re: six more 2.0 issues

On Mar 1, 2017, at 10:39 AM, Eric Prud'hommeaux <eric@w3.org> wrote:
> 
> We were down to three issue but then I surveyed the issues with no
> milestone (is:open is:issue no:milestone) and found six that either
> belonged on the 2.0 track or needed an explicit decision otherwise.
> This brings us to nine 2.0 issues:
> 
> 
> #15 Remove "negated properties" from features in Shex.io Webpage and
> in primer primer
> 
>  This calls for some maintenance and wordsmithing. In particular,
>    http://shexspec.github.io/primer/#negated-properties
>    https://shexspec.github.io/spec/#example-negation
>  need to describe the use of the
>    my:predicate . {0}
>  idiom to do simple negation. The spec link is involved as it
>  needs an explicit trace like the examples above it.
> 
> 
> #26 Design a nice logo for ShEx help-wanted webPage
> 
>  Anyone of for some art?  
> 
> 
> #33 Title of document "Shape Expression Vocabulary Terms"
>  vocabularyTerms
> 
>  I think Gregg was hoping that Jesse would take over maintenance of
>  this document.

I'm happy to update it and continue to maintain. I think there's an issue about sx:INF to be resolved. 

> #37 ShapeMap with negative declarations enhancement language-suggestion
> 
>  This is a modest enhancement of the spec to say that a ShapeMap
>  records both positive and negative node/shape associations. We don't
>  prescribe any reporting standard for now so no further work is
>  necessary unless we decide this reflects on the tests.
> 
> 
> #39 Update Antlr grammar to be in synch with the recent changes in BNF
>  Antlr-grammar
> 
>  I think it may be in synch. A simple ShExC-to-ShExJ program written
>  in some ANTLR-supported language would prove that.
> 
> 
> #40 "max": "*" in ShExJ interpreted as xsd:integer vocabularyTerms
> 
>  This should be resolved given the migration to INF. Anyone know
>  otherwise?

There was an objection to sx:INF in favor of sx:Unbounded, I believe. Requires consensus. 

> #41 ^^-style facet arguments Voting-Needed
> 
>  This is prototyped in all relevent repos and should be
>  non-controversial.
> 
> 
> #38 Representing top level shape references bug Voting-Needed
> 
>  I believe this is resolved.
> 
> 
> #42 Use of schema start vs shapeMap language-suggestion spec
> 
>  I thought this was going to be easy but I'm less confident now.
> 
> -- 
> -ericP
> 
> office: +1.617.599.3509
> mobile: +33.6.80.80.35.59
> 
> (eric@w3.org)
> Feel free to forward this message to any list for any purpose other than
> email address distribution.
> 
> There are subtle nuances encoded in font variation and clever layout
> which can only be seen by printing this message on high-clay paper.
>

Received on Wednesday, 1 March 2017 19:26:40 UTC