Merge pull request #163 from BuildingSync/improvement/152-ratings

Add BenchmarkValue element

BuildingSync.xsd

@@ -2271,6 +2271,18 @@
                     </xs:simpleType>
                   </xs:element>
                   <xs:element name="BenchmarkYear" type="xs:gYear" minOccurs="0"/>
+                  <xs:element name="BenchmarkValue" minOccurs="0">
+                    <xs:annotation>
+                      <xs:documentation>The calculated score or rating for the benchmark scenario.</xs:documentation>
+                    </xs:annotation>
+                    <xs:complexType>
+                      <xs:simpleContent>
+                        <xs:extension base="xs:decimal">
+                          <xs:attribute ref="auc:Source"/>
+                        </xs:extension>
+                      </xs:simpleContent>
+                    </xs:complexType>
+                  </xs:element>
                 </xs:sequence>
               </xs:complexType>
             </xs:element>

proposals/2019/Add BenchmarkValue element.md

@@ -0,0 +1,19 @@
+# Add BenchmarkValue element
+
+## Overview
+
+This proposal is to add the `auc:BenchmarkValue` child element to the `auc:Benchmark` element.
+
+## Justification
+
+The `auc:Assessment` element (a child element of the `auc:Building` element) provides a mechanism to assert programs that issue energy labels, ratings, scores, certifications, etc., at the building level; however, there is no corresponding mechanism at the scenario level.
+
+The `auc:Benchmark` element (a child element of the `auc:ScenarioType` element) is available; however, there is nowhere within the schema to assert the calculated score or rating.
+
+## Implementation
+
+1. Add `auc:BenchmarkValue` child element to `auc:Benchmark` element.
+
+## References
+
+N/A