Ticket #120 (closed issue: wontfix)

Opened 13 years ago

Last modified 12 years ago

[M] Service Binding

Reported by: selatham Owned by: lawrence
Priority: critical Milestone: MeetingsJan2007
Component: MOLES Version:
Keywords: AHMJan2007 Cc:

Description (last modified by lawrence) (diff)

When a DIF document is produced and loaded for harvest, how do we ensure that the CSML URI points to an existing CSML doc, or if no CSML, what services should be provided for a given dataset. Similarly for the browse links to other entities.

Change History

comment:1 Changed 13 years ago by selatham

Currently - Instructions in MOLES guide re. what will feed through to DIF and be understood by NDG Discovery. This is an NDG discovery only solution to service definition.

comment:2 Changed 13 years ago by selatham

Does ISO have anything to say on service definition (or OGSA?)

comment:3 Changed 13 years ago by domlowe

  • Status changed from new to assigned

comment:4 Changed 13 years ago by lawrence

  • Milestone changed from ALPHA to BETA

Need to look at the ISO19119 (and ISO19139) documentation as well

comment:5 Changed 13 years ago by lawrence

  • Status changed from assigned to new
  • Description modified (diff)
  • Component changed from T10_Working_Grid to T07_MOLES
  • Summary changed from Discovery metadata links to Data services to [M] Service Binding
  • Owner changed from domlowe to lawrence
  • Milestone changed from BETA to PreBeta
  • Keywords MOLES_Schema added

This applies to browse content as well, and the resolution will affect ticket:130 which is about how the gui handles the information.

comment:6 Changed 13 years ago by lawrence

  • Type changed from issue to task

comment:7 Changed 13 years ago by selatham

Regarding Services the GCMD DIF GCMD URL Content Type Keywords latest list includes:-

ACCESS MAP VIEWER ACCESS WEB SERVICE GET DATA > ECHO GET DATA > EDG GET DATA > EOSDIS DATA POOL GET DATA > GIOVANNI GET DATA > LAADS GET DATA > LAS GET DATA > MIRADOR GET DATA > MODAPS GET DATA > NOMADS GET DATA > OPENDAP DATA (DODS) GET DATA > OPENDAP DIRECTORY (DODS) GET DATA > THREDDS CATALOG GET DATA > THREDDS DATA GET DATA > THREDDS DIRECTORY GET DATA > WHOM GET DATA > WIST GET DATA GET MAP SERVICE GET RELATED DATA SET METADATA (DIF) GET RELATED SERVICE METADATA (SERF) GET SERVICE GET SOFTWARE PACKAGE GET WEB COVERAGE SERVICE (WCS) GET WEB FEATURE SERVICE (WFS) GET WEB MAP SERVICE (WMS) VIEW EXTENDED METADATA VIEW PROJECT HOME PAGE VIEW RELATED INFORMATION

comment:8 Changed 13 years ago by lawrence

  • Status changed from new to assigned

comment:9 Changed 13 years ago by selatham

  • Cc mggr removed
  • Priority changed from required to critical

What depends on Service Binding? Are we talking about all NDG services. We need a convention for NDG services? How do we handle others?

comment:10 Changed 12 years ago by selatham

  • Keywords AHMJan2007 added; MOLES_Schema removed
  • Type changed from task to issue
  • Milestone changed from PreBeta to MeetingsJan2007

Ag said:-

I believe this issue to be about:

  1. URIs that point to an NDG resource/service/dataset/file:

My example is that a user points the BADC geosplat at a file at PML, something like:

 http://badc.nerc.ac.uk/cgi-bin/splatui?fileURIList=http://www.pml.ac.uk/ndg/services/datasets_wrapped/europe-8bit-1999010100

This requires geosplat/user to know what the URI of the particular service that can deliver the dataset/file is. In reality, this service needs to have NDG-security built in so it could do methods such as (i) getAuthRoles() and (ii) getFile(secureToken).

These authentication/delivery services might need to be centrally lodged with a simple NDG core service such as:

http://ndg.nerc.ac.uk/services/resolve_service?URI=SomeObscureURIThatNeedsMapping

This would return the service binding and the mapped URI.

  1. The arguments that can be passed to any given service:

Such as telling the data extractor the bounding box and date/time window you are interested in on invocation.

Am I on the right track? If so, can we split these things up into:

  1. Resolving URIs to NDG resources.

and

  1. Service Bindings - arguments that can be passed to NDG-resources.

comment:11 Changed 12 years ago by lawrence

OK, so current thinking is now moved to the ServiceBinding wiki page.

comment:12 Changed 12 years ago by lawrence

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

I think we've decided to finess this all for NDG ...

Note: See TracTickets for help on using tickets.