Recommended HTTP Accept header - ANSWERS
In my experience rapper has a pretty good one: Accept: application/rdf+xml, text/rdf;q=0.6, application/n-triples, text/plain;q=0.1, text/turtle, application/x-turtle, application/turtle, text/n3;q=0.3, text/rdf+n3;q=0.3, application/rdf+n3;q=0.3, application/x-trig, application/rss;q=0.8, application/rss+xml;q=0.8, text/rss;q=0.8, application/xml;q=0.3, text/xml;q=0.3, application/atom+xml;q=0.3,
Sinatra::LinkedData - Linked Data Content Negotiation for Sinatra Applications
This is a Sinatra extension that provides Linked Data content negotiation for Sinatra applications. http://github.com/datagraph/sinatra-linkeddata Features Implements HTTP content negotiation for RDF content types using the Rack::LinkedData middleware. Supports all RDF.rb-compatible serialization formats. Supports both classic and modular Sinatra applications. Examples Adding Linked Data content n
eqentia.com - eqentia リソースおよび情報
This webpage was generated by the domain owner using Sedo Domain Parking. Disclaimer: Sedo maintains no relationship with third party advertisers. Reference to any specific service or trade mark is not controlled by Sedo nor does it constitute or imply its association, endorsement or recommendation.
httpRange-14 change proposal call
Call for proposals to amend the "httpRange-14 resolution" Jonathan A Rees, 29 February 2012 In 2002 the issue of how use of URIs in RDF interacts with use of URIs on the "good old-fashioned hypertext Web" was raised, and debate has been raging ever since. The TAG weighed in with its opinion in 2005 with the so-called "httpRange-14 resolution". Community consensus has not held very well, and ever s
Blog - Crossref
2024 September 24Meet the candidates and vote in our 2024 Board electionsOn behalf of the Nominating Committee, I’m pleased to share the slate of candidates for the 2024 board election. Each year we do an open call for board interest. This year, the Nominating Committee received 53 submissions from members worldwide to fill four open board seats. We maintain a balanced board of 8 large member seat
5 Very Important Things to Note about HTTP based Linked Data
It isn't World Wide Web Specific (HTTP != World Wide Web) It isn't Open Data Specific It isn't about "Free" (Beer or Speech) It isn't about Markup (so don't expect to grok it via "markup first" approach) It's about Hyperdata - the use of HTTP and REST to deliver a powerful platform agnostic mechanism for Data Reference, Access, and Integration. When trying to understand HTTP based Linked Data, esp
The URI, URL, and Linked Data Meme's Generic HTTP URI (Updated)
The URI, URL, and Linked Data Meme's Generic HTTP URI (Updated) Situation Analysis As the "Linked Data" meme has gained momentum you've more than likely been on the receiving end of dialog with Linked Open Data community members (myself included) that goes something like this: "Do you have a URI", "Get yourself a URI", "Give me a de-referencable URI" etc.. And each time, you respond with a URL --
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
http://www.jenitennison.com/blog/node/168/
Change Proposal for HttpRange-14 from Jeni Tennison on 2012-03-22 (public-lod@w3.org from March 2012)
Tumbled Logic - 303 Considered Harmful < The assorted witterings of Mo McRoberts
seevl.net
Quick and dirty linked data content negotiation - bobdc.blog
Good night, Posterous
New opportunities for linked data nose-following
Rack::LinkedData - Linked Data Content Negotiation for Rack Applications
Content Negotiation and HTTP 303 Redirect Code Samples | Linked Data - Connect Distributed Data across the Web
Getting The Linked Data Value Pyramid Layers Right (Update #2)
Getting The Linked Data Value Pyramid Layers Right (Update #2)
5 Very Important Things to Note about HTTP based Linked Data