Tree-Sitter grammar for SDML
A tree-sitter grammar for the Simple Domain Modeling Language (SDML). For more information on the language, see the documentation.
Example
module campaign <https://advertising.amazon.com/api-model> is
import [dc rdfs skos]
@skos:prefLabel = "Campaign sub-domain"@en
@skos:version = xsd:decimal(2)
datatype Name <- string {
minLength = 5
maxLength = 25
}
datatype Identifier <- opaque string {
length = 20
} is
@dc:description = "An opaque, general, entity identifier."@en
end
property CampaignId -> Identifier is
@skos:prefLabel = [
"Campaign Identifier"@en
"Identified de campagne"@fr
]
@dc:description = "The globally unique identifier for a Campaign entity"@en
end
structure Tag is
key -> token
value -> {0..} rdfs:langString
end
entity Campaign is
identity ref CampaignId
name -> Name is
@skos:definition = "the name of the campaign"@en
end
tag -> {unordered unique 0..} Tag
target -> {1..} Target
end
entity Target
end
Bindings
The following bindings are built and released along with any version upgrade of the source version. The tree-sitter tool also generates bindings for C, Go, and Swift that are not built and released to any repository.
Node bindings are published to npmjs and can be installed using the npm command directly, or by making it a project dependency.
〉npm install -g tree_sitter_sdml
Python bindings are published to PyPI and can be installed using any
standard tool, such as pip.
〉pip3 install tree_sitter_sdml
Rust bindings are published to crates.io and can be installed via cargo in the usual manner.
〉cargo install tree_sitter_sdml
License
This package is released under the Apache License, Version 2.0. See LICENSE file for details.
Changes
See CHANGES.md.
Additional Links
Metadata
Release files for tree-sitter-sdml 0.4.14
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tree_sitter_sdml-0.4.14.tar.gz | 93.7 kB | Without provenance | Details for tree_sitter_sdml-0.4.14.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tree_sitter_sdml-0.4.14-cp38-abi3-macosx_11_0_arm64.whl | CPython 3.8 | abi3 | macOS 11.0+ ARM64 | Details for tree_sitter_sdml-0.4.14-cp38-abi3-macosx_11_0_arm64.whl |
Total release size: 163.8 kB
Release files / tree_sitter_sdml-0.4.14.tar.gz
| Download URL | tree_sitter_sdml-0.4.14.tar.gz |
|---|---|
| Size | 93.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e973f1514811ca02b8d979540131d1930a2548b8b97df59daa05d012fcf4201a
|
|
BLAKE2b-256 checksum How to use checksums |
1ce8074eefca79aa79b4a4f71251346cd4372aab5254f8b44c81f79d29fe02c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / tree_sitter_sdml-0.4.14-cp38-abi3-macosx_11_0_arm64.whl
| Download URL | tree_sitter_sdml-0.4.14-cp38-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 70.1 kB |
| Tags | CPython 3.8 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
f2fcf5c6edecfceab8a59ce0998e4eb84a99196ac0594f04b2c4c55401dd8f92
|
|
BLAKE2b-256 checksum How to use checksums |
26d87285fe9b4a4a07a082f433f745e16a31c16327dfda43defb1d2fd3dd1a87
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Security for tree-sitter-sdml 0.4.14
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.