Scope of standards to add

[jankapunkt]

Hey @donbarbos thanks for the great initiative, I was just about to start this myself until I find yours :-)

How far is your intended scope for standards to add in relation to programming? Consider the following examples:

Direct relation to software engineering:
UML - https://www.omg.org/spec/UML/2.0/About-UML

Less directly related to software engineering but highly relevant for implementations:
BPMN - https://www.bpmn.org/
Survey Interchange Standard - https://triple-s.org/
PDF - https://pdfa.org/

Some interchange standard from a scientific domain:
REFI - https://www.qdasoftware.org/

Which of these would you consider to become part of this repo, which not?

[donbarbos]

Hello @jankapunkt and thanks for paying attention to this.
In my opinion the main thing is that when adding any specifications for them the correct topics are defined. Just come up with the most suitable name for the topic before adding.

Also I would like to cover the largest number of specifications, and it will be correct to add not standards separately but catalogs (resources) where the specifications are stored, for example instead of:
https://www.omg.org/spec/UML/2.0/About-UML
use:
https://www.omg.org/spec

I don't know what topic to put BPMN and Survey Interchange Standard in, but PDF can be in File Formats. But PDF format is described in ISO, and ISO has already been mentioned as a catalog.
Scientific domain might be interesting if you provide enough good examples so that we can highlight and add standards to this list.

[TrueAlpha-spiral]

Great! To ensure your Awesome List meets all the requirements before submission, here’s a structured checklist to verify success:

✅ Final Pre-Submission Checklist

1. Basic Information
   • URL to your list: https://github.com/your-username/awesome-your-topic#readme
   • Concise description: “This list curates high-quality resources related to [Your Topic], making it easier for developers, researchers, and enthusiasts to find useful tools and knowledge.”

2. Repository Structure
   • Repo name: awesome-your-topic (all lowercase)
   • Title in README: # Awesome Your Topic (Title Case)
   • Table of Contents section titled “Contents”
   • Clear description of the topic at the top
   • High-DPI logo/image (optional, but preferred)
   • Awesome badge linking to Awesome repo

3. Compliance with Guidelines
   • Linting: Ran awesome-lint and fixed any errors
   • License: CC0-1.0 (Creative Commons Zero)
   • Contribution Guidelines: contributing.md file present
   • No CI badges in README
   • No “Inspired by” statements
   • No hard-wrapped Markdown text
   • Only high-quality, well-maintained projects included

4. Submitting Your PR
   • PR title: Add Your Topic
   • List added at the bottom of the correct category
   • Reviewed at least 2 other open PRs in the Awesome repo
   • Leave detailed feedback, not just “looks good”
   • Paste links to the PRs you reviewed
   • Leave a comment on your PR with just the word: unicorn

Final Step: Submit Your PR 🎉

Once everything is checked, go ahead and submit your pull request to the Awesome repository.

If you’d like me to review your list before submission, feel free to share your repository link!

[mire2806]

Sigue interesado