Repository navigation
Define scoped semantic standards profile - #656
Merged
Merged
Conversation
Signed-off-by: transitrix <automation@transitrix.com>
transitrix
approved these changes
Oct 21, 2026
transitrix
left a comment
Owner
There was a problem hiding this comment.
Independent review of 2ee4190: no actionable findings. The scoped profile preserves existing authoring/tool contracts, declares deferred implementation choices, and keeps one authoritative mapping register. Documentation, example, compatibility and publication checks pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Adds Semantic Standards Profile 1.0 for explicitly declared authoring, interchange and tool-support scopes. It defines role/identity, namespace, provenance, validation, lifecycle and compatibility obligations with evaluation evidence, candidate dispositions and a worked example. Git/YAML authoring and existing tool schemas remain unchanged.
Establishes the existing ArchiMate differences register as the detailed comparison home with same-change maintenance, links the profile from documentation entry points, and qualifies introductory relation, Concern and equivalence wording. Concrete ontology, namespace implementation, service and exchange-engine choices remain separately scoped.
How it is verified
Checklist