Closed KonradHoeffner closed 3 years ago
This seems to be a part of 3LGM²:
[...] 3LGM². With the tool we provide a so called reference model for the domain layer. This model contains all hospital functions and all entity types mentioned in the book (and some more).
Can be downloaded from https://www.3lgm2.de/Referenzmodelle_und_Beispielmodelle/ at https://www.3lgm2.de/Referenzmodelle_und_Beispielmodelle/RM_DomainLayer_version2_English.z3lgm and viewed in the 3LGM² tool.
Given that this is a structured file format that contains a lot of information, a transformation script from 3LGM² to HITO catalogues would make sense here. Then a new version of the reference model could also be updated quickly. Investigate how difficult it is to access this file format. If it turns out to be too difficult, an alternative approach is to git clone the 3LGM² Tool source code and create the mapping in Java based on that source code.
OK, .z3lgm is just a compressed .3lgm file, and that is an XML file. Now the question is only, how accessible is the XML structure.
<element class="Aufgabe" hash="AUF_1067173903876_219">
<field name="layer">4</field>
<field name="name">Appointment scheduling</field>
<field name="description">
Appointment scheduling: The hospital must be able to schedule an appointment for a patient´s visit. [...]
</field>
</element>
class="Aufgabe"
identifies a function, the hash could be the suffix of the URI, the name becomes the label and the description maps to rdf:comment. Layer 4 seems to be the domain layer that we need.
@SebStaeubert: Just tagging you here in case I am way off base or if you have some advice.
Now I just need to find out, how subclasses are encoded.
I asked @FranziskaJahn and she told me that this is not necessary anymore because the already existing blue book catalogue is modeled after the 3LGM² reference model for the domain layer. However if in the future any 3LGM² Tool file should be converted to HITO, we could continue this direction.
Notes from meeting, can anyone clarify?