Microdata’s name-value pairs are per webpage, not per website.
So on a website about a music group, it can be expected that each page contains an "own" MusicGroup
item, which is, however, actually always about the same music group. But from the Microdata or schema.org perspective, these different items would not be semantically connected that way (consumers might guess this however, e.g. by comparing property values).
Microdata’s itemid
attribute could be used to uniquely identify each item. But it is required that the used vocabulary supports "global identifiers for items" (itemid
is used for some types on schema.org (e.g., in the example for MedicalScholarlyArticle
), but it’s not clear to me if it’s really supported as required by Microdata for other types, like MusicGroup
).
So in your case, you could:
- leave it as it is
- duplicate the information, so that each item has all relevant content (possibly using
meta
/link
elements) - move all information on one page (possibly using
itemref
) - (if it should be allowed for general use with schema.org) use
itemid
to state that several items are actually about the same thing