search

Geonovum / uml2json

Best Practise for OGC - UML to JSON Encoding Rules
https://geonovum.github.io/uml2json/document.html
0 stars 1 forks source link

7.2 - pja - JSON encoding specific Tagged Values #9

Closed PalmJanssen closed 1 year ago

PalmJanssen commented 1 year ago

Table 3 shows that apparantly UML needs many JSON specific Tagged Values. This is quite a load for a UML application schema. How will that work? Should a EA profile for JSON be developed?

jechterhoff commented 1 year ago

In order to apply the tags in a UML 2 based model, stereotypes will have to be defined, and thus a UML profile. The question is whether we should go into more detail within the specification, or leave that as future work.

In fact, the UML profile would be what in Geospatial Data Modelling and Model-driven Transformation of Geospatial Data based on UML Profiles is called an encoding UML profile.

The way in which the UML profile should be defined, especially with respect to practicality, would need further work (and may be out-of-scope for this project). Defining multiple UML profile packages, for conceptual and specific encoding purposes, and merging them into a community profile as needed, using the package merge mechanism of UML, would be an interesting approach - but sadly does not seem to work in Sparx Systems Enterprise Architect (only modeling works out-of-the-box, but the actual merge seems to not directly be supported by EA).

PalmJanssen commented 1 year ago

agree