Develop API for typed name components in naming convention
name::Component APIs to support typed name components for segment number, version number, timestamp, and sequence number.
#4 Updated by Junxiao Shi 10 months ago
https://gerrit.named-data.net/#/c/ndn-cxx/+/5043/ patchset1 has a
convention argument in each API, which could cause difficulty for eventual removal.
patchset3 is an alternate design that only offers global settings for encoding and decoding conventions. While it is easier for eventual removal, every part of an application would have to adopt the same convention at least for encoding. Suppose for some reason PSync wants REV2 (to talk to other nodes using new convention) and management client wants REV1 (to talk to legacy application), an application using both would have to switch the global encoding convention setting back-and-forth, and won't work at all if it's multi-threaded.