SaaSHub helps you find the best software and product alternatives Learn more →
Specifications Alternatives
Similar projects and alternatives to specifications
-
-
jc
CLI tool and python library that converts the output of popular command-line tools, file-types, and common strings to JSON, YAML, or Dictionaries. This allows piping of output to tools like jq and simplifying automation scripts.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
binary-experiments
Experiments with various binary formats based on Jevko.
-
-
easyjevko.js
A JavaScript library for Easy Jevko -- a simple data format built on Jevko.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
mint-lang
:leaves: A refreshing programming language for the front-end web
-
-
markup-experiments
A collection of experiments with Jevko and text markup.
-
interjevko.js
Experimental Schema-based Minimal Data Interchange with Jevko.
-
-
community
Features Jevko-related things created by various authors (by jevko)
-
-
-
-
queryjevko.js
Functions to convert between complex values and a human-readable format which fits into URL query strings.
-
-
algebralang
at this time this is some example code of a language I want to build
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better specifications alternative or higher similarity.
specifications reviews and mentions
Posts with mentions or reviews of specifications.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-03.
-
SVGs as Elm Code
Notice that here I used a convention where names which end with "=" become XML attributes, whereas names which don't become children.
I have used the same convention here (except I don't bother with transforming names with spaces into camelCase): https://github.com/jevko/specifications/blob/master/easyjevk... to generate this HTML file: https://htmlpreview.github.io/?https://github.com/jevko/spec...
Now I intend to write specifications that codify conventions like this into different formats based on this fundamental syntax of square brackets.
It can be useful for all kinds of things. Its advantage is extreme simplicity and flexibility.
BTW, for clarity I have to say that the format that I used here: https://news.ycombinator.com/item?id=32995047 does a bit more transformations -- it actually sometimes treats whitespace as a separator (e.g. in `svg width[391]` space is a separator). That allows for extreme conciseness, but is not necessary and introduces complexity.
-
Jc – JSONifies the output of many CLI tools
A plain Jevko parser simply turns your unicode sequence into a tree which has its fragments as leaves/labels.
No data types on that level, much like in XML.
Now above that level there is several ways to differentiate between them.
The simplest pragmatic way is a kind of type inference: if a text parses as a number, it's a number, if it's "true" or "false", it's a boolean. Otherwise it's a string. If you know the implicit schema of your data then this will be sufficient to get the job done.
Otherwise you employ a separate schema -- JC in particular has per-parser schemas anyway, so that's covered in this case.
Or you do "syntax-driven" data types, similar to JSON, e.g. strings start w/ "'".
Here is a shitty demo: https://jevko.github.io/interjevko.bundle.html
It shows schema inference from JSON and the schemaless (syntax-driven) flavor.
Jevko itself is stable and formally specified: https://github.com/jevko/specifications/blob/master/spec-sta...
It's very easy to write a parser in any language (I've written one in several) and from there start using it.
However, I am still very much working on specifications for formats above Jevko. I have some recent implementations of the simplest possible format which converts Jevko to arrays/objects/strings:
-
Jevko: a minimal general-purpose syntax
Thank you for your feedback. Can you clarify?
What is the "first page" that you are referring to?
Can you paste a link to it along with the broken examples link?
This Hacker News submission features the blog post under this URL:
https://djedr.github.io/posts/jevko-2022-02-22.html
Clearly, you are not talking about this page, as that contains multiple links rather than a singular link.
Perhaps you are talking about the specification which is here:
https://github.com/jevko/specifications/blob/master/spec-sta...
(linked from the blog post)
and here:
(linked from jevko.org)
All three link to Jevko examples here:
https://github.com/jevko/examples
but all these examples links seem to be correct on my end.
I agree about the importance of examples, and I try to lead with them on jevko.org and jevko.github.io (which are the front pages of Jevko -- possibly I should merge them into one).
However a formal specification is not necessarily the place to put the leading examples.
This is also where the Subjevko rule is defined. It isn't quite introduced as "known knowledge" -- the purpose of a specification is to define the unknown, more or less from the ground up. This is also why specifications tend to get a little abstract. Jevko's spec is no exception. This should be in line with expectations of authors of tools such as parsers, validators, generators, or other kinds of processors, for which the spec is the authoritative reference.
It is not necessarily the best first place to look for explanation, if you are approaching from a more casual side.
I agree that from that side a clear picture of what Jevko is and how it can be used is still lacking. I certainly should add more examples and explain the concepts with analogies.
So I appreciate the essence of your advice and hope I'll manage to improve on that.
- Syntax Design
-
A note from our sponsor - SaaSHub
www.saashub.com | 18 Apr 2024
Stats
Basic specifications repo stats
6
9
4.1
4 months ago
jevko/specifications is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of specifications is HTML.
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com