> > […] > > I realize that FIG has taken the IETF approach, but I just don't think it > works for when you try to apply it to code. Regardless of whether or not > adding type hints to (eg) PSR-3 requires an entirely new PSR, the > package/namespaces shouldn't be any different, it should just be a major > version change in the composer package. >
Just for the record: IETF has two naming schemes: A sequential one for the RFCs and a different sequential one for the Internet Standards. The whole process is described in RFC 1796 <https://tools.ietf.org/html/rfc1796>. Using this naming scheme for FIG would require a second numbering scheme for PHP-Fig Standards. That would f.e. mean that there is a PHP-Fig Standard X that describes Coding Styles. The actual implementation is described by PSR-1 which then was "obsoleted" (Please, don't start a discussion on whether it was obsoleted or not, this is just to clarify the point!) by PSR-2 which might become obsoleted by PSR-12 as soon as that is finished and accepted. So for every PHP-FIG Standard there can be multiple successive PSRs. Cheers Andreas -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/30c78335-5e7c-486f-8611-9e95ddcd0c5f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
