Thinking about this the last couple of days, there were two topics that feel worth sharing:
1. Instead of specifying a specific enumeration in a PSR, a PSR could also describe a policy for how to maintain a specific enum package. For instance, the mentioned country codes for phone numbers PSR could specify that the implementation will be updated when the ITU E.164 registry changes. New enum entries will be added, old entries could be deprecated an removed after 2 years. The PSR could contain an initial implementation, especially if there are additional methods on the enum. 2. Given the mission of the FIG, should we try to limit ourselves to enums that have interop benefits? For instance, log levels and HTTP status codes seem like good candidates, but I can't readily see units of measurement (except potentially for time) being of direct use. -- Vincent -- 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 php-fig+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/29ddd7c5-67a5-4173-b437-5a8c6b2cc9c3n%40googlegroups.com.
