Add uri sample with query showing it isn't captured

[JordonPhillips]

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[david-perez]

I would explicitly call out somewhere that labels and greedy labels can only capture path segments from the URI. A far as I can see there is no mention in the spec as to what exactly do labels capture from the URI.

In the example(s), I would add #fragment to the end of the URI to convey that path fragments are also not captured by labels, or provide a separate example. I would also add the example(s) to the "Greedy labels" section.

[david-perez]

These changes look good but what I'm missing is a sentence in the spec saying something like "Labels can only capture path segments".

As of now, I think the spec is ambiguous as to what exactly do labels capture. Given:

1. Patterns MAY contain label placeholders in the path,
2. Labels MUST NOT appear in the query string; and
3. Labels MUST NOT appear in the fragment,

then the pattern /foo/{bar+} adheres to the above three rules, but given the URI path /foo/quux?key=value#fragment, the spec doesn't explicitly say that the label {bar+} will only capture the string quux and not the string quux?key=value#fragment. With these changes, the examples implicitly convey this, but the question "what exactly do labels capture?" is never directly addressed by the spec.

[JordonPhillips]

what I'm missing is a sentence in the spec saying something like "Labels can only capture path segments".

I added that in already:

Labels only capture path segments.

[david-perez]

Ah, missed that in the diff. Looks good.

Commit message needs rewording before pushing, since now we're making the spec clearer in this respect and we're adding two examples, one for query string, one for fragment.