3 ms·
As well as a nigh tabular form in "N-triples" and "N-quads" https://www.w3.org/TR/n-triples/ https://www.w3.org/TR/n-triples/ https://www.w3.org/TR/n-quads/
by tejtm 3y ago
As well as a nigh tabular form in "N-triples" and "N-quads"
https://www.w3.org/TR/n-triples/ https://www.w3.org/TR/n-triples/
https://www.w3.org/TR/n-quads/ https://www.w3.org/TR/n-quads/
which can end up as the easiest formats to work with sometimes.
There are tools like 'rapper' and 'serd' to convert to and from the various formats.
https://librdf.org/raptor/rapper.html https://librdf.org/raptor/rapper.html
https://drobilla.net/software/serd.html https://drobilla.net/software/serd.html
- jshen 3y agoThe problem is that they aren’t tabular and the examples they give which make them look simple are incomplete. For example, they rarely show examples that specify the language or data type. A truly tabular format is hextuples. https://github.com/ontola/hextuples https://github.com/ontola/hextuples
- tejtm 3y ago1000% agree. My dabbling in that direction stopped at five (name-spaced) identifiers. Effectively extending n-quads with an "edge" identifier. Mainly to eliminate blank-nodes but it handed the optional language & typing just fine and more importantly for my use case allowed for the uri to be expressed as curie (namespace) and a local_id each in their own column.