futures addition

Future.md

@@ -14,6 +14,10 @@ The SARIF project started with a relatively simple mission, define a standard fo
 
 Ultimately, the SARIF standard would enable the automatic exchange of results from all types of software analysis tools. This page details some of the efforts and investigations that the SARIF team is planning in order to achieve that goal.
 
+## Acronym Change
+
+With an expanded scope the **SARIF** acronym's underlying expansion would change from **S**tatic **A**nalysis **R**esults **I**nterchange **F**ormat to **S**ystematic **A**nalysis **R**esults **I**nterchange **F**ormat.
+
 ## SARIF Field Compatibility
 
 The following table shows mapping between current SARIF terminology as used for static analysis and that of other possible use cases.
@@ -65,3 +69,11 @@ Software doesn't exist in a vacuum. Modern software often runs in a complex ecos
 One way to tackle this problem is to identify a way to link SARIF into a model of that ecosystem, such as what is generated by "observability" tools that leverage OpenTelemetry. Linking of this nature has benefits in both directions. People looking at the entire ecosystem can drill into SARIF details from the global picture. People more focused on individual software components can enrich SARIF results with an understanding of context.
 
 For example, imagine that SARIF identifies a "critical" SQL injection problem in an application. Adding global context would enable adding risk factors that temper that result. The application might only contain read-only, public data. Or it might only be accessible by administrators. Or it might be protected by a runtime protection module. The contextual risk calculation may be only "low".
+
+## Provide Domain-specific Schema Subsets
+
+In order to reduce the overhead of working with the complete SARIF schema and also accommodate the diverse needs of automated software pipelines, domain-specific schema subsets would be created. These would be strict subsets in that they would conform to the master SARIF schema.
+
+Schema subsetting would also allow for the adoption of SARIF in these new domains as the weight of the current schema acts as a barrier to entry.
+
+Additionally, these schema subsets should accelerate the creation of SARIF data manipulation within the build pipeline.