Improve the favicon according to the logo created at #11

There is a slight difference in the font size of the editors in the ShEx validation section.

Reference/proof of concept: https://codemirror.net/demo/search.html

The application is currently working as expected (mostly). However, not only is more testing required (see #4) but the current tests should be enhanced/fixed, they are disrupting Travis' builds.

In its current state, the UML class diagram displayed as SVG in the ShEx>UML conversion becomes a chaotic tangle of arrows when processing a certain number of shapes with plenty of relations.

It would be of great help to the user to offer a way to navigate/display this info in a more selective, clear method. This is in no way a trivial matter and thus will require some time to prepare.

A couple of approaches have been briefly commented.

• Allowing the user to move and relocate the elements of the diagram to his will. Seems quite complicated... I'll see if there's anything that eases this possibility, but I don't hope for much with the current implementation. Also, with the number of elements that the troublesome diagrams possess, it doesn't really lessen the amount of work required for the user to clarify the information.
• Select a "main" shape and its inmediate neighbours on demand. This one seems more feasible, as well as it's a better option for the user, I'd say. I'll try around and see where it takes me...

In ShEx validate, the font size of YASHE is different to the font size of YaTE.

When the user edits RDF data and changes between different options, the RDF data is lost. It would be better if it were kept in some in-memory storage so the user could use the same RDF data to validate, visualize, etc...

The same functionality could be used also for ShEx and SHACl schemas...

We currently offer 3D visualizations for ShEx (example) thanks to 3dshex.

There are some caveats though:

• After resizing the visualization via CSS to fit our UI constraints, some interactivity is lost (on hover/click events). Looks like the mouse position detected does not correspond with the actual one.

When visualizing a medium size diagram like this one, half of the diagram generated can't be seen.

The RDFShape server provides better support now for errors which could help the visualizations of errors in rdfshape-client.

In particular, the JSON representation of errors in ShEx now returns the the location (line/col) of the RDFNode and the Shape label. It would be great for a user to be able to get a link from the RDFNode/label to the corresponding position in Turtle or in ShEx.

I suppose that this feature will require modifications in YaSHE or YATE, @mistermboy is the functionality in YaSHE/YATE to go to some specific line/col in the editor or maybe highlight it with a different color?

Maybe, the lint extension from codemirror could be useful?

Add a single buttom that allows to check the status of the server

When editing large RDF files, the editor windows have a fixed size which can't be changed. I think it would improve the user experience if it were possible to move those windows...

It would be even better if those windows could be put in any place selected by the user.

The main page contains a typo in this text:

Data [analyis](https://rdfshape.weso.es/dataInfo) and visualization

Should be analysis instead of analyis

Thanks to Bob Ducharme for pointing it out.

It would be nice to have Streaming validation to the SHACL

At this moment, there are several components and utilities that are common with wikishape and could be published to a standalone repository.

We created the shapeComponents repository for that.

It would be nice to be able to merge 3 or more RDF inputs...

El diagrama UML generado con Shumlex posee un comportamiento asociado a las clases al hacer clic (resaltar aquella y sus vecinos). Tal comportamiento se ha perdido con la nueva versión. Parece ser que se genera el diagrama como corresponde en un dummy, del cual se toma el SVG y se reproduce en la ventana final. Esto va bien para el aspecto visual, pero los scripts asociados se pierden por el camino.

We are having similar problems navigating RdfShape and WikiShape (see weso/wikishape#18)

I think several components and utilities that are shared by wikishape and rdfshape should be extracted and put together in a common module which could be pubished to npm.

Then, we could add a dependency from both rdfshape and wikishape to that module.

Once we have created the test-suite, we should have a test for each element in the examples menu that checks that it works.

I noticed that the data visualization example was not working.

The application currently offers two types of visualizations:

• RDF data visualizations (https://rdfshape.weso.es/dataVisualize, https://rdfshape.weso.es/dataMergeVisualize).
• ShEx visualizations (https://rdfshape.weso.es/shExVisualize).

The following problems should be tackled:

• RDF visualizations allow to choose a target image format, but all options return an SVG.
• ShEx visualizations only allow the SVG format.
• We should implement a mechanism in the client API that allows users to query the client only for the image resulting from a visualization. That way, users will be able to embed images generated by RdfShape in their contents.

The input label for ShEx schemas in RDFShape is "Shapes graph". While that terminology is OK for SHACL, in the case of ShEx, it is called Schema.

If those labels are separate, it would be better to ask for "Schema" or "ShEx schema" in the case of ShEx.

In the case of SHACL, it can remain as "Shapes graph" because that's the terminology used in SHACL

When updating to the latest version of Shumlex, the UML visualizations have the angle brackets (<, >) appear as invalid/unknown symbols. This is a minor issue, but it did not happen before.

• Before (0.4.2):
  

• After (0.6.0):
  

The permalink in the ShEx to SHACL option doesn't work at this moment.

Refactor the code to use typescript

In a few places ("About", "This client is already deployed here."), readers are sent to https://rdfshape.weso.es/
That link does not work, but rdfshape.herokuapp.com/ does. So either fix the redirect, or correct the link?

I have created a small test for the DataInfo component at: src/data/tests/dataInfo.test.js.

There are several things that I would like to improve:

1.- The test didn't work because it seems the method document.body.createTextRange is not implemented in jsDom. We found some questions in stack overflow that explain some solutions like this one. We added directly the code and it seems to work...however, it would be better to reuse that code in other components that depend on codeMirror.
2.- I would like to mock the axios calls to the server like it is explained in several places like here.
3.- I would like to test the rest of the components and options.

While implementing some enhancements to the client I realized I couldn't access the pages related to ShEx operations:

• http://rdfshape.weso.es/shExValidate
• http://rdfshape.weso.es/shExValidateEndpoint
• http://rdfshape.weso.es/shExInfo
• http://rdfshape.weso.es/shExVisualize
• http://rdfshape.weso.es/shExConvert
• http://rdfshape.weso.es/shEx2Shacl

All I get is a blank page and the following error in the console:
TypeError: Cannot read property 'line' of undefined
at yashe.bundled.min.js:29480
at s (yashe.bundled.min.js:5605)
at t (yashe.bundled.min.js:5620)
at x.foldCode (yashe.bundled.min.js:5667)
at x.e.collapsePrefixes (yashe.bundled.min.js:28673)
at w (yashe.bundled.min.js:28850)
at Function.v.fromTextArea (yashe.bundled.min.js:28924)
at ShExForm.js:16
at ml (react-dom.production.min.js:4706)
at Fs (react-dom.production.min.js:6471)
vl @ react-dom.production.min.js:4636
react-dom.production.min.js:2835

Does it happen to you as well? @labra @mistermboy
Cant it be related to #19 or am I missing something?

Right now permalinks are too long and they are sometimes shown on hidden places. We should implement the functionalities already present in Wikishape:

• Use shorter permalinks
• Place the permalink buttons on more visible spots
• Allow users to copy the permalinks to their clipboards

Hi,

the UML conversion to ShEx is currently broken. Even when I try to run the example...I only get an error response:

Error response from https://api.rdfshape.weso.es
An error has occurred while creating the ShEx equivalent. Check your inputs.

Cheers
Ralf

When trying to visualize some medium size RDF data like this, the permalink option doesn't seem to work.

The problem may be that the generated URL is longer than expected but if that is the case, some nice error message would be better than the current behaviour.

It seems that the rdfshape client doesn't handle properly Turtle files that contain escaped literals with double quotes. For example something like the following gives a strange error:

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

:alice :name "\"Alice\"" .

The error message is not very helpful and says:

Error response from data/info

syntax error in line 3 near '"'

When one is using the "Merge" option it would be nice to also be able to visualize the merged RDF that resulted.

Example - PNG Generation - Fails
Example - SVG Generation - Succeeds.

Moreover, viz.js seems to be deprecated, so we should look for alternatives or focus on cytoscape.