3 ms·
I think this is nice but having this in and a lot of other meta data in a machine readable form would be nicer. You could also think of things like licenses a a
by jillesvangurp 7y ago
I think this is nice but having this in and a lot of other meta data in a machine readable form would be nicer. You could also think of things like licenses a and copyrights.
Technically, the problem this specification solves is making it easier to find security related metadata for projects that typically have this information already but just not an easy to find place. So, the next logical step would be making this machine readable so IDEs, project hosting websites, and other tools, can do the right things instead of having to parse files intended for humans with no consistently used syntax.
- sho 7y agoLooks pretty machine readable to me? This is the consistent syntax to be used.
- jillesvangurp 7y agoWas expecting something like a yaml or json file to be a good standard for this. It's nearly 2020, we should not be improvising text file formats in standards anymore. .txt screams intended for humans.
- sho 7y agoYou're thinking too short term. .txt far predates, and will far outlast, any standard du jour. I bet you wouldn't be so gung ho about security.xml. I really don't see the issue. robots.txt works just fine, and this is simply following in its highly successful footsteps. What you suggest is change for change's sake.