Should we extend xsd:decimal?

Dear Semantic Web community,

an issue has been raised some time ago about the DCAT-3 specification 
[1], related to the use of `xsd:decimal` as the range a property, and 
how a seemingly correct JSON-LD document may produce ill-formed 
`xsd:decimal` literals [2].

Exploring the possible solutions to this issue, I came to the conclusion 
that

- it is a shame that `xsd:decimal` does not support the E notation [3] 
just like `xsd:double` does, and
- actually, many implementations (of RDF, SPARQL, OWL...) do support the 
E notation for `xsd:decimal`.

I created a github repo at

     http://github.com/pchampin/xsd_decimal

to document this issue and the current state of implementations, and 
discuss whether updating the normative definition of `xsd:decimal` would 
be a good idea or not.

Please chime in if you are interested

   pa

[1] https://github.com/w3c/dxwg/issues/1536
[2] 
https://json-ld.org/playground/#startTab=tab-nquads&json-ld=%7B%22%40context%22%3A%7B%22ex%22%3A%22http%3A%2F%2Fexample.com%2Fns%2F%22%2C%22xsd%22%3A%22http%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema%23%22%2C%22ex%3Afoo%22%3A%7B%22%40type%22%3A%22xsd%3Adecimal%22%7D%7D%2C%22ex%3Afoo%22%3A%5B12.3%5D%7D

[3] https://en.wikipedia.org/wiki/Scientific_notation#E_notation