"Seegrid will be due for a migration to confluence on the 1st of August. Any update on or after the 1st of August will NOT be migrated"

Publishing model packages so others can use them


Related pages

Reusability of Application Schemas

Application Schemas may be created for a specific operational application, but the whole concept of using a standards-oriented approach is predicated on a specific community of practice defining elements of an information model to support interoperability. By extension, such models should be broken down into cleanly separated "packages" specific to the community of interest, and importing models from other domains where possible.

In turn, this leads to consideration of how a domain model should be published to support re-use by client applications.

Publishing an Application Schema within the HollowWorld framework

Artefacts Required

  • UML model (normative) - XMI file containing published package - this should be published using a subversion repository so it can be loaded as a read-only artefact (see HollowWorld)
  • .EAP "workbench" - this should be made available to assist the loading of dependencies, since otherwise it may be required to load a large number of packages manually
  • GML Application schemas (FullMoon output) - this is the artefact needed by most implementers
  • Generated documentation
  • FulllMoon configurations for the package ready to use by client applications (see ExternalDependencyConfiguration)

Using a model or schema from outside the HollowWorld framework

If you wish to import an external resource, such as an XML-schema, for re-use within the HollowWorld Framework, then you should publish the FullMoon configuration files. (Exactly where is an issue for registry solutions to model management, an issue for the future)

Topic revision: r7 - 15 Oct 2010, UnknownUser

Current license: All material on this collaboration platform is licensed under a Creative Commons Attribution 3.0 Australia Licence (CC BY 3.0).