- From: Amirouche <amirouche@hyper.dev>
- Date: Tue, 22 Jun 2021 13:46:56 +0200
- To: Dave Raggett <dsr@w3.org>
- Cc: Sarven Capadisli <info@csarven.ca>, semantic-web@w3.org, marie.destandau@inria.fr
On 2021-06-22 11:31, Dave Raggett wrote: > My two cents worth: > > Knowledge graphs can be considered as graph based representations of > data, data models, metadata, and semantics. In principle, knowledge > graphs can expose services for local or remote applications, that are > subject to role based access control. A SPARQL end-point is just one > possibility. > > I like Jo Stichbury’s explanation: > >> Knowledge graphs are able to capture diverse meta-data annotations >> such as provenance or versioning information, which make them ideal >> for working with a dynamic dataset. There is an increasing need to >> account for the provenance of data and include it so that the >> knowledge can be assessed by its consumers in terms of credibility >> and trustworthiness. A knowledge graph can answer what it knows, and >> also how and why it knows it. > > Federated knowledge graphs are where graphs are split across databases > held at different locations and managed by different groups, e.g. > different parts of an enterprise, or different entities within a > national health service. > >> On 22 Jun 2021, at 09:04, Sarven Capadisli <info@csarven.ca> wrote: >> >> On 22/06/2021 09.29, Pierre-Antoine Champin wrote: >> >>> Dear SemWebers, >>> with a few other colleagues, I am collating a list of projects, >>> tools and demos showcasing how RDF technologies make it easier to >>> build /Federated Knowledge Graphs/. Do you have any link to >>> suggest? >>> thanks in advance >> >> What's definition of "federated knowledge graphs"? >> Great answer above. Maybe the tool created by M. Destandau (in cc) works with federated graphs?
Received on Tuesday, 22 June 2021 11:47:29 UTC