Added mention of service description method as a potential future direction to reduce duplication (Issue #60)

Issue #60

Author: drchristhorpe

EditorsDraft/index.html

@@ -2227,7 +2227,9 @@
 future iterations of the specification by becoming involved in the communities
 associated with Open Active and the open specification.
 
-
+In a future version, it is imagined that an API method describing the service,
+and including such things as the links to Privacy Policy, Terms and Conditions
+and the target for a ReserveAction could be used to reduce data duplication. 
 
 </section>
 

EditorsDraft/live.html

@@ -1962,7 +1962,10 @@ <h2 id="draft-community-group-report-10-september-2018">Draft Community Group Re
 </ul><p>We have not yet decided what the priorities are, or whether all of these
 requirements are in scope for version 1.0 and would encourage people to shape
 future iterations of the specification by becoming involved in the communities
-associated with Open Active and the open specification.</p></section><section class="normative"><!--OddPage--><h2 id="new-open-active-models-defined-in-the-0-5-booking-api-specification-which-are"><span class="secno">9. </span>New Open Active models defined in the 0.5 Booking API specification which are</h2><p>not yet reflected in the current version (1.1) of the Open Active Modelling
+associated with Open Active and the open specification.</p><p>In a future version, it is imagined that an API method describing the service,
+and including such things as the links to Privacy Policy, Terms and Conditions
+and the target for a ReserveAction could be used to reduce data duplication.
+</p></section><section class="normative"><!--OddPage--><h2 id="new-open-active-models-defined-in-the-0-5-booking-api-specification-which-are"><span class="secno">9. </span>New Open Active models defined in the 0.5 Booking API specification which are</h2><p>not yet reflected in the current version (1.1) of the Open Active Modelling
 Specification.</p><section><h3 id="error"><span class="secno">9.1 </span>Error</h3><table>
 <thead>
 <tr><th>Property</th>