Re: Why is the value of @version a number?

Hey Lutz,

Thanks for raising this question! I'm not sure what informed the original decision, but I do know that the JSON-LD Working Group has begun discussing some variations on the approach:
https://github.com/w3c/json-ld-syntax/issues/33

If you have some specific thoughts/concerns/ideas around this topic, we'd love your input!

Thanks,
Benjamin
Co-Chair JSON-LD WG
https://www.w3.org/2018/json-ld-wg/
http://json-ld.org/


--

http://bigbluehat.com/

http://linkedin.com/in/benjaminyoung

________________________________
From: Lutz Helm <helm@ub.uni-leipzig.de>
Sent: Friday, August 17, 2018 9:52:40 AM
To: public-linked-json@w3.org
Subject: Why is the value of @version a number?

Hi,

I just stumbled upon the fact that @version has to be a number in
json-ld 1.1 contexts. Is there any reason why this is not a string?
I guess it shouldn't ever happen that a spec is released as patch
version, and there will probably not be more than eight more versions
with nonbreaking changes to the spec, so a decimal number might suffice,
but I'm still a little bit puzzled.

Best regards,
Lutz

--
Lutz Helm
Bereich Digitale Dienste
AG Anwendungsentwicklung

Universitätsbibliothek Leipzig
Beethovenstraße 6, 04107 Leipzig

T: +49 341 97 30566

helm@ub.uni-leipzig.de
https://www.ub.uni-leipzig.de/