Relationship between FB Open Graph object identity, object url and app domain?

I'm looking for clarification on how Facebook uniquely identifies objects in the object graph. Specifically, we have several hundred sites for which there is significant overlap in pages that display hotel information. We'd like to have 'Like' buttons for hotels, but have the counts aggregate across sites - so that it doesn't matter on which site a person 'likes' a specific hotel, it'll contribute to the same global count.

More importantly, the philosophy behind Open Graph is that is represents associations between real-world objects - which just happen to be represented by a web-page, so it makes sense for page about a particular hotel to reference the same hotel page object in the graph, regardless of which site it was 'liked' from. For example, for books and products the Open Graph Protocol (OGP) uses ISBN and UPC numbers, while no such universal code exists for other types.

Spec开发者_Python百科ifically,

1. If I set the Open Graph Protocol (OSP) og:url meta property of a hotel page to a URL that references a central site - so that it will be the same og:url for all pages about that hotel regardless of which of our many sites the information appears on, will that achieve the uniqueness required? (does FB even interpret that or is it considered opaque?)
2. When I use the FB Debugger/Lint app to check my page, it complains that the App ID referenced in the fb:app_id meta tag isn't allowed on any domain other that the 'base' domain set in the App's settings on Facebook. Assuming that this implies I need to create a separate app for every domain we use(!), is there any implication of that for the hotel object identity? (or will the hotel identity remain independent and 'Like'ing a hotel via a Graph API call with any App ID will result in the correct association with the single hotel object as identified in its og:url?). Do I even need an App ID on the page? (just admins perhaps?)
3. If Facebook returns any of the hotels when people search on the Facebook site, which URL/link will it offer for the result? (the og:url?)
4. Lastly, and slightly OT, I'm wondering what happens if the og: metadata for a particular canonical og:url object has different properties on different sites, what Facebook will make of it (- e.g. if the og:site_name was different on each domain where the same hotel was represented by the same og:url)

I'm still trying to get my head around it all, so I appreciate all those Facebook ninjas out there :) Apologies if I've put too much detail.

Cheers.

To partially answer 1, Facebook says "If a user likes your URL using a Like button, a News Feed story [...] will be published to Facebook. The og:title links to og:url and the og:site_name is rendered pointing to your site's domain automatically."

Sad. While the og:url is intended to uniquely identify a real-world object, Facebook apparently thinks all users would like to have a link to only a single web-page about the object, regardless of the existence of many and from which page about the object they hit 'Like'. So, even if a user 'Likes' a hotel from a page like coolhotelinfo.con/abchotel or discounthotels.con/abchotel they'll get a link on their feed to boringhotelreferencedata.con/abchotel (for example).