name: disallow empty NameComponent in canonical order section
This commit does not change the meaning of the spec.
It makes the informative part of the spec consistent with the nominative part.
refs #1763
Change-Id: Ibe623d03932516f8ebcaa7e7381288cf7d9edc6a
diff --git a/name.rst b/name.rst
index ee706b1..aeb6181 100644
--- a/name.rst
+++ b/name.rst
@@ -11,16 +11,13 @@
We use a 2-level nested TLV to represent a name.
The Type in the outer TLV indicates this is a Name.
All inner TLVs have the same Type indicating that they each contain a name component.
-There is no restriction on the Value field in a name component and it may not contain any bytes:
+There is no restriction on the Value field in a name component and it may contain any non-empty byte sequence.
::
Name ::= NAME-TYPE TLV-LENGTH NameComponent*
NameComponent ::= NAME-COMPONENT-TYPE TLV-LENGTH BYTE+
-.. % 0 or many name components in name
-.. % 0 or many bytes in name component
-
NDN URI Scheme
~~~~~~~~~~~~~~
@@ -56,7 +53,7 @@
Canonical Order
~~~~~~~~~~~~~~~
-In several contexts in NDN packet processing, it is useful to have a consistent ordering of names and name components. NDN names consist of a sequence of NameComponents, and each NameComponent is a sequence of zero or more 8-bit bytes. The ordering for components is such that:
+In several contexts in NDN packet processing, it is useful to have a consistent ordering of names and name components. NDN names consist of a sequence of NameComponents, and each NameComponent is a sequence of one or more 8-bit bytes. The ordering for components is such that:
- If *a* is shorter than *b* (i.e., has fewer bytes), then *a* comes before *b*.