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: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > 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 > > - -- > Peter Saint-Andre > https://stpeter.im/ > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.8 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk+F4VcACgkQNL8k5A2w/vxRvACgoX1+IvQU/W6ZWKF5aCHcoYmV > Py4AoIYMBBxvtmCSkM1Vsy+46USwzumQ > =pg4b > -----END PGP SIGNATURE----- > _______________________________________________ > precis mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/precis -- Joe Hildebrand _______________________________________________ precis mailing list [email protected] https://www.ietf.org/mailman/listinfo/precis
