Add paragraph about service query and fragment rules.

index.html

@@ -738,7 +738,7 @@ <h2>
       <pre class="nohighlight">
 did-reference      = did (did-fragment-reference / did-service-reference)
 did-fragment-reference  = "#" did-fragment
-did-service-reference   = ";" service-id] [ "/" service-path ] [ "?" service-query ] [ "#" service-fragment ]
+did-service-reference   = ";" service-id [ "/" service-path ] [ "?" service-query ] [ "#" service-fragment ]
 service-id         = ALPHA / DIGIT / "." / "-" / "_"
       </pre>
 
@@ -748,7 +748,7 @@ <h3>
         </h3>
 
         <p>
-  A generic <a>DID fragment</a> (the did-fragment rule in Section
+  A generic <a>DID fragment</a> (the <pre>did-fragment</pre> rule in Section
   <a href="#did-reference"></a>) is identical to a URI
   fragment and MUST conform to the ABNF of the fragment ABNF rule in
   [[RFC3986]]. A DID fragment MUST be used only as a method-independent
@@ -782,14 +782,20 @@ <h3>
       <p>
 A DID Reference Service path (the <pre>service-path</pre> rule above) is
 identical to a URI path and MUST conform to the ABNF of the path-rootless ABNF
-rule in [[RFC3986]]. A DID path is used to address resources available via a DID
+rule in [[RFC3986]]. The path is used to address resources available via a DID
 service endpoint. See Section <a href="#service-endpoints"></a>.
       </p>
 
       <p>
 A specific DID scheme MAY specify ABNF rules for DID Reference service paths
 that are more restrictive than the generic rules in this section.
       </p>
+
+      <p>
+A DID Reference Service <pre>query</pre> and <pre>fragment</pre> parts are
+identical to their URI counterparts and MUST conform to the ABNF of the query
+and fragment rules in [[RFC3986]].
+      </p>
     </section>
 
     <section>