webr3: wonder when we can start colouring bits of it green
ww: gives a 500 error for HTTP HEAD?
webr3: data.gov data now cors/js accessible, thanks to Li Ding
ww: Dispenses with Collections for easier querying
webr3: Please add weight if you use purl.org and care about js access to ontologies
webr3: Added to buzzword.org.uk, ontologi.es and wiki.ontologi.es. (ty Toby Inkster)
webr3: js+cors support..
webr3: js+cors support..
webr3: now CORS and JS friendly, see: http://productdb.org/gtin/00319980033520.rdf
webr3: FOAF now CORS and JS friendly
webr3: now javascript and CORS friendly
webr3: also http://www.heppnetz.de/grprofile/ and http://www.heppnetz.de/ontologies/vso/ns.owl
webr3: also http://www.heppnetz.de/grprofile/ and http://www.heppnetz.de/ontologies/vso/ns.owl
webr3: now javascript and CORS friendly
webr3: curl -I -X OPTIONS -H "Origin: http://host.com" http://linkedopencommerce.com/sparql
webr3: now javascript and CORS friendly
webr3: curl -I -X OPTIONS -H "Origin: http://host.com" http://linkedopencommerce.com/sparql
webr3: now javascript and CORS friendly
webr3: now javascript and CORS friendly
webr3: curl -I -X OPTIONS -H "Origin: http://host.com" http://lod.openlinksw.com/sparql
webr3: curl -I -X OPTIONS -H "Origin: http://host.com" http://lod.openlinksw.com/sparql
HISTORICAL HYPERMEDIA: AN ALTERNATIVE HISTORY OF THE SEMANTIC WEB AND WEB 2.0 AND IMPLICATIONS FOR E-RESEARCH
danbri: Nice background on some early hypertexty thinkers (like Paul Otlet).
KjetilK: Relevant to the SemanticInbox discussion
tobyink: think kjetilk is referring to http://wiki.qpsmtpd.org/plugins:queue:http-forward
tobyink: This seems hard-coded to always transmit as application/x-www-form-urlencoded. This is more tunnelling traditional SMTP/RFC822 messages over HTTP, whereas I'm just using HTTP's in-built message transmission protocol to send messages that are more than plain old requests for web pages.
KjetilK: The important part is that it would be trivial to forward the request, however you want to do that, so that you can for example use a WebID to authenticate, and then reject the message in the SMTP dialog if the authentication fails
tobyink: think kjetilk is referring to http://wiki.qpsmtpd.org/plugins:queue:http-forward
tobyink: This seems hard-coded to always transmit as application/x-www-form-urlencoded. This is more tunnelling traditional SMTP/RFC822 messages over HTTP, whereas I'm just using HTTP's in-built message transmission protocol to send messages that are more than plain old requests for web pages.
KjetilK: The important part is that it would be trivial to forward the request, however you want to do that, so that you can for example use a WebID to authenticate, and then reject the message in the SMTP dialog if the authentication fails
danbri: " (artistsrelease groups/50) + (artistsreleases/50) + (artistsrecordings/50) + (artistsworks/50) "
danbri: "That results in a whopping 117.6 billion pages of RDFa"
danbri: Scary redundancy! But cool to have all that data
danbri: "That results in a whopping 117.6 billion pages of RDFa"
danbri: Scary redundancy! But cool to have all that data
ww: actually quite useful for sparql endpoint fingerprinting as well...