James M Snell wrote:
...
Every Profile document will be associated with an identifier. The
identifier is either a short name or an IRI following the same pattern
as atom:link/@rel values. However, use of the short names will be
> ...
I think in this is a case where you really want a URI.
restricted and must follow a strict convention... Specifically, only
Profiles published through the IETF process will be allowed short
names. For a Profile published as an Internet-Draft, the profile
identifier is the document name. For instance, given a theoretical
draft-snell-profile-blogging-01.txt, the identifier for the Profile is
"draft-snell-profile-blogging-01". For a Profile published as an RFC,
the project identifier is the RFC# in the pattern "RFC####". The
shortnames are always case-insensitive so "rfc9999" is equivalent to
"RFC9999" or "Rfc9999", etc. For all other Profiles, the identifier is
an absolute IRI that SHOULD be dereference-able to retrieve the Profile
document.
"SHOULD be referenceable": doesn't compute, unless you define the
format. (It is not needed for interoperability, so doesn't deserve
RFC2119 keywords).
You would also need to define what you mean by "IETF process". Do
private submissions directly to the RFC Editor count?
Suggestion: just always require URIs; Internet Drafts and RFCs have a
canonical URN through RFC2648. For instance
urn:ietf:rfc:4287
...
BR, Julian
