Re: Creating a Registry for community provided Attributes

['Andreas Heigl' via PHP Framework Interoperability Group]

Hey Matteo

Am 12.06.25 um 12:44 schrieb Matteo Beccati:

Hey Andreas,

I've replied on Mastodon before reading your post here. Why not having a new "standard" Attributes PER, or am I talking nonsense?

Attributes though can provide different solutions to different problems.

So how would that fit into the problem-space?







BUt I am looking forward to how others see that!

Cheers

Andreas
--
                                                              ,,,
                                                             (o o)
+---------------------------------------------------------ooO-(_)-Ooo-+
| Andreas Heigl                                                       |
| mailto:andr...@heigl.org                  N 50°22'59.5" E 08°23'58" |
| https://andreas.heigl.org                                           |
+---------------------------------------------------------------------+
| https://hei.gl/appointmentwithandreas                               |
+---------------------------------------------------------------------+
| GPG-Key: https://hei.gl/keyandreasheiglorg                          |
+---------------------------------------------------------------------+

--
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 visit 
https://groups.google.com/d/msgid/php-fig/b877073c-ef85-4dd6-8d65-e625fff34112%40heigl.org.

After reading up on the details of the PER I am still hesitant whether it is the right thing... To me the PSR and PER are regarding one solution to a problem. The PSR being "just" one solution, the PER regarding changing solutions, but still to one problem. I am totally with you that the topic of solving the one problem (there there currently not being a good, easy and central way to distribute user-land attributes) should be handled in a PSR (or a PER). But whether the result is then to go for the PER process or eventually something totally different - also depending on how the artifacts are distributed - should probably be the first part that the working group should figure out. Also seeing that PSR5 and PSR19 are still in draft mode - when all they do is - by current standards - define attributes - is not very convincing to use a PSR or a PER for the process of providing a defied set of attributes for the masses...

OpenPGP_signature.asc
Description: OpenPGP digital signature