Skip to content

docs: add missing period for consistency in App Directory compliance list #1741

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
AtharvaKathe18 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: add missing period for consistency in App Directory compliance list #1741

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fcadc60
docs: fix incorrect term 'schema' to 'scheme' for Bearer authentication
AtharvaKathe18 Jan 28, 2026
e2cdcf7
docs: add missing period for consistency in App Directory compliance …
AtharvaKathe18 Jan 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions website/docs/app-directory/spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,12 +32,12 @@ An FDC3 Standard compliant App Directory implementation **MUST**:
- `/v2/apps` (GET)
- `/v2/apps/{appId}` (GET)
- Ensure that `appId` field values assigned to applications are unique within the directory.
- Ensure that app directory records served meet the minimum requirements specified in the [app directory OpenAPI specification](pathname:///schemas/next/app-directory.html#tag/Application)
- Ensure that app directory records served meet the minimum requirements specified in the [app directory OpenAPI specification](pathname:///schemas/next/app-directory.html#tag/Application).
- Support retrieval of app directory records via either the raw `appId` (e.g. `myAppId`) or fully-qualified appId (e.g. `myAppId@host.domain.com`) as defined in the [app directory overview](overview#shrinking-the-uri).

An FDC3 Standard compliant App Directory implementation **SHOULD**:

- Support authentication (where required) via the HTTP Authorization header and Bearer authentication schema (implemented via JWT tokens)
- Support authentication (where required) via the HTTP Authorization header and Bearer authentication scheme (implemented via JWT tokens)
- Select any `categories` field values from the recommended list.
- Encourage the use of the `lang` and `localizedVersions` fields in appD records to support localization and accessibility.

Expand Down
Loading