Data Interoperability

MitziLaszlo · August 1, 2019, 1:29pm

solid/process/blob/master/panels.md

# Solid Panels

Below is a listing of [Solid Panels](README.md#solid-panels). Solid Panels are groups of individuals focused on a specific problem or domain relevant to Solid, with an aim to propose changes to the Solid Specification, Solid Roadmap, and/or Supporting Documentation. Anyone may join a panel or suggest a new panel.

Anyone can create a Solid Panel by submitting a request to the Solid W3C community group mailing list, or by making a pull request directly to this document.

This listing helps people find panels in which they may want to participate, and helps editors find panels to consult as part of the editorial process.

## Example Panel
This is an example that people can use as a template for submitting their own panels. A description of the panel, including its focus and goal, should go here.

### Communication channels
- Link to join mailing list goes here
- Link to public chat goes here
- Any other public communication link goes here

### Panelists
- [Panellist Name](link to github profile) <[email@example.org](mailto:email@example.org)> (@github handle)
- [Panellist Name](link to github profile) <[email@example.org](mailto:email@example.org)> (@github handle)

This file has been truncated. show original

michielbdejong · August 1, 2019, 2:17pm

I made a first start with this in https://github.com/solid/solid-panes/blob/master/Documentation/conventions.md

JimSchoening · August 1, 2019, 9:05pm

The Avatar team’s approach is posted at Common Core Ontology with Linked Data.

We’re renaming our Common User Profile to call it ‘card+,’ since it allows compatible card extensions that all conform to the Common Core Ontologies (CCO).

Since this group seems to have consensus on using FOAF for the Solid Card, we will post a solution soon that is both FOAF and CCO compatible, plus allows compatible extensions.

More will be posted within a week or maybe two.

Jim Schoening

JKReynolds · August 5, 2019, 5:59pm

Data Interoperability, Solid, and CardX

August 5th, 2019

Introduction

We propose CardX, an extended form of the existing Solid card. CardX stores the same information as the existing card format; however, apart from infrastructure data such as storage and account information, the data is mapped using the Common Core Ontologies (CCO)¹.

The CCO, which is based on Basic Formal Ontology² (BFO) provide a rich set of mid and upper ontologies that can fulfill the role of cross-domain information representation. This enables the ability for multiple individuals to share and leverage information relevant to them. It is infinitely extensible and supports querying information at multiple levels so that the degree of exactness vs. generality required by a given use case can be applied³.

While there are several benefits to using the CCO, the most beneficial aspect with regards to data interoperability is the fact that it can be extended in a logically consistent manner. To accomplish this extension, the CCO is accompanied by a rule-guided method. The combination of the CCO and this methodology allows different groups to develop ontologies and still arrive at semantically interoperable models⁴.

The CCO is compatible with other ontologies, such as FOAF⁵, already in use by the Solid community. In the coming weeks our team will be releasing tools for working with CardX.

These tools will support three CardX use cases:

A Solid user who would like to use CardX by adding the CardX triples to their existing card.
A Solid developer how wishes to use the CCO while keeping their app available to users of the current Solid card.
A Solid user who wishes to replace their Solid card with the CardX.

These tools include:

CardX Creation App: This app allows a Solid user to populate the fields of their CardX using a number of data sources including their existing card, manual entry into a form, and appropriately mapped RDF files produced by the Facebook data retrieval tool (soon to be released).
CardX-lib: This library provides tools for converting information from the existing card into the CardX format within a developer’s app, as well as for converting the data back into the existing card format for storing changes back to a user’s Solid pod. The inverse functionality will also be supported, allowing developers of currently existing apps to convert data from CardX users to the current card format for use in their apps. Additionally, this library will provide functionality for card/CardX reconciliation for users who choose to maintain both card formats on their pod.

Recently our team launched a calendar app that utilized the CCO to store event data. Today we will be releasing a weather application that, in addition to display a user’s local weather based on their address, will be able to display events previously scheduled for the current day using the calendar app. These apps demonstrate a cross application data use case that show the benefits of using a common, extensible ontology.

Contacts

Please contact the individuals below with questions or requests for support:

Jason Reynolds (Polaris Alpha), Solid forum ID: JKReynolds
Robert Ganger (CUBRC, Inc.), Solid forum ID: rganger
James Schoening (US Army CCDC C5ISR), Solid forum ID: JimSchoening

References

¹ “CommonCoreOntology,” GitHub. [Online]. Available: https://github.com/CommonCoreOntology. [Accessed: 2August-2019].
² “Basic Formal Ontology (BFO) | Home.” [Online]. Available: https://basic-formal-ontology.org/. [Accessed: 2August-2019].
³ “Data Integration for the Individual using the Solid Platform,” GitHub. [Online]. Available: https://github.com/avatar-use-cases/CCO-LD-Avatar/blob/master/Data Integration%. [Accessed: 2-August2019].
⁴ “Ontology” [Online]. Available: https://www.cubrc.org/index.php/data-science-and-information-fusion/ontology [Accessed: 2-August-2019]
⁵ “FOAF Vocabulary Specification.” [Online]. Available: http://xmlns.com/foaf/spec/. [Accessed: 21-May-2019].

JKReynolds · August 9, 2019, 5:11pm

@MitziLaszlo @michielbdejong We are currently reviewing how CardX would impact or could benefit current Solid apps as well as confirming it’s alignment with schema.org and vcard. Afterward, we will post what we find.

MitziLaszlo · August 12, 2019, 12:24pm

Hi @JKReynolds,

Great work! Best to connect with the other panellists on the Data Interoperability Panel.

Mitzi

tonanto · September 4, 2019, 4:24pm

thanks for info

Topic		Replies	Views
Client Side Libraries Panel	5	685	August 23, 2019
Artificial Intelligence Panel	13	1505	September 8, 2019
About the Interoperability category Interoperability	0	488	June 2, 2020
Work towards interoperable ecosystems in Solid Interoperability	21	1465	June 8, 2020
Solid Application Access Request UI Interoperability	2	717	July 18, 2022

Data Interoperability

Data Interoperability, Solid, and CardX

Introduction

Contacts

References

Related Topics