To the extent possible under law, the editors have waived all copyright
and related or neighboring rights to this work.
In addition, as of 9 September 2025,
the editors have made this specification available under the
Open Web Foundation Agreement Version 1.0,
which is available at https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owfa-1-0.
Parts of this work may be from another specification document. If so, those parts are instead covered by the license of that specification document.
Abstract
Establishes standardized programming patterns and best practices for developing robust and maintainable ASIMOV software components.
1. Introduction
The [ASIMOV] Platform is a polyglot development platform for trustworthy,
neurosymbolic AI.
This specification establishes standardized programming patterns and best
practices for developing robust and maintainable ASIMOV software components.
URI resolver. Takes a URI (that is, URN or URL) input, produces a resolved URL
output.
Data flow for resolvers
3.10.1. Arguments
Argument
Arity
Default
Summary
INPUT-URL
0..1
none
The input URL.
3.10.2. Options
Option
Flag
Default
Summary
--limit=COUNT
-n
none
The maximum number of outputs.
3.11. Runner
Language runtime engine. Consumes text input conforming to a grammar, executes
it, and produces the execution result as output.
Data flow for runners
3.11.1. Arguments
Argument
Arity
Default
Summary
INPUT-FILE
0..1
- (/dev/stdin)
The input file path.
3.11.2. Options
Option
Flag
Default
Summary
--define=VAR=VAL
-D
none
A key/value definition.
3.12. Writer
RDF dataset exporter. Consumes RDF input, produces some output.
Data flow for writers
3.12.1. Arguments
Argument
Arity
Default
Summary
INPUT-FILE
0..1
- (/dev/stdin)
The input file path.
OUTPUT-FILE
0..1
- (/dev/stdout)
The output file path.
3.12.2. Options
Option
Flag
Default
Summary
--input=FORMAT
-i
jsonl
The input format.
--output=FORMAT
-o
auto
The output format.
4. RDF Mapping
5. Security Considerations
6. IANA Considerations
This specification does not require any IANA registrations.
7. Acknowledgments
The editors would like to thank the ASIMOV Platform community for their contributions and feedback during the development of this specification.
8. Changes
This section will document changes between versions of this specification.
Conformance
Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology.
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”
in the normative parts of this document
are to be interpreted as described in RFC 2119.
However, for readability,
these words do not appear in all uppercase letters in this specification.
All of the text of this specification is normative
except sections explicitly marked as non-normative, examples, and notes. [RFC2119]
Examples in this specification are introduced with the words “for example”
or are set apart from the normative text with class="example", like this:
This is an example of an informative example.
Informative notes begin with the word “Note”
and are set apart from the normative text with class="note", like this:
