Re: Is the same video but in different encodings the owl:sameAs?

Hi Tom,

I am wondering what happens with the Linked Data Principles in the world of HTML video as you described. In [1], one of the basic principles, named "Making URIs Defererenceable", considers the Content Negotiation and states: 

"The Web is intended to be an information space that may be used by 
humans as well as by machines. Both should be able to retrieve
  representations of resources in a form that meets their needs, such as
 HTML for humans and RDF for machines. This can be achieved using an 
HTTP
  mechanism called content negotiation [50]. The basic idea of content negotiation is that HTTP clients send HTTP headers with each request to indicate what kinds of documents 
they prefer. Servers can inspect these headers and select an appropriate response. If the headers indicate that the client prefers HTML, then 
the server will respond by sending an HTML document. If the client 
prefers RDF, then the server will send the client an RDF document." 

Does this mean that we need a completely new mechanism for tackling the old problem in a new technology such as HTML5?

Thanks,
Milorad

[1] http://linkeddatabook.com/editions/1.0/




>________________________________
> From: Thomas Steiner <tomac@google.com>
>To: Milorad Tosic <mbtosic@yahoo.com> 
>Cc: Thomas Steiner <tomac@google.com>; "public-lod@w3.org" <public-lod@w3.org> 
>Sent: Thursday, December 5, 2013 8:31 PM
>Subject: Re: Is the same video but in different encodings the owl:sameAs?
> 
>
>
>Hi Milorad,
>
>
>Unfortunately content negotiation in the HTTP sense is not an option with HTML5 video, as the "content negotiation" in a sense is taken care of by the browser. In my initial mail, check the link on the @currentSrc attribute. If you want to support all browsers on all platforms and device types, you have to specify several sources in different encodings. So you almost always end up with several media resources for the "same" video, hence my original question…
>
>
>Cheers,
>Tom
>
>-- 
>Thomas Steiner, Employee, Google Inc.
>http://blog.tomayac.com, http://twitter.com/tomayac
>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.12 (GNU/Linux)
>
>iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom.hTtP5://xKcd.c0m/1181/
>-----END PGP SIGNATURE-----
>
>
>