{"id":353,"date":"2024-03-01T15:54:15","date_gmt":"2024-03-01T14:54:15","guid":{"rendered":"http:\/\/localhost\/?page_id=353"},"modified":"2024-09-17T08:28:18","modified_gmt":"2024-09-17T06:28:18","slug":"from-transmodel-to-data-file","status":"publish","type":"page","link":"https:\/\/transmodel-cen.eu\/index.php\/from-transmodel-to-data-file\/","title":{"rendered":"From Transmodel to data file"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

From Transmodel to data file<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Models may exist at different levels of abstraction.\u00a0<\/p>

  • Conceptual Model <\/b>\u2013 A high level implementation neutral representation. A conceptual model describes the elements and relationships of a model independently of any specific implementation technology. It can be used to understand and relate different implementations using many different technologies and physical models.\u00a0<\/li>
  • Physical Model <\/b>\u2013 A design for implementing the Conceptual model using a specific technology. A physical model maps a conceptual model into a more detailed model that assumes a specific implementation technology, subject to particular constraints of that technology. In general a physical model will have more limited semantics than a conceptual model because of the constraints of the chosen implementation language and of the need to simplify the use of a rich conceptual model for any practical implementation. A physical model is still however not usually an executable or completely finalised representation, but rather a translation tool that shows how to go from a very high level technology-independent conceptual model to a concrete implementation in a specific language.\u00a0<\/li>

  • Implementation Model\u00a0<\/b>\u2013 An implementation of the model in a specific language that supports declarative modelling constructs. An implementation model represents a physical model in the actual language constructs and types of an implementation language, such as a DDL (Data Definition Language) for a database or an XML (Extensible Markup Language)\u00a0 schema for an exchange format. It is directly executable using tools or programs. NeTEx uses W3C XML schemas for this purpose, but in principle other languages could be chosen in future.<\/p><\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

    \n\t\t\t\t\t
    \n\t\t
    \n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
    \n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t
    \n\t\t\t
    \n\t\t\t<\/path><\/svg>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
    \n\t\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    From conceptual to physical model<\/em><\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    From a data model in UML to a data exchange format in XML\u00a0<\/b><\/p>

    UML<\/b> (Unified Modelling Language) provides a formalism to represent data structures. It may be used at conceptual or physical level.<\/p>

    XML<\/b> (Extensible Markup Language) provides, using specific transformation rules, a serialisation of data initially defined in the conceptual\/physical models.\u00a0 In other words: the application of specific transformation rules to the physical model, provides an XML file dedicated to data exchanges (XML data exchange format).<\/p>

    The transformation rules are in detail described in the NeTEx-Part 1 document.<\/p>

    The following example (described in detail in NeTEx-Part 1) shows the dififierent steps:<\/p>

        • a conceptual model, represented in UML (using Transmodel conventions),<\/li>
        • a corresponding physical model and<\/li>
        • a corresponding XML file.<\/li><\/ul><\/li><\/ul><\/li><\/ul>

          Conceptual level\u00a0<\/b><\/p>

          The THING conceptual model: an entity called THING may be classified by TYPE OF THING and grouped with GROUP of THINGs. Each THING can be made up of one or more CHILD THINGs. A THING can be associated with many SOMETHING ELSEs. The entities together make up a THING conceptual model.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

          \n\t\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
          \n\t\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t

          Physical level<\/b><\/p>

          The THING physical model is obtained as follows:<\/p>

              • the names of the entities are spelled in line with XML naming conventions: \u2018THING\u2019 becomes \u2018Thing\u2019, \u2018SOMETHING ELSE\u2019 becomes \u2018SomethingElse<\/b>\u2019, \u2018TYPE OF THING\u2019 becomes \u2018TypeOfThing<\/b>\u2019.<\/li>
              • all model Elements are made specializations of the DataManagedObject<\/b> or other more specific supertype. For example,\u00a0TypeOfThing<\/b> is a specialisation of TypeOfValue<\/b>; GroupOfThings<\/b> is a specialisation of GroupOfEntities<\/b><\/li><\/ul><\/li><\/ul><\/li><\/ul>

                NB.Several types of presentations of a UML model may be provided. The figure below is called “Thing Model Concise” without visualising all details, showing for example only the name of the parent classes in the upper right corner (without showing their attributes).<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

                \n\t\t\t\t\t
                \n\t\t\t\t
                \n\t\t\t\t
                \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                \n\t\t\t\t\t
                \n\t\t\t\t
                \n\t\t\t\t
                \n\t\t\t\t\t\t\t\t\t

                Implementation level<\/strong><\/p>

                XSD language (XML Schema Definition Language) is the current standard schema language for all XML documents and data. XSD specifies how to formally describe the elements in an Extensible Markup Language (XML) document.<\/p>

                Below the initial THING model is represented using the XSD formalism.<\/strong><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

                \n\t\t\t\t\t
                \n\t\t\t\t
                \n\t\t\t\t
                \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                \n\t\t\t\t\t
                \n\t\t\t\t
                \n\t\t\t\t
                \n\t\t\t\t\t\t\t\t\t

                The rules for the transformation to get an XML file (for example how to represent relationships, inheritance, etc) are described in detail in the NeTEx-Part 1 documentation.<\/p>

                The following XML fragment<\/strong> shows a sample instance of a Thing<\/strong> (i.e. an object of the class Thing) containing two ChildThing<\/strong> instances and classified with a TypeOfThing<\/strong> instance. It has a parent \u2018abc:43262<\/i>\u2019 and is associated with three other instances of SomethingElse<\/strong> elements.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

                \n\t\t\t\t\t
                \n\t\t\t\t
                \n\t\t\t\t
                \n\t\t\t\t\t\t\t\t\t

                <<\/span><\/span>Thing<\/span><\/span> id<\/span><\/span>=”<\/span><\/span>abc:3456<\/span><\/span>“<\/span><\/span> version<\/span><\/span>=”<\/span><\/span>001<\/span><\/span>“><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <<\/span><\/span>Name<\/span><\/span> lang<\/span><\/span>=”<\/span><\/span>en<\/span><\/span>“><\/span><\/span>Lunch<\/span><\/span><\/<\/span><\/span>Thing<\/span><\/span>><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <<\/span><\/span>ThingType<\/span><\/span>>nextB<\/span><\/span>ig<\/span><\/span><\/<\/span><\/span>ThingType<\/span><\/span>><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <TypeOf<\/span><\/span>ThingRef<\/span><\/span> ref<\/span><\/span>=<\/span><\/span>\u201dabc:Val01\u201d version<\/span><\/span>=<\/span><\/span>\u201dany\u201d<\/span><\/span>\/><\/span><\/span>\u00a0<\/span><\/p><\/div>

                \u00a0<\/span><\/span><ParentThing<\/span><\/span>Ref<\/span><\/span> ref<\/span><\/span>=<\/span><\/span>\u201dabc:43262\u201d version<\/span><\/span>=<\/span><\/span>\u201dany\u201d<\/span><\/span>\/><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <<\/span><\/span>ThingProperty2<\/span><\/span>><\/span><\/span>bar<\/span><\/span><\/<\/span><\/span>ThingProperty2<\/span><\/span>><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <<\/span><\/span>children<\/span><\/span>><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <<\/span><\/span>ChildThing<\/span><\/span> id<\/span><\/span>=”<\/span><\/span>abc:34561<\/span><\/span>“><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <<\/span><\/span>IsCool<\/span><\/span>><\/span><\/span>true<\/span><\/span><\/<\/span><\/span>IsCool<\/span><\/span>><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <\/<\/span><\/span>ChildThing<\/span><\/span>><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <<\/span><\/span>ChildThing<\/span><\/span> id<\/span><\/span>=”<\/span><\/span> abc: 34562<\/span><\/span>“><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <<\/span><\/span>IsCool<\/span><\/span>><\/span><\/span>false<\/span><\/span><\/<\/span><\/span>IsCool<\/span><\/span>><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <\/<\/span><\/span>ChildThing<\/span><\/span>><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <\/<\/span><\/span>children<\/span><\/span>><\/span><\/span>\u00a0<\/span><\/p><\/div>

                \u00a0<\/span><\/span><<\/span><\/span>somethingsElse<\/span><\/span>><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <S<\/span><\/span>omethingElse<\/span><\/span> ref<\/span><\/span>=”<\/span><\/span>abc:66561<\/span><\/span>” ><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <S<\/span><\/span>omethingElse<\/span><\/span> ref<\/span><\/span>=”<\/span><\/span>abc:68752<\/span><\/span>” ><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <S<\/span><\/span>omethingElse<\/span><\/span> ref<\/span><\/span>=”<\/span><\/span>abc:21756<\/span><\/span>” ><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <\/<\/span><\/span>somethingsElse<\/span><\/span> ><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <\/<\/span><\/span>Thing<\/span><\/span>><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <<\/span><\/span>TypeOfThing<\/span><\/span> id<\/span><\/span>=”<\/span><\/span> abc:Val01<\/span><\/span>“<\/span><\/span> version<\/span><\/span>=”<\/span><\/span>any<\/span><\/span>“><\/span><\/span>\u00a0<\/span><\/p><\/div>

                <<\/span><\/span>Name<\/span><\/span> lang<\/span><\/span>=”<\/span><\/span>en<\/span><\/span>“><\/span><\/span>Good Thing<\/span><\/span><\/<\/span><\/span>Thing<\/span><\/span>><\/span><\/span>\u00a0<\/span><\/span>\u00a0<\/span><\/p><\/div>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

                From Transmodel to data file Models may exist at different levels of abstraction.\u00a0 Conceptual Model \u2013 A high level implementation neutral representation. A conceptual model describes the elements and relationships of a model independently of any specific implementation technology. It can be used to understand and relate different implementations using many different technologies and physical […]<\/p>\n","protected":false},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-353","page","type-page","status-publish","hentry","entry"],"_links":{"self":[{"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/pages\/353","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/comments?post=353"}],"version-history":[{"count":35,"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/pages\/353\/revisions"}],"predecessor-version":[{"id":3115,"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/pages\/353\/revisions\/3115"}],"wp:attachment":[{"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/media?parent=353"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}