TS32Structured data

Does each entity keep the same identifier?

Stable @id values connect the same entities without creating duplicates.

Prepare evidence

In the app: Evidence import
You provide: Graphs and @id identifiers
Allow for: Depends on evidence needed

Prepare evidence

Understand

The same entity. A consistent identity.

Stable @id values connect the same entities without creating duplicates.

TSEP protocol criterion

Identifier stability is a policy to define for your graph. TSEP assesses references within that scope; an identifier does not guarantee a rich result.

The rules and limits of this check are detailed at the bottom of this guide.

Check

The same entities. The same identifiers?

In TSEP Control

You import evidence for this control. The engine assesses it within the declared scope; missing items remain visible.

Your contribution

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

With your own tools

Export structured data from sample pages and compare @id values for the same entities. Check references and vocabulary with the Schema.org validator; document your identifier policy.

Evidence to retain

Archived graph, inventory of present entities and identifiers, assessed references and duplicates.

What this result covers

Schema.org defines a vocabulary; interpretation depends on the consumer.

Act

A stable identity. Repaired links.

Reuse a stable identifier for the same entity and repair inconsistent references.

Recheck

The model evolves. Does the graph stay sound?

After correction, gather new evidence with the same scope and expectations. Retain both dated observations to compare what changed.

Your reference points

To go further.

Statuses, sources and method.

Understand the statusesC · NC · NT · NA

The same legend in guides, analysis and demo. Each status depends on the control’s evidence and rules.

C · Verified: The criterion is met within the assessed scope. Keep dated evidence for the next comparison.
NC · To correct: Reuse a stable identifier for the same entity and repair inconsistent references.
NT · Not established: Evidence or confirmations are insufficient to conclude. Supply what is missing; this status does not establish an SEO error.
NA · Not applicable: The control does not apply to the scope under its rules, with a retained justification. Missing evidence alone does not make it non-applicable.

Sources and references1 reference

Schema.org — Data modelschema.org · new tab

Detailed method and rules3 rules

Control method and criteria

Method
Build the graph and identify unnamed nodes, variable identifiers and duplicates.

Acceptance criteria
The same entities retain identifiers across the corpus; graph references resolve and duplicates are assessed, without requiring all types named in the legacy grid.

Non-applicability
No relevant graph with identifiers.

Detailed rules

TS32-A01 · Qualified prior registry and corpus.

Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.

Scope
Declared corpus of 2–16 JSON-LD exports using identifiers.

Evidence
Prior registry, native exports, local contexts, recomputed graphs and bound reviews; jsonld-identity-corpus-v1 contract.

Method
Check distinct entities, plan and bound prior population/mapping/reference review.

Acceptance criteria
Collision-free registry and three supported judgments; distinct-entity collision fails even with absent review.

When the result remains inconclusive
Missing evidence, review, runtime or context; empty/named graph, notice or unqualified reference/ID. Independent contradictions preserved.

Non-applicability
No NA in this bounded profile.

Assumptions
Declared/reviewed origin, completeness, bases, dates and mappings; not authenticated.

Limitations
Supplied corpus coherence, no temporal stability, real identity, page collection, cross-document merging or Google guarantee.

TS32-A02 · Required identifiers and corpus references.

Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.

Scope
Declared corpus of 2–16 JSON-LD exports using identifiers.

Evidence
Prior registry, native exports, local contexts, recomputed graphs and bound reviews; jsonld-identity-corpus-v1 contract.

Method
Recompute native exports independently and compare defined IRIs with the registry; inventory references and scope.

Acceptance criteria
Required IRIs defined and scope/references qualified; required absence from a complete nonempty graph fails, gaps or ambiguity are inconclusive.

When the result remains inconclusive
Missing evidence, review, runtime or context; empty/named graph, notice or unqualified reference/ID. Independent contradictions preserved.

Non-applicability
No NA in this bounded profile.

Assumptions
Declared/reviewed origin, completeness, bases, dates and mappings; not authenticated.

Limitations
Supplied corpus coherence, no temporal stability, real identity, page collection, cross-document merging or Google guarantee.

TS32-A03 · Evidence-bound mapping and duplicate review.

Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.

Scope
Declared corpus of 2–16 JSON-LD exports using identifiers.

Evidence
Prior registry, native exports, local contexts, recomputed graphs and bound reviews; jsonld-identity-corpus-v1 contract.

Method
Bind each export and recomputed node to mapping, repetition/duplicate and reference-meaning reviews.

Acceptance criteria
Exact coverage and supported judgments; bound contradiction fails, incomplete/unknown review is inconclusive.

When the result remains inconclusive
Missing evidence, review, runtime or context; empty/named graph, notice or unqualified reference/ID. Independent contradictions preserved.

Non-applicability
No NA in this bounded profile.

Assumptions
Declared/reviewed origin, completeness, bases, dates and mappings; not authenticated.

Limitations
Supplied corpus coherence, no temporal stability, real identity, page collection, cross-document merging or Google guarantee.

Rule version 0.2.0-rc.1 · Public protocol reference · Versioned source

Put it into practice

← Back to controls