Skip to content

Revise numbering scheme to avoid clash with OWASP Top 10 #24

@bkimminich

Description

@bkimminich

Currently the numbering scheme is A1:2019, A2:2019 etc. which is identical to the way OWASP Top 10 is doing it. Their latest entries are A1:2017 to A10:2017. This could cause confusion such as people might assume that the OWASP Top 10 had a 2019 release when only seeing references to A1:2019 etc. somewhere.

For comparison, the Docker Top 10 (https://github.com/OWASP/Docker-Security) avoid this by using D1, D2 etc. as their numbering scheme. (They lack the year of document release though.)

Recommendation

As A is taken by OWASP Top 10 and no other single-letter comes to mind change numbering scheme into API1:2019 to API10:2019.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions