RFR (12): 8215318: Amend the Standard Algorithm Names specification to clarify that names can be defined in later versions

[Sean Mullan]

Please review this change to the Java Security Standard Algorithm Names 
specification [1] to clarify that standard names that are defined in 
later versions of SE are also supported in prior versions, as long as 
the applicable Security APIs are also supported.

Please see the CSR for the motivation and exact wording changes: 
https://bugs.openjdk.java.net/browse/JDK-8215320

This change will also be included in the upcoming Maintenance Reviews of 
the Java SE 8 and 11 Platform JSRs. See [2] for more information.

I have also included the raw diffs below:

diff -r 8829e86def29 
closed/src/java.base/share/specs/security/standard-names.md
--- a/closed/src/java.base/share/specs/security/standard-names.md 
Thu Dec 20 14:21:16 2018 -0500
+++ b/closed/src/java.base/share/specs/security/standard-names.md 
Wed Jan 02 15:39:12 2019 -0500
@@ -20,6 +20,10 @@
  The Java SE Security API requires and uses a set of standard names for
  algorithms, certificate and keystore types.

+Names that are added to subsequent Java SE versions of this specification
+also apply to this version of the specification if the Security APIs that
+those names are defined for are supported.
+
  In some cases naming conventions are given for forming names that are not
  explicitly listed, to facilitate name consistency across provider
  implementations. Items in angle brackets (such as `<digest>` and

--Sean

[1] 
https://docs.oracle.com/en/java/javase/11/docs/specs/security/standard-names.html
[2] 
https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2018-December/000308.html