On 12/6/13 6:39 AM, Thomas Steiner wrote:
[+mamund CHEZ yahoo POINT com]Dear Public-LOD, Thanks yet another time for your insightful comments. I will most probably go with the "FRBR-ish" approach then by giving my <video> elements an ID, sans explicitly using FRBR terms… <http://videos.example.org/#video> a ma:MediaResource . <http://videos.example.org/#video> ma:title "Sample Video" . <http://videos.example.org/#video> ma:description "Sample Description" . <http://videos.example.org/#video> ma:locator <http://ex.org/video.mp4> . <http://videos.example.org/#video> ma:locator <http://ex.org/video.ogv> . The whole discussion spawned off an interesting side discussion here and on Twitter [1] on how HTTP content negotiation and client-side "content negotiation" (note the quotes) works with <video>. Mike Amundsen (CC'ed) then built the bridge to Web images, where upon reading up on its history (/me too young) I stumbled upon this quote [2] from 1993: "Actually, the image reading routines we're currently using figure out the image format on the fly, so the filename extension won't even be significant." Interesting… Thanks again all on this thread for helping me out! Cheers, Tom -- [1] https://twitter.com/tomayac/status/408889842849054720 [2] http://1997.webhistory.org/www.lists/www-talk.1993q1/0257.html
Hoping the following illustrations [1][2][3] aid the process of clarifying the different kind of abstraction that name resolution protocols bring to networks (or clouds):
[1] http://bit.ly/1cjYwqN -- Internet Cloud (DNS cnames for computers are what matter re. data access) [2] http://bit.ly/1c9JpwF -- World Wide Web Cloud (HTTP URLs for documents are what matter re. data access) [3] http://bit.ly/INv6ag -- Linked Open Data Cloud (HTTP URIs for entities are what matter re. data access).
Sometimes we talk about #2 in the context of #3 and matters get confusing, unnecessarily :-)
-- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: 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
smime.p7s
Description: S/MIME Cryptographic Signature
