Matches in Ruben’s data for { ?s ?p ?o }
- WhatsInAPod maker me.
- WhatsInAPod maker wout_slabbinck.
- WhatsInAPod maker ruben_dedecker.
- WhatsInAPod maker patrick_hochstenbach.
- WhatsInAPod maker jesse_wright.
- WhatsInAPod maker me.
- WhatsInAPod title "What’s in a Pod? – A knowledge graph interpretation for the Solid ecosystem".
- WhatsInAPod isPartOf proceedings_of_the_6th_workshop_on_storing_querying_and_benchmarking_knowledge_graphs.
- WhatsInAPod name "What’s in a Pod? – A knowledge graph interpretation for the Solid ecosystem".
- WhatsInAPod label "What’s in a Pod? – A knowledge graph interpretation for the Solid ecosystem".
- WhatsInAPod name "What’s in a Pod? – A knowledge graph interpretation for the Solid ecosystem".
- WhatsInAPod topic publication.
- WhatsInAPod topic interoperability.
- WhatsInAPod topic data_access.
- WhatsInAPod topic Solid.
- WhatsInAPod topic Web_API.
- WhatsInAPod topic Linked_Data.
- WhatsInAPod topic World_Wide_Web.
- WhatsInAPod subject publication.
- WhatsInAPod subject interoperability.
- WhatsInAPod subject data_access.
- WhatsInAPod subject Solid.
- WhatsInAPod subject Web_API.
- WhatsInAPod subject Linked_Data.
- WhatsInAPod subject World_Wide_Web.
- WhatsInAPod authorList b0_b1873.
- WhatsInAPod topic publication.
- WhatsInAPod topic interoperability.
- WhatsInAPod topic data_access.
- WhatsInAPod topic Solid.
- WhatsInAPod topic Web_API.
- WhatsInAPod topic Linked_Data.
- WhatsInAPod topic World_Wide_Web.
- WhatsInAPod abstract "The Solid vision aims to make data independent of applications through technical specifications, which detail how to publish and consume permissioned data across multiple autonomous locations called “pods". The current document-centric interpretation of Solid, wherein a pod is solely a hierarchy of Linked Data documents, cannot fully realize this envisaged independence. Applications are left to define their own APIs within the Solid Protocol, which leads to fundamental interoperability problems and the need for associated workarounds. The broader longterm vision for Solid is confounded with the concrete HTTP interface to pods today, leading to a narrower solution space to address these core issues. We examine the mismatch between the vision and the prevalent document-centric interpretation, and propose a reconciliatory graph-centric interpretation wherein a pod is fundamentally a knowledge graph. In this article, we contrast the existing and proposed interpretations in terms of how they support the Solid vision. We argue that the knowledge-centric interpretation can improve pod access through different Web APIs that act as views in a database sense. We show that our zoomed-out interpretation provides improved opportunities for storage, publication, and querying of decentralized data in more flexible and sustainable ways. These insights are crucial to reduce the dependency of Solid apps on implicit API semantics and local assumptions about the shape and organization of data and the resulting performance. The suggested broader interpretation can guide Solid through its evolution into a heterogeneous yet interoperable ecosystem that accommodates a multitude of read/write data access patterns.".
- WhatsInAPod datePublished "2022".
- WhatsInAPod mainEntityOfPage dedecker_quweda_2022.
- WhatsInAPod sameAs WhatsInAPod.
- WhatsInAPod isPrimaryTopicOf dedecker_quweda_2022.
- WhatsInAPod page dedecker_quweda_2022.
- WhatsInAPod number "81".
- WhatsInAPod number "96".
- WhatsInAPod number "3279".
- WhatsInAPod volume "3279".
- WhatsInAPod locator "81".
- WhatsInAPod locator "96".
- WhatsInAPod locator "3279".
- WhatsInAPod volume "3279".
- WhatsInAPod position "3279".
- WhatsInAPod volumeNumber "3279".
- WhatsInAPod endingPage "96".
- WhatsInAPod startingPage "81".
- WhatsInAPod pageEnd "96".
- WhatsInAPod pageStart "81".
- WhatsInAPod pageEnd "96".
- WhatsInAPod pageStart "81".
- idlab.technology type Document.
- idlab.technology type Q386724.
- idlab.technology type CreativeWork.
- idlab.technology type Document.
- idlab.technology type Work.
- idlab.technology type Document.
- idlab.technology primaryTopic organization.
- idlab.technology topic organization.
- idlab.ugent.be type Document.
- idlab.ugent.be type Q386724.
- idlab.ugent.be type CreativeWork.
- idlab.ugent.be type Document.
- idlab.ugent.be type Work.
- idlab.ugent.be type Document.
- idlab.ugent.be primaryTopic organization.
- idlab.ugent.be topic organization.
- www.ugent.be type Document.
- www.ugent.be type Q386724.
- www.ugent.be type CreativeWork.
- www.ugent.be type Document.
- www.ugent.be type Work.
- www.ugent.be type Document.
- www.ugent.be primaryTopic Ghent_University.
- www.ugent.be topic Ghent_University.
- www.imec-int.com type Document.
- www.imec-int.com type Q386724.
- www.imec-int.com type CreativeWork.
- www.imec-int.com type Document.
- www.imec-int.com type Work.
- www.imec-int.com type Document.
- www.imec-int.com primaryTopic IMEC.
- www.imec-int.com topic IMEC.
- Provenance title "provenance".
- Provenance name "provenance".
- Provenance label "provenance".
- Provenance name "provenance".
- Provenance page publication.
- Provenance page publication.
- Provenance page publication.
- Provenance page publication.
- Provenance page publication.
- Provenance page publication.
- Provenance page publication.
- Provenance page publication.
- Provenance page publication.