Iwan Aucamp

One option to solve this is to enforce that `rdflib.terms.Literal` always has a datatype, but then we won't be able to support RDF 1.0 anymore. I'm somewhat okay with this,...

I think the best option is to just not allow null literals.

> One option to solve this is to enforce that `rdflib.terms.Literal` always has a datatype, but then we won't be able to support RDF 1.0 anymore. I'm somewhat okay with...

> An other option: allow `None` datatype but for `__eq__` and `__hash__` use `self.datatype or XSD.string` to get the datatype. This may be quite unexpected if someone is not familiar...

Another related issue: - https://github.com/RDFLib/rdflib/issues/670

> > `def __new__(value: str, lang: str, datatype: str)` -> Create with the supplied datatype and lang, potentially with some validation. > > This variant seems dangerous because it indeed...

One problem is that SPARQL 1.1 defines Simple Literal: > [18.1.2. Simple Literal](https://www.w3.org/TR/sparql11-query/#simple_literal) > > Definition: Simple Literal > > The set of Simple Literals is the set of all...

> One problem is that SPARQL 1.1 defines Simple Literal: > > > [18.1.2. Simple Literal](https://www.w3.org/TR/sparql11-query/#simple_literal) > > Definition: Simple Literal > > The set of Simple Literals is the...

What we can also do is have a `simple` attribute on Literal which is true if the Literal is initialized with a null datatype :thinking: But we can maybe add...

> What we can also do is have a `simple` attribute on Literal which is true if the Literal is initialized with a null datatype thinking This would complicate equality...