Jump to content

PHP Standard Recommendation

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by DrSchlagger (talk | contribs) at 11:49, 16 February 2016 (→Normal notability and citation guidelines do not apply here.: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

  • Comment: I'm not sure what to do with this one since it doesn't have third-party sources. Am asking at reviewer help. LaMona (talk) 15:40, 17 January 2016 (UTC)

The PHP Standard Recommendation (PSR) is a PHP specification published by the PHP Framework Interop Group. Similar to Java Specification Request for Java, it serves the standardisation of programming concepts in PHP. The aim is to enable interoperability of components and to provide a common technical basis for implementation of proven concepts for optimal programming and testing practices. The PHP-FIG is formed by several PHP frameworks founders.[1]

Each PSR is suggested by members and voted according to a established protocol [2] to act consistently and inline with their agreed upon processes.

Number Name Description Editor Coordinator Sponsor Status
PSR-0 Autoloading Standard It describes the mandatory requirements that must be adhered to for autoloader interoperability.[3] N/A N/A N/A Deprecated and substituted by PSR-4 [4]
PSR-1 Basic Coding Standard It comprises what should be considered the standard coding elements that are required to ensure a high level of technical interoperability between shared PHP code. [5] N/A N/A N/A Accepted [4]
PSR-2 Coding Style Guide It considers PSR-1 and it is intended to reduce cognitive friction when scanning code from different authors. It does so by enumerating a shared set of rules and expectations about how to format PHP code. [6] N/A N/A N/A Accepted [4]
PSR-3 Logger Interface It describes a common interface for logging libraries. [7] Jordi Boggiano N/A N/A Accepted [4]
PSR-4 Autoloading Standard It describes a specification for autoloading classes from file paths. It is fully interoperable, and can be used in addition to any other autoloading specification, including PSR-0. This PSR also describes where to place files that will be auto loaded according to the specification. [8] Paul M. Jones Phil Sturgeon Larry Garfield Accepted [4]
PSR-5 PHPDoc Standard The main purpose of this PSR is to provide a complete and formal definition of the PHPDoc standard. This PSR deviates from its predecessor, the de-facto PHPDoc Standard associated with phpDocumentor 1.x, to provide support for newer features in the PHP language and to address some of the shortcomings of its predecessor. [9] Mike van Riel Phil Sturgeon Donald Gilbert Draft [4]
PSR-6 Caching Interface The goal of this PSR is to allow developers to create cache-aware libraries that can be integrated into existing frameworks and systems without the need for custom development. [10] Larry Garfield Paul Dragoonis Robert Hafner Accepted [4]
PSR-7 HTTP Message Interface It describes common interfaces for representing HTTP messages as described in RFC 7230 and RFC 7231, and URIs for use with HTTP messages as described in RFC 3986. [11] Matthew Weier O'Phinney Beau Simensen Paul M. Jones Accepted [4]
PSR-8 Huggable Interface It establishes a common way for objects to express mutual appreciation and support by hugging. This allows objects to support each other in a constructive fashion, furthering cooperation between different PHP projects. [12] Larry Garfield Cal Evans Paul M. Jones Draft [4]
PSR-9 Security Disclosure It gives project leads a clearly defined approach to enabling end users to discover security disclosures using a clearly defined structured format for these disclosures. [13] Lukas Kahwe Smith Korvin Szanto Larry Garfield Draft [4]
PSR-10 Security Advisories It gives researchers, project leads, upstream project leads and end users a defined and structured process for disclosing security vulnerabilities. [14] Lukas Kahwe Smith Larry Garfield Korvin Szanto Draft [4]
PSR-11 Container Interface It describes a common interface for dependency injection containers. The goal is to standardize how frameworks and libraries make use of a container to obtain objects and parameters (called entries in the rest of this document). [15] Matthieu Napoli, David Négrier Paul M. Jones Jeremy Lindblom Draft [4]
PSR-12 Extended Coding Style Guide It extends, expands and replaces PSR-2, the coding style guide and requires adherance to PSR-1, the basic coding standard. [16] Michael Cullum Korvin Szanto Alexander Makarov Draft [4]

The PHP-FIG official website has the PSR documentation that follows the RFC 2119 written by Scott Bradner in March 1997 at Harvard University.

References

  1. ^ "PHP-FIG members list". PHP-FIG official website. Retrieved 10 January 2016.
  2. ^ "PHP-FIG voting protocol". PHP-FIG official website. Retrieved 10 January 2016.
  3. ^ "PSR-0: Autoloading Standard". PHP-FIG official website. Retrieved 10 January 2016.
  4. ^ a b c d e f g h i j k l m "PSR status list". PHP-FIG official website. Retrieved 10 January 2016.
  5. ^ "PSR-1: Basic Coding Standard". PHP-FIG official website. Retrieved 10 January 2016.
  6. ^ "PSR-2: Coding Style Guide". PHP-FIG official website. Retrieved 10 January 2016.
  7. ^ "PSR-3: Logger Interface". PHP-FIG official website. Retrieved 10 January 2016.
  8. ^ "PSR-4: Autoloading Standard". PHP-FIG official website. Retrieved 10 January 2016.
  9. ^ "PSR-5: PHPDoc Standard". PHP Documentor official git repository at Github. Retrieved 10 January 2016.
  10. ^ "PSR-6: Caching Interface". PHP-FIG official website. Retrieved 10 January 2016.
  11. ^ "PSR-7: HTTP Message Interface". PHP-FIG official website. Retrieved 10 January 2016.
  12. ^ "PSR-8: Huggable Interface". PHP-FIG official git repository at Github. Retrieved 10 January 2016.
  13. ^ "PSR-9: Security Disclosure". PHP-FIG official git repository at Github. Retrieved 10 January 2016.
  14. ^ "PSR-10: Security Advisories". PHP-FIG official git repository at Github. Retrieved 10 January 2016.
  15. ^ "PSR-11: Container Interface". PHP-FIG PSR-11 official git repository at Github. Retrieved 10 January 2016.
  16. ^ "PSR-12: Extended Coding Style Guide". PHP-FIG official git repository at Github. Retrieved 10 January 2016.

PHP Standard Recommendation

Normal notability and citation guidelines do not apply here.

PHP, is notable due to its ubiquity. This information is to specific and technical to add to the existing PHP article as it would be cumbersome. It is also important enough not to ignore. A standards body by definition is both authoritative and notable within their area of expertise as they control how that bit of technology is implemented in industry. If the IEEE puts out a new paper redefining the channel bands for 802.11X than that publication would be notable, and authoritative even if only the IEEE had it posted. DrSchlagger (talk) 11:49, 16 February 2016 (UTC)

(Don't let guidelines get in the way of good editing" -- Larry M. Sanger (co founder of Wikipedia)

Retrieved from "https://en.wikipedia.org/w/index.php?title=PHP_Standard_Recommendation&oldid=705252810"