Using namespace scoping seems reasonable. Just about any separator would
suffice, as in "::" from C++ & Perl, "." from a variety of languages,
":" from xml, etc.
Tony Hansen
PS. I would have called it C++ namespacing.
On 4/11/2012 5:50 PM, Peter Saint-Andre wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We could go all Perly and do FreeClass::resourcepart
;-)
On 4/11/12 2:33 PM, Joe Hildebrand wrote:
That seems like a reasonable idea. Is there a suggested naming
pattern that denotes the superclass? E.g. ResourceFreeClass,
LocalpartNameClass
On 4/11/12 1:54 PM, "Peter Saint-Andre"<[email protected]>
wrote:
While writing documents that subclass the base PRECIS classes,
I've found myself naming the subclasses (e.g., rfc6122bis talks
about the localpart subclass of the NameClass and the resourcepart
subclass of the FreeClass). Is this something we want to encourage?
If so, does it make sense to gather those names when people
register new uses of PRECIS as requested in the framework
document?
Peter
_______________________________________________
precis mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/precis
