Repositories read with their docs
Intended use comes from the documentation a project publishes, not a guess from a function signature.
Repositories findable by what they do, read with their documentation attached, alongside the discussion threads that resolved the same error you're looking at.
Who issues them: International Organization for Standardization 59% · IETF 39% · World Wide Web Consortium 1%
Filing office: United States 42% · European Patent Office 24% · WIPO (PCT) 15%
Read from the running index when this page was served. Shares are of the records that declare the field, not of the whole shelf.
Intended use comes from the documentation a project publishes, not a guess from a function signature.
The accepted answer in a Q&A thread leads, rather than the longest reply.
Held alongside the repository, because it decides whether you can use it at all.
Roles read from the employer's own careers page, not an aggregator's altered copy.
Still deciding?
We'll walk the collections above and show what a question of yours returns.
Request accessActivity and licence are read as structured fields alongside the repository, so that question doesn't require opening the project yourself.
Code and Projects are live; Workflow is in beta and reads the same material as it ships.
Request private access and we'll walk the standards, repository, patent and thread shelves with you.
Browse the rest of the catalog at /apps.
Request access