First draft of BPMN Icon Extension #1
Conversation
This file contains 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
|
@barmac what do you think? |
|
@bastiankoerber does this help you? |
|
While the structure is clever, and XSD-compliant, the relationship does not seem to be the correct element for such extensions. So I'd classify this as a workaround. |
|
You are right: This is the least painful workaround that is possible with the current BPMN schema. However, it's also not completely outside the scope of relations. I have created a test case to ensure that SCE allows extension elements in it's top-level DI container and a future BPMN revision could adopt that in it's schema. |
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.
I tried to capture the discussion of today's meeting in an example and a design description. From here we could start an XML schema and specification text.