Hello. I am new to the BPMN-JS community and would like to make a feature request.
I am interested in enabling end-users to be able to create and edit extensible metadata for diagrams, nodes, and connectors, using, for example, JSON-LD.
With respect to UX topics for adding extensible metadata to diagrams, there could be a menu option for users to view and edit a text resource associated with the diagram.
As considered, end-users creating or editing structured-knowledge annotations for diagrams would need URIs for those diagrams. In theory, a special URI could be utilized for these purposes, e.g., this:diagram
, and the JSON-LD resource could be later transformed, as needed.
{
"@context": "https://www.example.org/schema.json",
"@id": "this:diagram",
"authoredBy": "Bob Smith",
"dateCreated": "2024-12-14"
}
With respect to UX topics for adding extensible metadata to nodes and connectors, this could resemble adding a text annotation to them but utilizing JSON-LD instead of natural-language text.
As considered, a node or connector would need a unique ID or URI to be provided to the end-user. In theory, special URIs could be used, e.g., this:node
and this:connector
, and JSON-LD resources could be later transformed, as needed.
{
"@context": "https://www.example.org/schema.json",
"@id": "this:node",
"estimatedDuration": "30m"
}
For scenarios where all end-users aren’t desired to enter JSON-LD, other possibilities include that developers or other advanced users could simply specify a schema or ontology (e.g., by URL) for a diagram, node, or connector type such that end-users would be able to make use of an extensible “property grid” widget, automatically populated using that schema or ontology, to visually interact with a set of properties and values for the diagram, node, or connector.
I am interested in enabling extensible metadata and how this could be stored into and loaded from BPMN 2.0 files as well as Semantic Web formats, e.g., utilizing the BPMN-Based Ontology (BBO).
While, visually, editable metadata could surface as JSON-LD annotations, metadata might be stored differently in BPMN 2.0 files.
Thank you.