RUDOF(SHEX-VALIDATE)

πŸ“¦
version 0.3.8 Β· 4 versions
, in ubuntu stonking

πŸ’– RUDOF(SHEX-VALIDATE) πŸ’–

okay bestie, so this is the rudof shex-validate page β€” it lives in section SHEX-VALIDATE of the manual, and yes it's giving very "version 0.3.8+ds" energy. Basically: you got RDF, you got ShEx schemas, and this lil icon makes them validate each other. Let's go πŸ¦‹


✨ NAME ✨

rudof shex-validate β€” validate RDF using ShEx schemas πŸŽ€


🌸 SYNOPSIS 🌸

rudof shex-validate [OPTIONS] [DATA]...

πŸ’… DESCRIPTION πŸ’…

Validate RDF using ShEx schemas. That's the whole vibe. You bring the data, you bring the schema, it tells you if the vibes check out. πŸ”₯

🫢 Arguments 🫢

  • [DATA]... β€” the data you wanna validate, fr fr. (Yeah, that's literally all it says here, and I'm not about to make up extra lore. 😭)

πŸ‘‘ OPTIONS πŸ‘‘

  • -s, --schema <INPUT> β€” the schema file name, a URI, or a straight-up - meaning "read it from stdin". πŸ’–
  • --compiled-schema <FILE> β€” a precompiled ShEx SchemaIR cache file. Already done the homework, just handing it in. ✨
  • --compile-to <FILE> β€” compile that ShEx schema and write the precompiled SchemaIR cache out to FILE. Save it for later, bestie. πŸŽ€
  • -f, --schema-format <FORMAT> β€” what format is the ShEx schema in?
    • default: shexc
    • possible values: internal, simple, shexc, shexj, json, jsonld, turtle, ntriples, rdfxml, trig, n3, nquads
  • -m, --shapemap <INPUT> β€” a ShapeMap. yes queen, bring the map. πŸ—ΊοΈ
  • --shapemap-format <FORMAT> β€” what format is the ShapeMap in?
    • possible values: compact, internal, json, details, csv
  • -n, --node <NODE> β€” the node to validate. point at it, validate it. πŸ’…
  • --sort_by <SORT_MODE> β€” sort the result by this (default = node).
    • default: node
    • possible values: node, shape, status, details
  • -l, --shape-label <LABEL> β€” the shape label (default = START). ⭐
  • -t, --data-format <FORMAT> β€” the RDF data format.
    • default: turtle
    • possible values: turtle, ntriples, rdfxml, trig, n3, nquads, jsonld, pg
  • --base-schema <IRI> β€” base schema, used to resolve relative IRIs in the schema. 🌈
  • --base-data <IRI> β€” base RDF data IRI, used to resolve relative IRIs in the RDF data. πŸ¦‹
  • --reader-mode <MODE> β€” RDF reader mode.
    • default: strict
    • possible values: lax, strict
  • -r, --result-format <FORMAT> β€” output result format (yes, the original spells it "Ouput", and I am faithfully reporting that typo, no cap 😭).
    • default: details
    • possible values: details, turtle, ntriples, rdfxml, trig, n3, nquads, compact, json, csv
  • --map-state <FILE> β€” MapState file name. 🧚
  • --strict-iris β€” require <> brackets around IRIs, aka strict mode. By default, bare http://??? IRIs are accepted β€” that's lax mode. so if you want the strictness, this is your girl. πŸ’œ
  • --external-resolver <SPEC> β€” external-shape resolver spec. Repeatable, so stack 'em. Syntax: <kind>[:<arg>]. Built-in kinds: reject-all, schema:<path>. Wanna know what's available? Use --list-external-resolvers. πŸ”
  • --list-external-resolvers β€” print the available external-shape resolver kinds and exit. short king behavior. πŸ‘‘
  • -c, --config-file <FILE> β€” config file name. πŸ“
  • -o, --output-file <FILE> β€” output file name, default = terminal. πŸ’–
  • --force-overwrite β€” force overwrite the output file if it already exists. no hesitation, no fear. πŸ”₯
  • --backend <BACKEND> β€” choose which RDF data backend to load the input into.
    • memory (default): parse into an in-process oxrdf::Graph.
    • qlever: launch a local QLever Docker container and index the input on disk. Requires the binary to be built with the qlever feature.
    • endpoint=<URL_OR_NAME>: query an external SPARQL endpoint by URL or by the name of an endpoint registered in the TOML config. See also the --endpoint / -e shortcut.
  • -e, --endpoint <URL_OR_NAME> β€” shortcut for --backend endpoint=<URL_OR_NAME>.
    • accepts either a full SPARQL endpoint URL or the name of an endpoint registered in the TOML config.
    • mutually exclusive with --backend. pick a lane, bestie. πŸ™ˆ
  • -h, --help β€” print help (see a summary with -h). 🫢
⚠️ heads up: --endpoint / -e and --backend are mutually exclusive β€” you cannot run both at once, that's not the move.

okay that's the whole page, mwah. πŸ’‹ this was rudof shex-validate, version 0.3.8+ds, dated August 2026 β€” go validate something and slay, periodt. βœ¨πŸ’œπŸ¦‹

πŸ“¦ where this page comes from