Ticket #2 (accepted task)

Opened 11 years ago

Last modified 10 years ago

Identify and tag suitably within the UML, independently referenceable objects

Reported by: lawrence Owned by: lawrence
Priority: major Milestone: V3 Atom Serialisation
Component: UML Information Model Version: V3.2
Keywords: simonc Cc:

Description (last modified by lawrence) (diff)

This is about working out what objects could to be serialised into atom ... and which are likely to be created by individuals at different times, and which could be created and served from different governance domains. It could be done either by a specific stereotype, or by a specialisation of gml feature type, or simply by agreeing that all gml feature instances should be independently managed.

This is marked in the top level NDG3 plan as part of the UML deliverable.

Change History

comment:1 Changed 11 years ago by lawrence

  • Version set to V3.2
  • Description modified (diff)

comment:2 Changed 11 years ago by sjdcox

  • Summary changed from Identify and tag suitably within the UML, independantly referencable objects to Identify and tag suitably within the UML, independently referenceable objects

comment:3 Changed 11 years ago by lawrence

  • Owner changed from Simon Cox to lawrence
  • Status changed from new to accepted

comment:4 Changed 11 years ago by lawrence

Documents will come from the following:

  • projects
    • grants within projects (subprojects)
  • observations
    • we imagine getting via some "processor" running on "data", e.g. granulite or csml?
    • what extra metadata?
      • phenomena
  • deployments within projects
    • instruments
    • algorithms
    • can use the same deployment subsequently with different algorithms as part of a different project, or the same project
      • what are the implications for that?
  • new virtual observation collections
  • existing virtual observation collections need updating to aggregate the newly acquired observation collection.

comment:5 Changed 11 years ago by lawrence

So now the issue is how to tag things.

  1. mark classes with a document stereotype ...
  2. work out what that stereotype means
    1. expect it to specialise feature type
    2. carry authorship
    3. carry an abstract
    4. carry an id (from feature type)
    5. be discoverable as a document, and transportable as document (possibly with the payload as a link a la atom)

comment:6 Changed 11 years ago by sjdcox

  1. Only the standard (GML/INSPIRE) stereotypes are recognized by FullMoon?.
  2. However, in the case the stereotype is a shorthand for inheriting some standard properties. So you can do this explicitly instead - i.e. create a 'Document' class and make it the parent of all the classes that you want to "stereotype" this way.
  3. However, you will probably hit multiple-inheritance, so you may have to use an association to the 'standard' properties (rather than a specialization). In which case the standard properties should be stereotyped <<DataType?>> to force them to be local.

comment:7 Changed 10 years ago by lawrence

  • Milestone changed from V3.2 UML Final to V3.2 XSD Serialisation

comment:8 Changed 10 years ago by lawrence

  • Milestone changed from V3.2 XSD Serialisation to V3 Atom Serialisation
Note: See TracTickets for help on using tickets.
 Trac Powered
Site hosted at the
British Atmospheric Data Centre
for the