W3C home > Mailing lists > Public > public-awwsw@w3.org > February 2011

Problem definition

From: Nathan <nathan@webr3.org>
Date: Thu, 17 Feb 2011 19:32:31 +0000
Message-ID: <4D5D77CF.8010409@webr3.org>
To: AWWSW TF <public-awwsw@w3.org>, Jonathan Rees <jar@creativecommons.org>
resend (sent from wrong address previously)

Hi,

Tried to write up the problem, as I see it (keeping away from solutions
at the minute).

Agree with the following summary(?):

Competing uses of dereferenceable absolute http scheme URIs:

1: network accessible resource
    - uri as an address for some process on the web
2: representation
    - uri as referring to a specific content+content-meta
      (fixed resource/simple IR)
3: document / "source of information"
    - not well defined, typically "web of documents"
4: primary topic of a document / "source of information"
    - when a document is primarily about one thing
5: any thing
    - any single thing, whatever a name is commonly used to refer to


Ideal Layers of the Web:

                            _ network accessible resources
   Network / Computers ----|_
          |                   representations
     [hidden by]
          |                 _ sources of information
    Web of Documents ------|_
          |                   documents
     [hidden by]
          |                 _ primary topic of a document
     Web Of Data ----------|_
                              any thing


Proof of each URI use:

1: network accessible resource
    <link rel="pingback" href="/pinger" />
    (treats @href like an address)

2: representation
    in a document you GET from <u>
    <link rel="stylesheet" href="/styles.css" />
    creates triple <u> xhv:stylesheet "<u>/styles.css" in RDFa
    (uses <u> to identify representation)

3: document / "source of information"
    <a href="/foo.html">foo</a>

4: primary topic
    <meta property="og:title" content="blog post title" />

5: any thing
    have you met <a href="<u>">my mum</a> ?
    <http://xmlns.com/foaf/0.1/name>


chimera theory:

   "URI refers to a 'chimera' entity that has some of the properties of
    the page and some of the properties of either its primary topic or
    the entity named on the page by the URI."

is chimera theory current reality? yes
   many pages, like a doc with open graph, uses the same URI to refer to:
    - network accessible document
    - representation
    - document
    - primary topic
    - any thing (usually also the primary topic "blog post" or "my mum")

problem:
web of data / sem web requires one name to be used to refer to one thing.

httpRange-14:
there exists a class of information resources, and dereferencable http
scheme URIs are used to refer to these

httpRange-14 problem, the rel cc:license problem:
"information resource" is loosely defined, such that when a GET pulls
back HTML which contains a "blog post", things from all three layers are
classed as an information resource
   - representation
   - the document
   - primary topic, the blog post.
does dc:created refer to representation, to the document, or the blog
post? does cc:license apply to the representation, the document or the
blog post?

does httpRange-14 resolution remove chimera state of the web?
   no.

potential next steps:
  - remove chimera state from web of data
     (possible B.C. breaks)
  - live with chimera state and focus on disambiguation
     (requires interpretation of statements, only graphs can be
interpreted to the level required to disambiguate chimera state)

Best,

Nathan
Received on Thursday, 17 February 2011 19:33:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 17 February 2011 19:33:39 GMT