SORD_VALIDATE(1)

πŸ“¦
version 0.16.22 Β· 5 versions
, in alpine 3.24, arch rolling, epel 10, fedora 43, fedora 44, nixpkgs unstable, ubuntu resolute, ubuntu stonking

πŸ’– SORD_VALIDATE πŸ’–

okay bestie, so this is the manual page for sord_validate, a lil tool from the General Commands Manual section (that's section 1, iykyk) and it's here to be your RDF data's ✨vibe check✨.


🌸 NAME 🌸

sord_validate β€” validate RDF data πŸ¦‹


✨ SYNOPSIS ✨

sord_validate [-hlv] input ...

πŸ’… DESCRIPTION πŸ’…

So sord_validate is a simple validator β€” and when I say simple I mean it does one thing and it does it well, periodt. What it checks is: are all the properties you used actually defined? and is the domain and range of those properties explicitly correct? That's the whole job. That's the assignment.

But here's the thing bestie, and I need you to hear me on this: a validation "error" here doesn't necessarily mean your data is invalid. It literally isn't, okay? Like, for example, you're not required to explicitly list types in RDF. It's not a rule, it's a vibe. So this validator implements a more strict and explicit set of rules, based on the realistic needs of simple real-world implementations. For example, missing explicit type information may be warned about β€” even though even a simple inference engine would be able to deduce it. She's just picky like that πŸ™ˆ.

Also super important: sord_validate never retrieves data from the web or special places on the file system. She stays in her lane. She only processes the files passed directly on the command line. Which means β€” and this is the part people always forget β€” you must pass all used vocabularies to get a useful result. All of them. Every single one. No cap.

And if an appropriate schema is available, literals get checked against datatype definitions β€” both the explicit datatype of the literal itself, and any types implied by the corresponding property. She's thorough πŸ’…. Three XML Schema Datatypes (XSD) constraints are currently supported:

  • regular expressions (xsd:pattern)
  • inclusive ranges (xsd:minimumInclusive and xsd:maximumInclusive)

Given an appropriate schema, that's genuinely enough to validate against most of the standard XSD datatypes. Slay.

The options are as follows:


πŸŽ€ OPTIONS πŸŽ€

  • -h β€” Print the command line options. (the "wait what were the flags again" button 🫢)
  • -l β€” Print errors on a single line. (compact mode, for when you want your problems condensed πŸ’€)
  • -v β€” Display version information and exit. (who even are you, girl? πŸ‘‘)

🌈 EXIT STATUS 🌈

sord_validate exits with a status of 0 if the input data is valid, or non-zero if there are issues with the data or if an error occurred. Zero is the good one. Anything else is giving "we need to talk" energy 😭.


πŸ’œ SEE ALSO πŸ’œ


⭐ STANDARDS ⭐

(standards?? she has them. citations?? she has those too. main character behavior fr fr πŸ“šβœ¨)


πŸ‘‘ AUTHORS πŸ‘‘

sord_validate is a part of sord, by David Robillard ⟨d@drobilla.net⟩. Iconic, honestly. Thank you for your service 🫢


and that's the whole page bestie!! this one shipped with the Debian package, dated January 20, 2025 β€” so if you're reading this from a Debian system, hi, you're exactly where you're supposed to be πŸ’–βœ¨πŸŒΈ go validate something. periodt. πŸ¦‹

πŸ“¦ where this page comes from