4 standards
A machine readable description an application publishes about itself: where it is deployed, which methods it exposes, and which registries name the protocols and baskets it uses.
Also searched as deployment-info.json, manifest, registry, ProtoMap, BasketMap, capability, metadata.
4 standards, spread across 4 of the 12 topics.
A tool that deploys an application needs to know its pieces, and every project describing that differently means the tooling only works on projects it was written for. This fixes the shape of that description file.
Filed under Applications
Manifests and deployment is the main subject of this one.
A tool that deploys an application needs to know its pieces, and every project describing that differently means the tooling only works on projects it was written for. This fixes the shape of that description file.
These are about something else, and deal with manifests and deployment on the way.
Deciding whether to trust a certificate means knowing which keys an organisation actually vouches with. This publishes that at the organisation's own domain, so it can be looked up the same way any other website detail is.
An application asking the user for one permission at a time, over and over, teaches them to click yes without reading. This lets an application declare everything it needs up front, in one place, so the user makes one informed decision.
If you know a domain runs some kind of overlay service, there was no standard place to find out where to actually send requests for it. You'd end up guessing at conventions like an api. subdomain, or asking around, with no way to be sure you weren't just hitting the wrong host. This gives a domain one clear file where it states, service by service, which URL to use.
Concepts that keep appearing on the same standards as this one.
Search standards by number, title, author or topic