Differentiating a concept and the website about it in RDFa

Hi,

I have a question on how to use RDFa to add linked data about a resource
to its HTML representation. Given the following assumptions:

 * The URI <https://example.com/> referes to an information resource
 * The information resource describes the Example concept
 * Using a web browser asking for text/html, we get an information
   resource describing Example formatted as HTML content
 * The text and formatting and such inside the HTML is a website *about*
   the Example thing
 * A website is an entity that we can make statements about
 * An IRI must never refer to two different concepts

We now add linked data statements about Example to the HTML using RDFa,
e.g.:

  <span property="schema:address">Foo Road 31, Bartown 12345</span>

Thus, we now know that:

  <https://example.com/> <http://schema.org/address> "Foo Road 31, Bartown 12345" .

Clearly, we uphold the assumption that <https://example.com/> refers to
a thing, and this thing has a postal address, and that the information
dereferencable from the IRI is about the Example thing. Good!

Now, we look at OpenGraph, and add:

  <meta property="og:type" content="og:website" />

Hence:

  <https://example.com/> <http://ogp.me/type> <http://ogp.me/website> .

Even worse and more obvious:

  <https://example.com> <http://purl.org/dc/terms/license> <https://creativecommons.org/licenses/by/4.0/> .

Now we are talking about two different concepts: The Example thing
(probably a schema:Organization), and a website describing this thing,
but we did so under the same IRI reference! Not good.

This means one of two things:

 a) At least one of my assumptions is wrong
 b) We need a way to differentiate between the two things "Example" and
    "a website describing Example"

What are the approaches to do this?

Some ideas:

 a) Let <https://example.com/> be the IRI of the **website about
    Example** and mint a new IRI for Example itself, e.g.
    <https://example.com/#me>
 b) Use the real file name of the document, e.g.
    <https://example.com/index.html> as the IRI for the website concept
 c) Use <https://example.com/> as the IRI of Example, and
    <https://www.example.com/> as the IRI of the website concept, having
    one redirect to the other when dereferencing

I think a) is not nice, and b) and c) seem buggy because I think
OpenGraph assumes that the RDFa statements have the current page URI as
their subject.


Any hints and discussion are appreciated.

Thanks,
Nik