On Tue, Sep 12, 2017 at 07:54:31AM -0500, Kate Stewart wrote: > Of concern, there are new fields added in 2.1 that are > not present in 2.0 (backwards compatibility), its best > the file is correctly labeled.
If you use the new-in-2.1 properties [1], you need to declare 2.1.
But if you don't use them, you can safely declare 2.0 and support both
older parsers that only handle 2.0 and new parsers that understand all
of 2.1.
As a useful alternative/supplement to the current release-notes
approach [1], I like the “New in {version}” annotations that Python
has for its properties (e.g. [2]). That makes it easy to discover
compat implications as you fill in a property, without having to jump
back and forth between the property definitions and the release notes.
Cheers,
Trevor
[1]: https://spdx.org/spdx-specification-21-web-version#h.1sh8jn1fc5zw
[2]:
https://docs.python.org/3.5/library/unittest.html#unittest.TestCase.skipTest
Cheers,
Trevor
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
