Write identity decisions before comparing strings
List described objects and why they are the same or different. A real organization can remain the same publisher across languages while each page version needs its own context. Language difference does not automatically create another company.
A fictional example has organization, page and service nodes. Two distinct services should not accidentally receive the same @id from a shared template. Repeating the same publisher identity is not automatically a collision, either.
Collect identifiers and relationships using them
Read relevant scripts from the rendered sample. Collect @id, described type and referring relationships. A reference can target an object described elsewhere; do not blindly require every object to be defined in the same script block.
Inspect relative identifiers against the document base and actual URL model. The same text can resolve differently when the base changes. A canonical address and object identifier have different roles and need a documented relationship where used.
Test collisions and legitimate reuse together
Introduce a deliberate collision in safe test data and check it is detectable. Then try legitimate reuse of the same organization. A test banning every repeated string would reject valid relationships.
Also compare facts different components give the same object. Two names can be valid language variants, but a page and business must not silently merge because a template copied the wrong identifier. Interpret the finding against identity decisions rather than occurrence counts alone.
| Case | Risk | Expected decision |
|---|---|---|
| Same publisher in two languages | Unnecessary identity splitting | Approved organization identity reused |
| Two distinct services | Template assigns one identifier | Different objects have intended identities |
| Separate script blocks | Conflicting descriptions of one object | Shared identity has compatible facts |
| Relative reference | Changed base points elsewhere | Resolved identifier follows the model |
| Moved page | Old relationship remains | Affected relation follows migration decision |
Keep reference tests for future template changes
Document object, identity source, components and why reuse is legitimate or wrong. Repeat cases after base, language model, generator or URL changes. Use fictional fixtures without private facts.
State verified relationships and external descriptions outside the sample. A consistent identifier register demonstrates a traceable model; it does not prove how a search engine built its knowledge graph or whether the page will be cited.