| Master | |
|---|---|
| ShEx Lite CI |  |
| AWS CI |  |
| Code Coverage |  |
ShEx Lite is a lightweight version of ShEx that has as an aim reduce the complexity of the syntax, improve the semactic analisis of the schemas and boost the performance of the validation process.
One of the restrictions of the language is that it represents a subset of ShEx. Therefore any source code developed in shex-lite format will be completly compatible with ShEx implementations. But although it is inspired in those ShEx implementations it is a complete independent language, it has its own syntax, semantics, features, compiler and validation process.
To learn more about ShEx-Lite, please see the paper presented at ISWC-2020 demos track.
As a whole, the ShEx-Lite compiler is principally responsible for translating Shex-Lite source code into dofferent intermediate representations like Java, Python or HTML. However, the Shex-Lite compiler front-end is ready for integration with other tools like IDE and syntax coloring thanks to its API design inspired in modern compilers like Roslyn, SwiftC or RustC.
Mainly the compiler is build in 5 major stages:
-
The source code is translated in to a Syntax Tree, that is a tree that contains all the tokens generated by the lexer in a tree structure generated from the rules of the grammar.
-
The Syntax Tre is parsed again to remove all unneed tokens like semicolons, braces and parenthesis. That way the Abstract Syntax Tree is formed.
-
Fom the AST we apply the semantic analysis and transformations to transform the tree in to a graph that is called the Shex-lite Intermediate Language. This graph contains information like where a definition took place and adds all of those information to other nodes.
-
Once we have the Intermediate Language we perform an analysis to validate that it is consistent. There is no missing references and things like that.
-
Finally the compiler generates the code for the different intermediate representations.
To look deeper to the compiler the following picture illustrates perfectly the data-flow:
Contributions to ShEx Lite are welcomed and encouraged!
To be a truly great community, shex-lite needs to welcome developers from all walks of life, with different backgrounds, and with a wide range of experience. A diverse and friendly community will have more great ideas, more unique perspectives, and produce more great code. We will work diligently to make the ShEx Lite community welcoming to everyone.
To give clarity of what is expected of our members, ShEx Lite has adopted the code of conduct defined by the Contributor Covenant. This document is used across many open source communities, and we think it articulates our values well.
If you want to contribute to ShEx-Lite the best and fastest way is to submit a proposal about a change that you would like to integrate with the project. For example: If you find that would be interesting to add a new SIL Generator for a language just submit a proposal with your idea and listen for the feedback of the core team and the comunity. We love to have proposals.
To submit your proposal we encourage you to use the GitHub issues system. You just have to click on create new issue and select the proposal template. And don't worry, if something is not up to the standards we will contact you in order to try to find a solution.
Shex-lite is a project that always maintains a minimum view of one year onwards, in this way we can anticipate different demands from users. Currently our roadmap is hold here [SLI-0090] 🚀 Long Term Roadmap (LTR).
These instructions give the most direct path to a working ShEx Lite development environment. To build from source you will need about 2Gb of disk space for sources. Depending on your machine, a clean build can take a few minutes. Naturally, incremental builds are much faster.
ShEx Lite is developed using scala PL and compiles against the JVM. Therefore all JVM supported systems are currently supported as host development operating system.
The compiler of ShEx Lite is build using scala language, that means that you will need to install Scala in order to be able to compile the sources.
Currently ShEx Lite uses scala 2.13.1.
We also encourage you to use the IDE IntelliJ. ShEx Lite was developed using this IDE and already includes some directives in the sbt to ensure that the project is imported and set up correctly.
First create a directory for all ShEx Lite sources:
mkdir shex-lite-sources
cd shex-lite-sourcesCloning the repository containing the sources:
git clone https://github.com/weso/shex-lite.git .ShEx-Lite uses SBT and scala. So build the project is as easy as go to the root directory of the project and execute:
sbt assemblyAfter building the .jar this tool can be used be means of the following instruction-set.
Usage
shexlc [options] <files> ... : Compile and generate target domain model objects
Options
-hw, --hide-warn : If present will hide the warnings
--java-pkg=STRING : If present will generate java domain object models with the given package
--out-dir=STRING : Sets the out directory where the sources will be generated
Arguments
<files> : ShEx-Lite sources to compile
We encourage you to add as much tests as possible and then run the previous existing ones with your new tests. As more tests we can do more confident about its behaviour that we will be. In the folder test you will find all resources that might be need.
In order to execute all tests locally you will need SBT. Again, testing is super easy and doesn't take too long. You just have to execute:
sbt testBe sure to look through the docs directory for more information about the compiler. In particular, the documents titled Debugging the ShEx Lite Compiler and Continuous Integration for ShEx Lite are very helpful to understand before submitting your first PR.
To read the compiler documentation, start by installing the Bikeshed documentation generator tool by runing the command:
git clone https://github.com/tabatkins/bikeshed.git
pip install --editable $PWD/bikeshed
bikeshed updateOnce complete, you can build the ShEx Lite documentation by changing directory into docs and typing ./scripts/build-doc.sh. This compiles the .bs files in the docs directory into HTML in the doc directory.
Many of the docs are out of date, but you can see some historical design
documents in the doc directory.
- Guillermo Facundo Colunga - Initial work - thewilly
- Alejandro González Hevia - Core Team - alejgh
- Jose Emilio Labra Gayo - Core Team - labra
- Daniel Fernández Álvarez - Core Team - danifdezalvarez
See also the list of contributors who participated in this project.
The project is completely open source and therefore they accept collaborations from different projects from all over the world including:
The Hercules ASIO project focuses on creating an ontological infrastructure and a semantic architecture to manage the administration of research in the environment of Spanish research centers and universities.
The HERCULES-Semantics of University Research Data project has a budget of Five Million Four Hundred Sixty Two Thousand Six Hundred Euros with an ERDF co-financing of 80%, therefore the European Regional Development Fund (ERDF), through the then Ministry of Economy, Industry and Competitiveness (currently the Ministry of Science and Innovation) as the Intermediate Body of the ERDF Smart Growth Operational Program - POCint (now the Multi-regional Operational Program of Spain - POPE) makes a contribution of Four Million Three Hundred Seventy Thousand Eighty euros.
ShEx Lite is primarily distributed under the terms of both the MIT license and the GNU General Public License (Version 3.0), with portions covered by various licenses.
See LICENSE-MIT, LICENSE-GNU, and LICENSE for details.
The ShEx Lite language is an open source, community project governed by a core team. It is also sponsored by the Web Semantics Oviedo Research Group at University of Oviedo ("WESO"), which owns and protects the ShEx Lite trademark and logo.
If you want to use these names or brands, please read the media guide.
Third-party logos may be subject to third-party copyrights and trademarks. See Licenses for details.