EasierRDF
EasierRDF copied to clipboard
w3c
Making RDF easy enough for most developers
This is especially for academic data and demonstrators, and this is less about technology or formalisms, but about politics. Long-term availability is a problem for Linked Data technology in general....
This deserves an issue to itself given the growing popularity of property graph databases and the opportunity for using RDF as an interchange framework between different databases. See also #20...
Knowledge representations may have a probabilistic nature and capturing that is especially important for complex business domains where data is ... non-stationary or contextual. This is often seen in `machine...
There are a couple of issues with numerical datatypes that make the accurate use of RDF for numerical data error-prone. The use of `xsd:float` and `xsd:double` entails a risk *...
Canonicalization is the ability to represent RDF in a consistent, predictable serialization. It is essential for diff and digital signatures. Developers expect to be able to diff two files, and...
Blank nodes
They are an important convenience for RDF authors, but they cause insidious downstream complications. They have subtle, confusing semantics. (As Nathan Rixham once aptly put it, a blank node is...
From #50 ... Anonymous classes (e.g. a blank node as the object of rdf:type) are complicated to consume and mix ontological layers. The instance shouldn't manage its own class, in...
It is needlessly confusing to have both rdf: and rdfs: namespaces, such as rdf:type versus rdfs:subClassOf . They should be transparently merged, to allow consistent use of rdf:, but with...
Shapes are important to describe business objects (entities) in RDF, see #63. There are several shape or shape-like languages: - SHACL - ShEx - JSONLD Frames - GraphQL Note: there...
