All Projects → catseye → Specs-on-Spec

catseye / Specs-on-Spec

Licence: other
A collection of language specifications which don't belong anywhere else

Projects that are alternatives of or similar to Specs-on-Spec

RulerZBundle
Symfony Bundle for RulerZ
Stars: ✭ 38 (+192.31%)
Mutual labels:  specifications
f2e-spec
Alibaba Front-end Coding Guidelines and Relevant Tools
Stars: ✭ 548 (+4115.38%)
Mutual labels:  specification
standard-components
A specification for functional UI components
Stars: ✭ 52 (+300%)
Mutual labels:  specification
taylor
Measure twice, cut once. Lisp-like functional language for computable & immutable specifications, interpreted by WebAssembly & the Ethereum Virtual Machine.
Stars: ✭ 30 (+130.77%)
Mutual labels:  specifications
donate-spec
The Missing Donation Specification for Open Source Software
Stars: ✭ 13 (+0%)
Mutual labels:  specification
proposals
Temporal proposals
Stars: ✭ 54 (+315.38%)
Mutual labels:  specification
daikon
Dynamic detection of likely invariants
Stars: ✭ 157 (+1107.69%)
Mutual labels:  specifications
adamant.language.reference
The Adamant Programming Language Reference
Stars: ✭ 18 (+38.46%)
Mutual labels:  specification
MARCspec
📄 MARCspec - A common MARC record path language
Stars: ✭ 21 (+61.54%)
Mutual labels:  specification
tinyspec
Simple syntax for describing REST APIs
Stars: ✭ 95 (+630.77%)
Mutual labels:  specification
Naos
A mildly opiniated modern cloud service architecture blueprint + reference implementation
Stars: ✭ 19 (+46.15%)
Mutual labels:  specifications
flyteidl
Specification of the IR for Flyte workflows and tasks. Also Interfaces for all backend services. https://docs.flyte.org/projects/flyteidl/en/stable/
Stars: ✭ 27 (+107.69%)
Mutual labels:  specification
spec-pattern
Specification design pattern for JavaScript and TypeScript with bonus classes
Stars: ✭ 43 (+230.77%)
Mutual labels:  specification
iscn-specs
International Standard Content Number - decentralized content registry
Stars: ✭ 16 (+23.08%)
Mutual labels:  specifications
specifica
Basic TLA+ related Haskell libraries (parser, evaluator, pretty-printer)
Stars: ✭ 19 (+46.15%)
Mutual labels:  specifications
service-mesh-performance
Standardizing Service Mesh Value Measurement
Stars: ✭ 234 (+1700%)
Mutual labels:  specifications
specifications-ITS-REST
openEHR REST API Specifications
Stars: ✭ 20 (+53.85%)
Mutual labels:  specification
specifications
Track specification elaboration.
Stars: ✭ 17 (+30.77%)
Mutual labels:  specification
klever
Read-only mirror of the Klever Git repository
Stars: ✭ 18 (+38.46%)
Mutual labels:  specification
webspicy
A technology agnostic specification and test framework that yields better coverage for less testing effort.
Stars: ✭ 42 (+223.08%)
Mutual labels:  specification

Specs on Spec

This is a collection of specifications for programming languages that have not been implemented. Indeed, many of them may well be unimplementable.

Most of them were designed, and their specs written, by Chris Pressey of Cat's Eye Technologies; the exceptions are:

  • Startre and *W, which were designed and written by John Colagioia; and
  • TURKEY BOMB, which (I baldly assert) was found unexpectedly one day under a stack of Byte magazines at a charity shop.

Also, I say "programming language", but of course that term is rather flexible 'round these parts:

  • Madison is a language for writing formal proofs;
  • MDPN is a (two-dimensional) parser-definition language; and
  • Opus-2 is a "spoken" language, for some rather exceptional meaning of "speaking".

Most of these specifications are "finished" in the sense that there is nothing obviously more to add to them. (Of course, an implementation, or some really brow-furrowing thought experiments, could always turn up problems with a specification.) The exceptions, which can be considered "works in progress", are:

  • Irishsea, which is largely a set of notes for a livecoding language.
  • Sampo, which is largely a set of notes for a production language.

The specification documents are copyrighted by their respective authors. Not that I mind if you fork this repo and submit pull requests to fix errors or the like, for such is the nature of the distributed version control beast.

Note on the name: in the dialect of English where I come from, "spec" is short for "specification" but "on spec" is short for "on speculation." Thus the name is trying to convey the idea of specifications that were just kind of pulled out of the air.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].