You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
The text was updated successfully, but these errors were encountered: