Ticket #15 (closed issue: fixed)

Opened 11 years ago

Last modified 9 years ago

how do we implement outbound links?

Reported by: lawrence Owned by: domlowe
Priority: major Milestone: V3.4 UML Final
Component: UML Information Model Version: V3.4
Keywords: simonc Cc: domlowe, lawrence, sjdcox

Description

One of the key issues for MOLES is how it works as a "coathanger".

In Atom we have a defined (and typed link). We should probably
implement the same outbound link concept within MOLES.

Change History

comment:1 Changed 11 years ago by sjdcox

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

comment:2 Changed 11 years ago by lawrence

Note that I've created a utilities package and put some bumf in it. I'm sure it's rubbish, but hopefully that'll be an incentive to clean it up.

comment:3 Changed 11 years ago by sjdcox

In GML Annex E idiom, tagging a property inlineOrByReference='byReference' forces it to use links only.

In the XML implementation this results in the property element having type='gml:ReferenceType' which means that it uses xlinks.

Pretty much all of the functionality implied by the classes in your Utilities package can be accommodated by xlinks, perhaps with

  1. some additional guidance mapping the semantics to the xlink attributes, and
  2. some occurrence constraints to override the fact that by default all xlink attributes are use='optional'

comment:4 Changed 10 years ago by sjdcox

In particular xlink:role xlink:arcrole xlink:title

comment:5 Changed 10 years ago by sjdcox

I've put a constraint on the MOLES3 package to record the issue.

comment:6 Changed 10 years ago by sjdcox

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

comment:7 Changed 9 years ago by lawrence

  • Status changed from closed to reopened
  • Cc domlowe added
  • Type changed from task to issue
  • Version changed from V3.2 to V3.4
  • Milestone changed from V3.2 UML Final to V3.4 UML Final
  • Resolution fixed deleted

Actually, I think this is the same issue that is now being addressed for CSML and others by Dominic Lowe's work ... and so I'm not satisfied that it's adequately resolved. One obvious use case that I don't get is how we would indicate that an outbound citation is to a VIVO or a CERIF instance in the case of MO_Project

comment:8 Changed 9 years ago by lawrence

  • Owner changed from sjdcox to sventour
  • Cc lawrence, sjdcox added
  • Status changed from reopened to assigned

comment:9 Changed 9 years ago by lawrence

Just sent this (excerpt from an email) to a few folks:

We have outbound links which in metafor we are handling with CI_OnlineResource. Recall that CI_OnlineResource has the applicationprofile attribute available, with a rather poor definition of what it's for. "name of an application profile that can be used with the online resource".

I think we could for example have a codelist here that included:

  • geosciml
  • csml
  • vivo
  • cerif

etc ...

Or URIs to descriptions of those things or ,

Then, where a moles class wants to point out to a better more complete discussion of something, then the appropriate attribute would have a ci_onlineresource and the instances would say what sort of resource it was via the applicationProfile.

comment:10 Changed 9 years ago by lawrence

So do we need, however, to specialise or constrain CI_OnlineResource so the appplication profile is constrained to a codelist (controlled vocabulary).

Similarly, we might want to consider extending the CI_OnlineFunctionCode codelist, so that we have something like

  • app profile - image; function - WMS;
  • app profile - netcdf; function - WCS;
  • app profile - rdf; function - ?
  • app profile - skos; function - vocab server ...

comment:11 Changed 9 years ago by lawrence

  • Owner changed from sventour to domlowe

comment:12 Changed 9 years ago by lawrence

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

We currently have a MO_OnlineResource specialisation of CI_OnlineResource.

Note: See TracTickets for help on using tickets.
 Trac Powered
Site hosted at the
British Atmospheric Data Centre
for the