fairpm/fair-protocol
0
0
Fork 0
mirror of https://gh.wpcy.net/https://github.com/fairpm/fair-protocol.git synced 2026-06-19 02:14:01 +08:00
Code Issues Projects Packages Activity Actions
fair-protocol/registry.md
Joost de Valk 2b50184fca Merge origin/main into feature/separate-auth-entitlements 
Resolve conflicts:
- Spec: keep entitlement-aware install flow, FairEntitlementService DID section, entitlements property, auth narrowed to repository auth
- Metadata table: merge main's last_updated/latest-security-release rows with this branch's entitlements row
- Description: keep 250-char limit from this branch
- Normalize Client/Repository/Package capitalization to main's convention
2026-05-29 08:55:15 +02:00

2.7 KiB
Raw Permalink Blame History

Registry

This document is a registry for the known extensions to the FAIR Package Management Protocol, along with defined package and artifact types.

Extensions

Name Contact
FAIR Authentication Methods FAIR Working Group
FAIR for WordPress Packages FAIR Working Group
FAIR for TYPO3 Packages FAIR Working Group

Package Types

Type Extension Contact
wp-core FAIR for WordPress Packages FAIR Working Group
wp-plugin FAIR for WordPress Packages FAIR Working Group
wp-theme FAIR for WordPress Packages FAIR Working Group
typo3-core Reserved for future use. FAIR Working Group
typo3-extension FAIR for TYPO3 Packages FAIR Working Group
typo3-theme Reserved for future use. FAIR Working Group

Authentication Methods

Method Extension Contact
bearer FAIR Authentication Methods FAIR Working Group
basic FAIR Authentication Methods FAIR Working Group
oauth2 FAIR Authentication Methods FAIR Working Group

Entitlement Types

The "Typical proof lifetime" column is non-normative guidance for vendors choosing the JWT exp claim on entitlement proofs. Vendors MAY use any lifetime appropriate to their entitlement model; the spec does not impose a maximum.

Type Description Typical proof lifetime
subscription Active subscription required to access the package. Days to one billing cycle (e.g., 1–30 days)
purchase One-time purchase required to access the package. Long-lived (months); refresh on revocation only
license-key Valid license key required to access the package. Up to the licence's own expiry
free-registration Free to use, but requires registration with the vendor. Long-lived (weeks to a year)