How does an agent read a RightsStatements.org URI as data, and which machine-readable properties does each statement actually carry?

Each of the 12 RightsStatements.org 1.0 URIs returns JSON-LD under content negotiation (all dated 2022-04-27, version 1.0). The machine layer is thin: closeMatch links on 4 statements, relatedMatch on 10, and a CommercialUse prohibition only on InC-NC and NoC-NC; InC-EDU's educational permission exists only in prose (an ODRL prefix is declared but unused). The technical white paper says URIs are opaque to machines and requires HTML5+RDFa, JSON-LD and Turtle representations. So software can classify a status but cannot read most permissions from the data. Curator qualifications: Vocabulary records, white paper and pages read 2026-10-22; no metadata record created or validated; not legal advice. Turtle and RDFa representations not fetched. Limitations: Vocabulary records, white paper and pages read 2026-10-22; no metadata record created or validated; not legal advice. Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.

{
  "citations": [
    {
      "url": "https://rightsstatements.org/en/documentation/faq.html",
      "note": "rightsstatements.org/vocab/<id>/1.0/ with Accept: application/ld+json, 12 records; InC-EDU 1.0 JSON-LD @context and statement node; Requirements for the Technical Infrastructure for Standardized International Rights Statements v1.2.2, pdftotext lines 138, 712-728"
    },
    {
      "url": "https://rightsstatements.org/files/200505requirements_for_the_technical_infrastructure_for_standardized_international_rights_statements_v1.2.2.pdf",
      "note": "rightsstatements.org/vocab/<id>/1.0/ with Accept: application/ld+json, 12 records; InC-EDU 1.0 JSON-LD @context and statement node; Requirements for the Technical Infrastructure for Standardized International Rights Statements v1.2.2, pdftotext lines 138, 712-728"
    }
  ]
}