On 7/23/14 12:17 PM, john.walker wrote:
Hi Kingsley,
In the case that Michael describes, could one reasonably expect that if the BBC were to embed the following triples as RDFa in the HTML served on the URL http://www.bbc.co.uk/programmes/b006mw1h, then a webcrawler would understand to go directly to the webpages about the seasons and episodes?

Absolutely!!

They could even use the following within <head/> :

1. <link @rel="{relation-or-predicate-identifier}" href="{relation-object}" ../> -- indicating that the doc in question is the subject of a relation denoted by {relation-or-predicate-identifier}

2. <link @rev="{relation-or-predicate-identifier}" href="{relation-subject}" ../> -- indicating that the doc in question is the object of a relation denoted by {relation-or-predicate-identifier} .

Even up the ante, for smart HTTP user agents by replicating the relations above using "Link:" response headers.

And to make your example live, I am tweaking your Turtle Snippet (aka. Nanotation) which will produce some interesting results. Note, my only change is a Nanotation parser hint i.e., ## Turtle Start ## and ## Turtle End ## :-)

## Turtle Start ##
@prefix schema: <http://schema.org/>.
<http://www.bbc.co.uk/programmes/b006mw1h> a schema:WebPage ;
  schema:about <http://www.bbc.co.uk/programmes/b006mw1h/thing> .
<http://www.bbc.co.uk/programmes/b006mw1h/thing> a schema:TVSeries ;
  schema:name "Gardeners' World" ;
schema:season <http://www.bbc.co.uk/programmes/p00fx55j/thing> , <http://www.bbc.co.uk/programmes/p00fx5b7/thing> ;
  schema:episode <http://www.bbc.co.uk/programmes/b049fnfd/thing> .
<http://www.bbc.co.uk/programmes/p00fx55j> a schema:WebPage ;
  schema:about <http://www.bbc.co.uk/programmes/p00fx55j/thing> .
<http://www.bbc.co.uk/programmes/p00fx5b7> a schema:WebPage ;
  schema:about <http://www.bbc.co.uk/programmes/p00fx5b7/thing> .
<http://www.bbc.co.uk/programmes/b049fnfd> a schema:WebPage ;
  schema:about <http://www.bbc.co.uk/programmes/b049fnfd/thing> .
## Turtle End ##

## start Turtle
@prefix schema: <http://schema.org/>.
<http://www.bbc.co.uk/programmes/b006mw1h> a schema:WebPage ;
  schema:about <http://www.bbc.co.uk/programmes/b006mw1h/thing> .
<http://www.bbc.co.uk/programmes/b006mw1h/thing> a schema:TVSeries ;
  schema:name "Gardeners' World" ;
schema:season <http://www.bbc.co.uk/programmes/p00fx55j/thing> , <http://www.bbc.co.uk/programmes/p00fx5b7/thing> ;
  schema:episode <http://www.bbc.co.uk/programmes/b049fnfd/thing> .
<http://www.bbc.co.uk/programmes/p00fx55j> a schema:WebPage ;
  schema:about <http://www.bbc.co.uk/programmes/p00fx55j/thing> .
<http://www.bbc.co.uk/programmes/p00fx5b7> a schema:WebPage ;
  schema:about <http://www.bbc.co.uk/programmes/p00fx5b7/thing> .
<http://www.bbc.co.uk/programmes/b049fnfd> a schema:WebPage ;
  schema:about <http://www.bbc.co.uk/programmes/b049fnfd/thing> .
## end Turtle
I guess, as Michael mentions, having the webpages as the href targets in the HTML effectively shortcuts that indirect relation.
Cheers,
John

> On July 23, 2014 at 5:23 PM Kingsley Idehen <kide...@openlinksw.com> wrote:
>
>
> On 7/23/14 10:50 AM, john.walker wrote:
> > Hi Michael,
> > Hope the laptop is ok :)
> > So I can think of your 'slash' NIR URI as something similar to a URN:
> > http://www.bbc.co.uk/programmes/b006mw1h/thing
> > It doesn't do much on it's own and *just* acts as an identifier.
> > Using HTTP it can be resolved to a URL via the 303, kind of similar to
> > a URN resolver.
> > Could you explain what you mean by "conneg penalty"?
> > I've set up an application working with 303s and, although I don't
> > consider myself mad, it does add an extra request to every click the
> > user does.
> > Getting the 303 response takes 20 - 25 ms on average, so it's not a
> > big issue in this case (internal company usage).
> > Interestingly enough I just checked a random shortened link off
> > Twitter and it went through no less than 5 HTTP 301/302 redirects (500
> > ms in total) before getting the HTML.
> > Taking that into consideration a single 303 is not too bad!
> > Regards,
> >
> > John Walker
>
> SeeAlso, the output of our variant of Vapour that illustrates entity
> denotation and connotation via HTTP URIs [1] .
>
> Basically, SEO should be targeting the entity denoted by the URI
> <http://dbpedia.org/page/Linked_data> since that URI denotes a Document.
> The document in comprised of RDF content where format is negotiable.
>
> Links:
>
> [1] http://bit.ly/entity-denotation-and-connotaton -- Vapour
> deconstruction of HTTP URIs that denote and connote entities of
> different types .
>
> [2] http://lists.w3.org/Archives/Public/public-lod/2014Jul/0085.html --
> related thread on this forum.
>
> --
> Regards,
>
> Kingsley Idehen
> Founder & CEO
> OpenLink Software
> Company Web: http://www.openlinksw.com
> Personal Weblog 1: http://kidehen.blogspot.com
> Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen
> Twitter Profile: https://twitter.com/kidehen
> Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
> LinkedIn Profile: http://www.linkedin.com/in/kidehen
> Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this
>
>


--
Regards,

Kingsley Idehen 
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog 1: http://kidehen.blogspot.com
Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen
Twitter Profile: https://twitter.com/kidehen
Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen
Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to