Question about structuring @id schema tags

[RosemaryB]

We are using JSON-LD to apply schema.  My colleague had question about applying @id tags in the schema parent lists:

While implementing schema, we've included @id as a parameter to both the "list" child of "ListItem" of a "BreadcrumbList" - on the same schema, we've added an @id parameter to mainContentOfPage and both @id parameters are set to the pages URL. Having this @id in both places is giving schema checker results that have the child elements of "mainContentOfPage" appearing under the "list" item.

Questions: is this good or bad? Where should @id be used? What should @id be set to?

Thanks for the insight!

[MattRoney]

Hi Rosemary! Did Everett's response help, or could you provide a link?

Thanks!

[Everett]

Can you share a link to a page with the code? You should use @id to indicate the URL of the entity being defined by the Schema. I think it's OK to have multiple @id's per page, but I think you should only have one per "node" since each node is identifying and defining one entity.

If the problem has to do with the same @id being used several times on the page, you may want to look into @base, which I think would allow you to specify the @id of the entity once for the entire page: http://www.w3.org/TR/json-ld/#advanced-concepts

Note: I'm not a developer. I have implemented Schema on several sites using JSON-LD, but only have a basic working knowledge. If you share the code perhaps it will be easier to assist you.