- From: Pierre-Antoine Champin via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Oct 2022 21:44:41 +0000
- To: public-dxwg-wg@w3.org
The more I think about this issue, the more I believe that the problem is the definition of `xsd:decimal` itself. It should allow the E notation. And the good new is... in practice, it kind of does. I've done my research, and a significant number of RDF implementations supporting `xsd:decimal` are perfectly happy with, e.g., "1.23E1"^^xsd:decimal. I have created a repo describing the issue, and the current state of implementations: https://github.com/pchampin/xsd_decimal/ I thought I would share this with the semantic web mailing list to get a sense of the community's opinion about this. @iherman, @gkellogg, what do you think? To get back to your issue, @jakubklimek, my conclusion is that you should be using strings to be on the safe side, *but* in many cases you may still use numbers and not run into any problem, because many implementations will recognized these non-standard xsd:decimals produced by JSON-LD... -- GitHub Notification of comment by pchampin Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1536#issuecomment-1294106410 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 October 2022 21:44:43 UTC