Ruben Verborgh’s data

Matches in Ruben’s data for { <https://dx.doi.org/10.1109/NWeSP.2011.6088202> ?p ?o }

• NWeSP.2011.6088202 author rik_van_de_walle.
• NWeSP.2011.6088202 author joaquim_gabarro_valles.
• NWeSP.2011.6088202 author me.
• NWeSP.2011.6088202 author me.
• NWeSP.2011.6088202 creator rik_van_de_walle.
• NWeSP.2011.6088202 creator joaquim_gabarro_valles.
• NWeSP.2011.6088202 creator me.
• NWeSP.2011.6088202 creator me.
• NWeSP.2011.6088202 about Web_service.
• NWeSP.2011.6088202 about Provenance.
• NWeSP.2011.6088202 about RESTdesc.
• NWeSP.2011.6088202 about Representational_state_transfer.
• NWeSP.2011.6088202 about Web_API.
• NWeSP.2011.6088202 about Metadata.
• NWeSP.2011.6088202 about Facebook.
• NWeSP.2011.6088202 about RDF.
• NWeSP.2011.6088202 author rik_van_de_walle.
• NWeSP.2011.6088202 author joaquim_gabarro_valles.
• NWeSP.2011.6088202 author me.
• NWeSP.2011.6088202 author me.
• NWeSP.2011.6088202 coparticipatesWith rik_van_de_walle.
• NWeSP.2011.6088202 coparticipatesWith joaquim_gabarro_valles.
• NWeSP.2011.6088202 coparticipatesWith me.
• NWeSP.2011.6088202 coparticipatesWith me.
• NWeSP.2011.6088202 type ScholarlyArticle.
• NWeSP.2011.6088202 type Article.
• NWeSP.2011.6088202 type Document.
• NWeSP.2011.6088202 type Document.
• NWeSP.2011.6088202 type Document.
• NWeSP.2011.6088202 type Q386724.
• NWeSP.2011.6088202 type CreativeWork.
• NWeSP.2011.6088202 type Work.
• NWeSP.2011.6088202 P50 rik_van_de_walle.
• NWeSP.2011.6088202 P50 joaquim_gabarro_valles.
• NWeSP.2011.6088202 P50 me.
• NWeSP.2011.6088202 P50 me.
• NWeSP.2011.6088202 maker rik_van_de_walle.
• NWeSP.2011.6088202 maker joaquim_gabarro_valles.
• NWeSP.2011.6088202 maker me.
• NWeSP.2011.6088202 maker me.
• NWeSP.2011.6088202 title "Adding Meaning to Facebook Microposts via a Mash-up API and Tracking Its Data Provenance".
• NWeSP.2011.6088202 isPartOf proceedings_of_the_7th_international_conference_on_next_generation_web_services_practices.
• NWeSP.2011.6088202 name "Adding Meaning to Facebook Microposts via a Mash-up API and Tracking Its Data Provenance".
• NWeSP.2011.6088202 label "Adding Meaning to Facebook Microposts via a Mash-up API and Tracking Its Data Provenance".
• NWeSP.2011.6088202 name "Adding Meaning to Facebook Microposts via a Mash-up API and Tracking Its Data Provenance".
• NWeSP.2011.6088202 topic Web_service.
• NWeSP.2011.6088202 topic Provenance.
• NWeSP.2011.6088202 topic RESTdesc.
• NWeSP.2011.6088202 topic Representational_state_transfer.
• NWeSP.2011.6088202 topic Web_API.
• NWeSP.2011.6088202 topic Metadata.
• NWeSP.2011.6088202 topic Facebook.
• NWeSP.2011.6088202 topic RDF.
• NWeSP.2011.6088202 subject Web_service.
• NWeSP.2011.6088202 subject Provenance.
• NWeSP.2011.6088202 subject RESTdesc.
• NWeSP.2011.6088202 subject Representational_state_transfer.
• NWeSP.2011.6088202 subject Web_API.
• NWeSP.2011.6088202 subject Metadata.
• NWeSP.2011.6088202 subject Facebook.
• NWeSP.2011.6088202 subject RDF.
• NWeSP.2011.6088202 authorList b0_b3355.
• NWeSP.2011.6088202 topic Web_service.
• NWeSP.2011.6088202 topic Provenance.
• NWeSP.2011.6088202 topic RESTdesc.
• NWeSP.2011.6088202 topic Representational_state_transfer.
• NWeSP.2011.6088202 topic Web_API.
• NWeSP.2011.6088202 topic Metadata.
• NWeSP.2011.6088202 topic Facebook.
• NWeSP.2011.6088202 topic RDF.
• NWeSP.2011.6088202 abstract "The social networking website Facebook offers to its users a feature called “status updates” (or just “status”), which allows them to create microposts directed to all their contacts, or a subset thereof. Readers can respond to microposts, or in addition to that also click a “Like" button to show their appreciation for a certain micropost. Adding semantic meaning in the sense of unambiguous intended ideas to such microposts can, for example, be achieved via Natural Language Processing (NLP). Therefore, we have implemented a RESTful mash-up NLP API based on a combination of several third party NLP APIs in order to retrieve more accurate results in the sense of emergence. In consequence, our API uses third party APIs opaquely in the background in order to deliver its output. In this paper, we describe how one can keep track of provenance, and credit back the contributions of each single API to the combined result of all APIs. In addition to that, we show how the existence of provenance metadata can help understand the way a combined result is formed, and optimize the result combination process. Therefore, we use the HTTP Vocabulary in RDF and the Provenance Vocabulary. The main contribution of our work is a description of how provenance metadata can be automatically added to the output of mash-up APIs like the one presented in this paper.".
• NWeSP.2011.6088202 datePublished "2011".
• NWeSP.2011.6088202 mainEntityOfPage steiner_nwesp_2011.
• NWeSP.2011.6088202 sameAs NWeSP.2011.6088202.
• NWeSP.2011.6088202 isPrimaryTopicOf steiner_nwesp_2011.
• NWeSP.2011.6088202 page steiner_nwesp_2011.
• NWeSP.2011.6088202 number "342".
• NWeSP.2011.6088202 number "345".
• NWeSP.2011.6088202 locator "342".
• NWeSP.2011.6088202 locator "345".
• NWeSP.2011.6088202 endingPage "345".
• NWeSP.2011.6088202 startingPage "342".
• NWeSP.2011.6088202 pageEnd "345".
• NWeSP.2011.6088202 pageStart "342".
• NWeSP.2011.6088202 pageEnd "345".
• NWeSP.2011.6088202 pageStart "342".