4 ms·

Funnily that's what the s semantic web stack achieved. JSON-LD, RDF/XML, turtle, n3 etc etc all different serialisations for the same knowledge. Choose the se

by jerven 11y ago

Funnily that's what the s semantic web stack achieved. JSON-LD, RDF/XML, turtle, n3 etc etc all different serialisations for the same knowledge. Choose the serialisation on the use case but no need to remodel your data evertime.

haddr 11y ago
Not 100%.. N3 and Turtle don't have the same expressiveness. Then there is XML... Semantic web is quite easy when it comes to Linked Data (and RDF/S subset), but is becoming painful when more expressiveness is necessary. Unfortunately, in many cases using only RDF/S is not enough, and some more heavyweight reasoning is required. This is both hard and not scalable for bigger sets of data. Then there is the Open World Assumpltion, which is somehow contrary to what a typical person would expect. You can't easily validate your data for some missing property, because of what OWA assumes: we don't know so we can't tell if it's false... Anyway Semantic Web has left a nice and mature technology stack, that is great for many tasks. Most of knowledge modelling use cases can be done with RDF and with multiple tools that supports it's creation, editing, reasoning, querying, visualisation, etc.
- jerven 11y ago
  You are right meant to write NTriples not N3 but editing on the phone is such a disaster. N3 adds a rule language next to the data description over RDF. XML disallows a few things that are possible in turtle but in practical terms there are very few cases where that could make a possible difference, e.g. who has a \beep code point in their normal text. OWL is powerfull but hard like all description logics, they ar e tools that very very few developers really master. Yet can be used for very interesting things. Validation is not the goal of OWL and is therefore not well supported. ShACL or whatever comes out of W3C for schema descriptions and constraints will be easier and more performant for this use case. On the last para: yes, yes and yes. Very mature stack with a lot of competition and innovation. Cheers!

by jerven 11y ago

haddr 11y ago

Not 100%.. N3 and Turtle don't have the same expressiveness. Then there is XML... Semantic web is quite easy when it comes to Linked Data (and RDF/S subset), but is becoming painful when more expressiveness is necessary. Unfortunately, in many cases using only RDF/S is not enough, and some more heavyweight reasoning is required. This is both hard and not scalable for bigger sets of data. Then there is the Open World Assumpltion, which is somehow contrary to what a typical person would expect. You can't easily validate your data for some missing property, because of what OWA assumes: we don't know so we can't tell if it's false... Anyway Semantic Web has left a nice and mature technology stack, that is great for many tasks. Most of knowledge modelling use cases can be done with RDF and with multiple tools that supports it's creation, editing, reasoning, querying, visualisation, etc.

jerven 11y ago
You are right meant to write NTriples not N3 but editing on the phone is such a disaster. N3 adds a rule language next to the data description over RDF. XML disallows a few things that are possible in turtle but in practical terms there are very few cases where that could make a possible difference, e.g. who has a \beep code point in their normal text. OWL is powerfull but hard like all description logics, they ar e tools that very very few developers really master. Yet can be used for very interesting things. Validation is not the goal of OWL and is therefore not well supported. ShACL or whatever comes out of W3C for schema descriptions and constraints will be easier and more performant for this use case. On the last para: yes, yes and yes. Very mature stack with a lot of competition and innovation. Cheers!