Prolog Improvement Proposals (PIPs)_ describe important extensions to Prolog that are not included in the Prolog ISO standards. These extensions may affect the Prolog language itself or they may be implemented as libraries or packages.
While PIPs describe important functionality, they are not standards. Rather they are intended to describe functionality implemented in current Prologs rather than to prescribe what all Prologs should do. Each PIP must be supported by at least two Prolog systems. We hope that this requirement will help to foster coordination between Prologs in developing new functionality, and in providing common APIs to existing functionality. Of course if a PIP is widely adopted by the Prolog community there is nothing to prevent it from being further developed into a standard by the appropriate working groups.
For questions about PIPs, see this FAQ.
For guidelines, see PIP-0001
These are the current PIPs:
| PIP # | Title | Status | Location (temporary) | |
|---|---|---|---|---|
| 0001 | What is a PIP? | Draft | https://gitlab.software.imdea.org/prolog-lang/implementors-forum | |
| 0100 | JSON to and from Prolog | Draft | https://gitlab.software.imdea.org/prolog-lang/pip-janus | |
| 0101 | Communication between Prolog and Python via Janus | Draft | https://gitlab.software.imdea.org/prolog-lang/pip-json | |
| 0102 | Dictionaries in Prolog | Draft | https://gitlab.software.imdea.org/prolog-lang/pip-janus | |
| 0103 | Modes | Draft |