Ruben Verborgh’s data

Matches in Ruben’s data for { ?s ?p ?o }

• fine-grained-content-negotiation refersTo rfc7231.
• fine-grained-content-negotiation refersTo rfc7089.
• fine-grained-content-negotiation refersTo rfc6906.
• fine-grained-content-negotiation refersTo rfc5988.
• fine-grained-content-negotiation refersTo json-ld.
• fine-grained-content-negotiation refersTo top.htm.
• fine-grained-content-negotiation refersTo rest-apis-must-be-hypertext-driven.
• fine-grained-content-negotiation refersTo json-ld-framing.
• fine-grained-content-negotiation refersTo MIC.2018.032501515.
• fine-grained-content-negotiation refersTo JD-07-2013-0098.
• fine-grained-content-negotiation refersTo the-lie-of-the-api.
• fine-grained-content-negotiation citation activitystreams-core.
• fine-grained-content-negotiation citation rfc7231.
• fine-grained-content-negotiation citation rfc7089.
• fine-grained-content-negotiation citation rfc6906.
• fine-grained-content-negotiation citation rfc5988.
• fine-grained-content-negotiation citation json-ld.
• fine-grained-content-negotiation citation top.htm.
• fine-grained-content-negotiation citation rest-apis-must-be-hypertext-driven.
• fine-grained-content-negotiation citation json-ld-framing.
• fine-grained-content-negotiation citation MIC.2018.032501515.
• fine-grained-content-negotiation citation JD-07-2013-0098.
• fine-grained-content-negotiation citation the-lie-of-the-api.
• fine-grained-content-negotiation datePublished "2016-11-30T09:00:00+01:00".
• fine-grained-content-negotiation datePublished "2016".
• fine-grained-content-negotiation description "Information resources can be expressed in different representations along many dimensions such as format, language, and time. Through content negotiation, HTTP clients and servers can agree on which representation is most appropriate for a given piece of data. For instance, interactive clients typically indicate they prefer HTML, whereas automated clients would ask for JSON or RDF. However, labels such as “JSON” and “RDF” are insufficient to negotiate between the rich variety of possibilities offered by today’s languages and data models. This position paper argues that, despite widespread misuse, content negotiation remains the way forward. However, we need to extend it with more granular options in order to serve different current and future Web clients sustainably.".
• fine-grained-content-negotiation subject RDF.
• fine-grained-content-negotiation subject JSON.
• fine-grained-content-negotiation subject World_Wide_Web.
• fine-grained-content-negotiation subject Content_negotiation.
• fine-grained-content-negotiation authorList b0_b2753.
• fine-grained-content-negotiation agreesWith MIC.2018.032501515.
• fine-grained-content-negotiation agreesWith JD-07-2013-0098.
• fine-grained-content-negotiation agreesWith the-lie-of-the-api.
• fine-grained-content-negotiation citesAsEvidence activitystreams-core.
• fine-grained-content-negotiation citesAsEvidence rfc6906.
• fine-grained-content-negotiation citesAsEvidence json-ld.
• fine-grained-content-negotiation citesAsEvidence rest-apis-must-be-hypertext-driven.
• fine-grained-content-negotiation citesAsEvidence MIC.2018.032501515.
• fine-grained-content-negotiation citesAsPotentialSolution rfc7089.
• fine-grained-content-negotiation citesAsPotentialSolution rfc6906.
• fine-grained-content-negotiation citesAsPotentialSolution rfc5988.
• fine-grained-content-negotiation isCitedAsAuthorityBy web-api-ecosystem.
• fine-grained-content-negotiation isCitedBy web-api-ecosystem.
• fine-grained-content-negotiation related_to participate.
• fine-grained-content-negotiation related_to calls.
• fine-grained-content-negotiation reply_of participate.
• fine-grained-content-negotiation reply_of calls.
• fine-grained-content-negotiation topic RDF.
• fine-grained-content-negotiation topic JSON.
• fine-grained-content-negotiation topic World_Wide_Web.
• fine-grained-content-negotiation topic Content_negotiation.
• fine-grained-content-negotiation abstract "Information resources can be expressed in different representations along many dimensions such as format, language, and time. Through content negotiation, HTTP clients and servers can agree on which representation is most appropriate for a given piece of data. For instance, interactive clients typically indicate they prefer HTML, whereas automated clients would ask for JSON or RDF. However, labels such as “JSON” and “RDF” are insufficient to negotiate between the rich variety of possibilities offered by today’s languages and data models. This position paper argues that, despite widespread misuse, content negotiation remains the way forward. However, we need to extend it with more granular options in order to serve different current and future Web clients sustainably.".
• fine-grained-content-negotiation abstract "Information resources can be expressed in different representations along many dimensions such as format, language, and time. Through content negotiation, HTTP clients and servers can agree on which representation is most appropriate for a given piece of data. For instance, interactive clients typically indicate they prefer HTML, whereas automated clients would ask for JSON or RDF. However, labels such as “JSON” and “RDF” are insufficient to negotiate between the rich variety of possibilities offered by today’s languages and data models. This position paper argues that, despite widespread misuse, content negotiation remains the way forward. However, we need to extend it with more granular options in order to serve different current and future Web clients sustainably.".
• fine-grained-content-negotiation alternativeHeadline "A case for more fine-grained content negotiation".
• fine-grained-content-negotiation description "Information resources can be expressed in different representations along many dimensions such as format, language, and time. Through content negotiation, HTTP clients and servers can agree on which representation is most appropriate for a given piece of data. For instance, interactive clients typically indicate they prefer HTML, whereas automated clients would ask for JSON or RDF. However, labels such as “JSON” and “RDF” are insufficient to negotiate between the rich variety of possibilities offered by today’s languages and data models. This position paper argues that, despite widespread misuse, content negotiation remains the way forward. However, we need to extend it with more granular options in order to serve different current and future Web clients sustainably.".
• fine-grained-content-negotiation mainEntityOfPage verborgh_sdsvoc_2016.
• fine-grained-content-negotiation sameAs fine-grained-content-negotiation.
• fine-grained-content-negotiation isPrimaryTopicOf verborgh_sdsvoc_2016.
• fine-grained-content-negotiation page verborgh_sdsvoc_2016.
• incentivized-collaboration author me.
• incentivized-collaboration publisher me.
• incentivized-collaboration creator me.
• incentivized-collaboration about personal_data.
• incentivized-collaboration about data_integration.
• incentivized-collaboration about Semantic_Web.
• incentivized-collaboration about Facebook.
• incentivized-collaboration about Distributed_ledger.
• incentivized-collaboration about World_Wide_Web.
• incentivized-collaboration author me.
• incentivized-collaboration publisher me.
• incentivized-collaboration coparticipatesWith me.
• incentivized-collaboration type PublicationVolume.
• incentivized-collaboration type Item.
• incentivized-collaboration type ScholarlyArticle.
• incentivized-collaboration type Article.
• incentivized-collaboration type WebPage.
• incentivized-collaboration type Document.
• incentivized-collaboration type Q386724.
• incentivized-collaboration type CreativeWork.
• incentivized-collaboration type Document.
• incentivized-collaboration type Work.
• incentivized-collaboration type Document.
• incentivized-collaboration P50 me.
• incentivized-collaboration maker me.
• incentivized-collaboration title "Decentralizing the Semantic Web through incentivized collaboration".
• incentivized-collaboration inDataset dataset.
• incentivized-collaboration headline "Decentralizing the Semantic Web through incentivized collaboration".
• incentivized-collaboration isPartOf proceedings_of_the_17th_international_semantic_web_conference_blue_sky_track.
• incentivized-collaboration isPartOf site.
• incentivized-collaboration name "Decentralizing the Semantic Web through incentivized collaboration".
• incentivized-collaboration label "Decentralizing the Semantic Web through incentivized collaboration".
• incentivized-collaboration name "Decentralizing the Semantic Web through incentivized collaboration".
• incentivized-collaboration topic personal_data.
• incentivized-collaboration topic data_integration.
• incentivized-collaboration topic Semantic_Web.
• incentivized-collaboration topic Facebook.
• incentivized-collaboration topic Distributed_ledger.
• incentivized-collaboration topic World_Wide_Web.
• incentivized-collaboration cites web-turns-28-letter.

• first
• previous
• next