Ticket #48 (closed task: fixed)

Opened 9 years ago

Last modified 9 years ago

MOLES result

Reported by: sventour Owned by: sventour
Priority: blocker Milestone: V3.4 UML Final
Component: UML Information Model Version: V3.4
Keywords: Cc:

Description (last modified by domlowe) (diff)

Defining the concept of MOLES result and the classes to model it.

Change History

comment:1 Changed 9 years ago by lawrence

I think we agreed that it should either be an observation collection or an observation in some other application schema ...

comment:2 Changed 9 years ago by lawrence

Conclusion: We should leave this as any!

But this leaves us with the "linking" problem (ticket:15): how does a consumer of a moles instance know what to expect if it traverses this association?

comment:3 Changed 9 years ago by lawrence

  • Status changed from new to closed
  • Resolution set to fixed

So we solve this by creating a MO_Result class which consists of 1 to many CI_OnlineResources.

comment:4 Changed 9 years ago by lawrence

  • Status changed from closed to reopened
  • Resolution fixed deleted

(oops, decision made, close ticket when in UML)

comment:5 Changed 9 years ago by lawrence

Does this need an identifier, beyond the gml identifier (since it's a feature type). Clearly we want to have a register of projects ... but presumably the gml identifier is enough ...

comment:6 Changed 9 years ago by lawrence

Ok: so ensure we understand the distinction between gml:id and gml:Identifier (the latter is for external consumption, the former, internal). (A WFS might expose both: Dom to tell us ...)

comment:7 Changed 9 years ago by lawrence

  • Status changed from reopened to assigned

Got it: MD_Identifier can be used for someone else's identifier for this record. So we need one of those for James (so we had better have 0..* because there might be more than one identifier known for this project).

See the wiki page for other attribute suggestions. Needs implementatoin.

comment:8 Changed 9 years ago by domlowe

Notes on gml ident. types:

gml:id:

The attribute gml:id supports provision of a handle for the XML element representing a GML object. Its use is mandatory for all GML objects.

<attribute name="id" type="ID"/> 

It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. An external identifier for the XML element representing the GML object in the form of a URI may be constructed using standard methods (IETF RFC 2396). This is done by concatenating the URI for the document, a fragment
separator ―#‖, and the value of the attribute of XML type ID.

gml:identifier - Often, a special identifier is assigned to an object by the authority that maintains the feature with the intention that
it is used in references to the object. For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a predefined property for such identifiers.

WFS Usage
For WFS (& Filter Encoding) the feature identifiers used are the gml:id attributes

(Although there would be nothing to stop you filtering on the gml:identifer property in the same way you can filter on any property of a feature in WFS.)

comment:9 Changed 9 years ago by lawrence

The identifier is a red herring here. Leave it as agreed!

comment:10 Changed 9 years ago by lawrence

Looking at the candidate stuff, we like the specialistion of OM_Observatoin, with an associated MO_Result, which is a datatype not a feature type. Change to composition.
Done for next time?!!! Accept specialised codelists in 3.4, even if we want them outside later (get the INSPIRE pattern when it's finalised).

comment:11 Changed 9 years ago by domlowe

Added 'segment' - i.e. result can consist of sub results.

comment:12 Changed 9 years ago by domlowe

  • Description modified (diff)

remove [0...*] from aggregation end of segment association.

comment:13 Changed 9 years ago by sventour

regarding the composition : MO_Observation- MO_REsult
The result can be a coverage ( accessible by The MO_OnLinesource) and therefore it can stand alone. So, this composition could be an aggregation but this is a minor issue and leave it for the futue.

comment:14 Changed 9 years ago by lawrence

  • Status changed from assigned to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.
 Trac Powered
Site hosted at the
British Atmospheric Data Centre
for the