How to use JSON-LD Reference Graph Auditor
- Enter the documents or graph arrays you want compared.
- Supply the supported local context and base for relative identities.
- Review unresolved edges, shared declarations and cycles before downloading the graph.
Example: JSON-LD Reference Graph Auditor
Inspect identities and reference edges across supplied JSON-LD documents using a bounded local context subset.
You add
JSON-LD documents: "[\n {\n \"@graph\": [\n {\n \"@id\": \"https://example.org/organisation\",\n \"@type\": \"Organization\",\n \"name\": \"Example Org\",\n \"member\": [\n {\n \"@id\": \"https://example.org/alex\"\n },\n {\n \"@id\": \"https://example.org/sam\"\n }\n ]\n },\n {\n \"@id\": \"https://example.org/alex\",\n \"@type\": \"Person\",\n \"name\": \"Alex\",\n \"teaches\": {\n \"@id\": \"https://example.org/course-1\"\n },\n \"knows\": {\n \"@id\": \"https://example.org/sam\"\n }\n },\n {\n \"@id\": \"https://example.org/sam\",\n \"@type\": \"Person\",\n \"name\": \"Sam\",\n \"knows\": {\n \"@id\": \"https://example.org/alex\"\n }\n }\n ]\n },\n {\n \"@graph\": [\n {\n \"@id\": \"https://example.org/alex\",\n \"@type\": \"Person\",\n \"author\": \"https://example.org/missing-person\"\n },\n {\n \"@id\": \"https://example.org/article-1\",\n \"@type\": \"Article\",\n \"author\": {\n \"@id\": \"https://example.org/alex\"\n },\n \"citation\": \"https://example.org/unknown-paper\"\n }\n ]\n }\n]"
Local context subset: "{\n \"@vocab\": \"https://schema.org/\",\n \"knows\": {\n \"@type\": \"@id\"\n },\n \"author\": {\n \"@type\": \"@id\"\n },\n \"member\": {\n \"@type\": \"@id\"\n }\n}"
Base URL for relative values: "https://example.org/"
You get
Read 5 nodes and 7 references; 2 unresolved, 1 shared identity and 1 cycle.
Options
- Local context
- Only the supported term/vocabulary and reference declarations are expanded. Remote contexts are never retrieved.
- Node identity
- Explicit identities can connect declarations across documents. A reference without a declaration remains unresolved within the supplied evidence.
Supported inputs and limits
Up to 12 documents, 500 nodes and 200,000 document characters. Declared local expansion subset only; no remote context resolution, RDF reasoning or rich-result promise. Blank-node labels are scoped to each supplied document; nesting is capped at 30 levels.
Where your input is processed
This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.
A relationship cycle can be valid
Two people can reference one another without making the JSON-LD invalid. Review repeated declarations and conflicting supplied types as separate findings. The bounded graph does not perform RDF reasoning, certify full JSON-LD expansion or establish search rich-result eligibility.
Questions about JSON-LD Reference Graph Auditor
Is every cycle an error?
No. Cycles are shown as relationships and can be valid.
Are external contexts loaded?
No. Use the supported local context subset for this inspection.
Does an unresolved edge prove invalid data?
The referenced declaration may exist outside the documents you supplied.