[foaf-dev] embedded file-based metadata - for .torrent

Peter Williams pwilliams at rapattoni.com
Fri Dec 24 20:06:16 CET 2010


Using the definitions in the wot ontology, assume that some instance of a metadata document makes statements that are (to humans) references to files (.sig etc) to be pulled using HTTP(s). Since those refs are related to descriptive statements that type the urlrefs, a reasoning engine might know that .sig is a PGP signature blob (without having formally defining the value syntax or internal-coding of such a blob). Presumably, a semweb processor is supposed to fire off a "plugin" that uses non-semweb metadata to fully interpret the blob; and ultimately present the information in a browser-centric manner.

In the case of FOAF-related ontologies (such as the proposed ontology for RSA  keys), is there any experience (a la wot) with pointing to a .torrent file (vs a .sig file), qualifying its urlref as torrent stream (rather than a PGP .sig  blob).... and firing off a file-type-centric plugin in the browser that renders the torrent stream (rather than firing off PGP sig verification of a transfer-syntax/encoding of a RDF stream)?

Ive been playing with outlook, embedded IE browser, email-pushes of openid-signed comments on wordpress blog sites, torrents, and twitter-microblogs about individual torrents (and torrent metadata). Seems an ideal mechanism for mass distribution of self-signed root certs for individuals....where (when combined with DNSsec) the seeding and peering process addresses spoofing threats attaching the authority of the binding to a domain-name.

If nothing else its complements the cached distribution model of the web, leveraging the survivability nature of packet switching (as intended by the early internet designers).


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.foaf-project.org/pipermail/foaf-dev/attachments/20101224/baa2114d/attachment.htm 


More information about the foaf-dev mailing list