weso / yashe Goto Github PK

It seems that the import keyword is not accepted?

The import keyword is part of the grammar. See production rule: [4½] in http://shex.io/shex-semantics/index.html#shexc

Still missing some small parts of the grammar that are not LL(1)

The folder doc contains some html files which seem to be out-of-date as they refer to queries instead of ShEx schemas.

Internally, there are also some methods like storeQuery which should be renamed to avoid confusion.

Upload Button Tooltip is wrong

Make a ShEx Pretty Print

• Add WikiShape
• Correct ShExAuthor href
• Correct RdfShape href
• Add more info about tools that use YASHE

The following code:

<S> {
  <p> . {1,3}
}

gives a false error in the cardinality.

var yashe = YASHE.fromTextArea(document.getElementById('texAreaId'), {
    fontSize:30
});

Fontsize option is not working

YASHE main button is wrong in the Docs page.
Maybe I should remove the "About" button too... I think it´s unnecessary

I use YASHE a lot to verify the structure of the ShEx I write. I typically copy and paste between the Wikidata editor and YASHE.
However, today I wrote a ShEx which contains an IMPORT. However, when checked on YASHE, an error was given.

Would it be possible to support IMPORT in YASHE?

Current Grammar don´t support some things:

• "import" keyword ✔️ (#103 )
• ^^ is not recognized -> rule [129s] rdfLiteral ✔️ (#103 )
• $ conflict between rule [40] and [42] ✔️ (#103 )

Allow the '.' in PN_LOCAL in order to do thinks like "codes:good.~"

Example 44 Validating RDF Data Book:

prefix codes: <http://example.codes/>  

:Product {   
      :status [ codes:good.~ codes:bad.~ ] 
}

Linked Isue (shexSpec/shex#99)

Upgrade all the dependencies to the last version to avoid warnings.

This input

  <#sequence_assembly>  {
    ( p:P2576 { ps:P2576  xsd:string } |
      ps:P4333 {xsd:string    p:P4333 } )  
  }

Produces this output after call the prettyprinter:

<#sequence_assembly>  {
  ( p:P2576 {
    ps:P2576  xsd:string } xsd:string p:P4333  
  }|  ps:P4333 { )  
}

Currently, the pretty-printer takes all of the directives and starts and sets them at the top of the document. This is wrong because it can affect to the semantic of the document.

It might be good to make some YASHE releases

By a shortcut or something like that, add Wikidata comments automatically after an entity or property.
Eg:

Before:

PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX wd: <http://www.wikidata.org/entity/>
PREFIX wdt: <http://www.wikidata.org/prop/direct/>

<human> {
  wdt:P19 . ?;                 
  wdt:P569 . ? ;              
  wdt:P735 . * ;               
  wdt:P734 . * ;               
  wdt:P106 . * ;               
  wdt:P27 @<country> *; 	  
  wdt:P22 @<human> *;       
  wdt:P25 @<human> *;          
  wdt:P3373 @<human> *;         
  wdt:P26 @<human> *;          
  wdt:P40 @<human> *;          
  wdt:P1038 @<human> *;       
}

After:

PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX wd: <http://www.wikidata.org/entity/>
PREFIX wdt: <http://www.wikidata.org/prop/direct/>

<human> {
  wdt:P19 . ?;                  # place of birth
  wdt:P569 . ? ;                # date of birth
  wdt:P735 . * ;                # given name
  wdt:P734 . * ;                # family name
  wdt:P106 . * ;                # occupation
  wdt:P27 @<country> *; 	    # country of citizenship
  wdt:P22 @<human> *;           # father
  wdt:P25 @<human> *;           # mother
  wdt:P3373 @<human> *;         # sibling
  wdt:P26 @<human> *;           # spouse
  wdt:P40 @<human> *;           # children
  wdt:P1038 @<human> *;         # relatives
}

There is a Codepen example for YASHE initialization that we can incorporate to YASHE docs page

The shapes autocompleter doesn't work with nonprefixed shapes until a prefixed shape is defined

E.g: 'Base has already been declared'

Red IRI should be blue

Annotations has stopped working:

dct:language [ wd:Q9035 ]
    // rdf:label "language"
    // rdf:comment "The language of lexeme must be Danish." ;

I think the new REGEXP token is to blame...

Change the share button on dark theme

Make some test using cypress

Add Wikidata Examples to the YASHE homepage

• Change REGEXP token color to yellow

YASHE does not recognize well regular expressions.

Example 38 Validating RDF Data Book:

:Product {  
    schema:name       xsd:string  MaxLength 10 ;  
    schema:weight     xsd:decimal MinInclusive 1 MaxInclusive 200 ;  
    schema:sku        /^[A-Z0-9]{10,20}$/ ; }

Grammar Rule -> [63] REGEXP

A time out was added on yashe.on("change") to fix some bugs.
Maybe the timeout is not needed with yashe.on("changes") that was deleted

• Design
• Functionality

• Lantag (e.g "@es") -> rule [129s] rdfLiteral

It does not recognize things like this:

:SpanishW3CPeople {
schema:telephone [ "+34"~ ] ;
schema:url [ http://www.W3C.es/Personal~ ]
}

There should be an error msg in the last line due to the lack of '}'

This should throw an error:

:Product ( 
  schema:name

Before PrettyPrint:

PREFIX wd:    <http://www.wikidata.org/entity/>
PREFIX wdt:   <http://www.wikidata.org/prop/direct/>

<human> {
  wdt:P31  {  wd:Q5 #asd
    .  } 
}

After PrettyPrint: (wrong output)

PREFIX wd:   <http://www.wikidata.org/entity/>
PREFIX wdt:  <http://www.wikidata.org/prop/direct/>


<human>  {
  wdt:P31  {  wd:Q5  . #asd } 
}

On the dark mode is already implemented

If a ShapeRef uses a non defined prefix, show prefix error and non defined shape error together.

In the Wikidata demo, when you hover over a predicate in a TripleExpression, it fetches the schema:description. Does it pick the language based on browser preferences?

It would be cool to extend this functionality by adding annotations to shapes as well, e.g.

<#P352_uniprot_id> {
	ps:P352 LITERAL ;
	prov:wasDerivedFrom IRI;
}
 // schema:description "UniProt identifier"@en
 // schema:description "identificador de UniProt"@es # just a guess

The editor could hide all of them except those in the preferred language so it wouldn't get to messy.

Prefixes Collapse doesn't work

• [Ctrl|Cmd]-Z
• [Ctrl|Cmd]-Y

Actual 'a' keyword is case insensitive and it shouldn't

Publish YASHE as an npm package

For some reason, the wikibase autocompleter doesn't work inside ValueSets

Document YASHE events:

yashe.on("upload")
yashe.on("download")
...

There is no information about how to download/build the system.

Add some releases that can be downloaded, maybe from a CDN or from NPM as with YASQE

The "Fork me on GitHub" button is wrong in the docs page. I suppose that I forgot to change the href from YASQE

There is a mistake on the rule [22] of the [shex11-grammar.pl] :(https://github.com/weso/YASHE/blob/gh-pages/lib/grammar/shex11-grammar.pl).

 [22] nodeConstraint ::= "LITERAL" stringFacet* 

Should be:

 [22] nodeConstraint ::= "LITERAL" xsFacet* 

If you are typing in capital letters and try to autocomplete it doesn't work
For example:

p -> prefix 👍
P -> 👎

In the features section:

• Add share btn
• Change "Prefix" to "Alias"

In the used by section:

• Add WikiAuthor

Modify the current token colors to adapt them to ShEx