Skip to content

Add registries/_extension/x-fdx-csdf-account-categories.md#106

Open
DavidBiesack wants to merge 2 commits into
OAI:mainfrom
DavidBiesack:docs/add-extention-x-fdx-csdf-account-categories
Open

Add registries/_extension/x-fdx-csdf-account-categories.md#106
DavidBiesack wants to merge 2 commits into
OAI:mainfrom
DavidBiesack:docs/add-extention-x-fdx-csdf-account-categories

Conversation

@DavidBiesack

Copy link
Copy Markdown
Contributor

Add entries to .gitignore:

  • Editor files (*.bak, *~)
  • MacOS .DS_Store directory metadata

Add entries to `.gitignore`:

* Editor files (`*.bak`, `*~`)
* MacOS `.DS_Store` directory metadata
@DavidBiesack DavidBiesack requested review from a team as code owners July 3, 2026 13:52

@baywet baywet left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution!

---

{% capture summary %}
The `x-fdx-csdf-account-categories` extension is used to tag API elements

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since there's already a namespace registration for those extensions, I suggest you setup a public repository under that organization, and manage the extensions there for clarity. Kind of like Microsoft and other namespaces are doing.
https://spec.openapis.org/registry/namespace/fdx.html

https://github.com/microsoft/OpenAPI/blob/main/extensions/index.md
https://guides.scalar.com/scalar/scalar-api-references/openapi#openapi-specification__custom-specification-extensions

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@baywet
Such recommendations are not in CONTRIBUTING.md - should we add them there (with examples, i.e. where x-ms is listed in the namespace registry), and perhaps the doc on the main registries page which just says:

Contributing
Please raise a Pull-Request and follow the instructions in CONTRIBUTING.md, or open an Issue to contribute or discuss a registry value.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@baywet @DavidBiesack we should definitely do something here- I somehow had no idea that the namespace registry linked to the extensions in the namespace, although that makes perfect sense to avoid drift.

@DavidBiesack you can decide how much of this you do or don't want to take on, but I think we need:

  • The main Registries page to explain this (easiest option would be in its own paragraph beneath the current one)
  • The Extension Field Registry / Extensions Registry (we should make the heading on the page match the heading in the list on the Registries page while we're at it) should link to the namespace registry, noting that more extensions can be found there
  • A "Repository" or "3rd-Party Registry" or something column in the Namespace Registry table between the "Prefix" and "Description" columns
  • Updated guidance in the spec repo's CONTRIBUTING documentation

@DavidBiesack whatever you don't want to take on, feel free to open an issue with the remaining bullet points (even all of them- I'd rather get this merged than get it hung up on longer-term work), or let us know and either @baywet or I can file it.

Comment thread .gitignore Outdated
node_modules/
scripts/
package-lock.json
.DS_Store

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add your own platform-specific exclusions to your global gitignore configuration, do not include them here.

@DavidBiesack

Copy link
Copy Markdown
Contributor Author

Thanks @handrews
I submitted #108 for you and others to tackle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants