@ -14,7 +14,7 @@ SPARQL is the query language of choice for RDF data, and NextGraph supports both
OWL is a language (based on RDF) that expresses the schema (also called Ontology) of the data.
When we are talking about publicly available data, most of the time concerning immutable facts like academic data, we use the term LOD for Linked Open Data. But Semantic data doesn't have to be public nor open, and in NextGraph we use RDf to store private and encrypted data that very few people will ever see.
When we are talking about publicly available data, most of the time concerning immutable facts like academic data, we use the term LOD for Linked Open Data. But Semantic data doesn't have to be public nor open, and in NextGraph we use RDF to store private and encrypted data that very few people will ever see.
Eventually RDF is just another data format, like JSON, XML or CSV, except that it has its own characteristics, that are very interesting, and that we will detail now here.
@ -87,7 +87,7 @@ But also because groups of interest tend to gather and establish standard ontolo
At NextGraph, we strive to gather the best existing ontologies out there and propose them to you so you can reuse them. We also make it easy for you to create new ones with graphical tools and editors, so you don't have to have a headache when trying to understand exactly how OWL works. If you know about UML, object-oriented programming, or modelling of data, then you can easily create new ontologies. It is all the same thing. We define classes, properties, and relationships between them.
One last word about RDf and ontologies: because the schema of data is encoded inside in each triple (in the predicate part), there is no need to keep track of the schema of your data, as we normally do with relational databases or even in JSON. The advantage of RDF is that predicates get assigned with globally unique identifiers too, so there is never any ambiguity about the schema of the data. No migrations needed. No data inconsistency neither.
One last word about RDF and ontologies: because the schema of data is encoded inside in each triple (in the predicate part), there is no need to keep track of the schema of your data, as we normally do with relational databases or even in JSON. The advantage of RDF is that predicates get assigned with globally unique identifiers too, so there is never any ambiguity about the schema of the data. No migrations needed. No data inconsistency neither.
@ -76,7 +76,7 @@ This is why NextGraph makes a strong separation between the data that is private
With federated queries, we will be able to ask our friends for recommendation, and to see our social graph in a more meaningful way.
Because Meta stores all the global graph based on the data that we provide to this company (by clicking, liking, commenting, following, etc) that does not mean that the Meta company let us have access to the data that we generated. To the contrary. They keep this data for themselves and share it only with advertisers and the CIA.
Because Meta stores all the global graph based on the data that we provide to this company (by clicking, liking, commenting, following, etc) that does not mean that the Meta company let us have access to the data that we generated. To the contrary. They keep this data for themselves and share it only with advertisers and other high-profile third-parties.
Here with NextGraph, we can finally regain control over our social graph and shared data, and if we are allowed by our peers, we can navigate this social graph freely.