I have a single page describing an organisation marked up with schema.org data, there are then multiple related pages with review data on. At the moment these review pages have the same Organisation tag as the main page but this doesn't feel right to me, it seems like there should be one Organisation record for each company.
Does anyone have an experience or guidance on this matter or the best way of marking up review data on related pages?
-- I have thought about using the organisation url parameter on the review pages which points back to the main page but I am concerned this would eventually impact the listing of these review pages.
Updated with examples
This is an example of the main organisation page http://www.insidebuzz.co.uk/law/hogan-lovells
And this is one of the sub pages http://www.insidebuzz.co.uk/reviews/hogan-lovells/question/overall-satisfaction
[update 5/17/2013]
I've now found that the way we can link items from one to another is with itemid="
. This link is to the WebSchemas/ExternalEnumerations page "Country" example. This example shows how this is done. Pay keen attention to the "itemid" usage.
NOT THE ANSWER:
Per HTML - Living Standard -- We can use the HTML5 Microdata "itemref" to accomplish your goal.
[example removed for brevity]
I've done this in MVC by placing the itemscope itemtype="...
in the MVC equivalent of a Master Page and in the View's (child pages) used itemprop
and itemref
etc.
NOT THE ANSWER:
http://schema.org/CollectionPage
isPartOf = Indicates the collection or gallery to which the item belongs.
Hope this helps.