Ticket #577 (closed issue: fixed)

Opened 13 years ago

Last modified 13 years ago

[M] Michael Hughes leaving BODC

Reported by: selatham Owned by: selatham
Priority: critical Milestone: ReFactored_Discovery_WebServices
Component: vocab Version:
Keywords: Cc:

Description (last modified by selatham) (diff)

Who will cover vocab WS work? Following Roy's comments the outstanding issue here seems to be that some effort is required elsewhere in NDG group:-

*One problem is the building of a mapping between BODC's relational schema and the MMI OWL schema that will form the specification for part of the Term Server infrastructure specification. Help from eleswehere in NDG would be appreciated here.

Change History

comment:1 Changed 13 years ago by rkl

Michael is leaving on January 5th and between now and then his first priority will be ensuring that everything he's done is properly documented so it can be picked up cleanly by whoever takes it over.

As far as NDG is concerned, the threat is to the Vocabulary Server code maintenance and API development and the production of the Term Server. Most of this can be handled within BODC, with these projects reassigned to Siva with help from other Java developers in the group if required. One problem is the building of a mapping between BODC's relational schema and the MMI OWL schema that will form the specification for part of the Term Server infrastructure specification. Help from eleswehere in NDG would be appreciated here.

comment:2 Changed 13 years ago by selatham

  • Owner changed from rkl to selatham
  • Description modified (diff)

comment:3 Changed 13 years ago by rkl

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

OWL mapping has been done by Michael and myself. We've also decided to build the term server on the relational version of the map rather than implement Luis Bermudez's code (has anybody else looked at Luis's output - it's daunting to say the least).

I've been able to obtain some additional Java programming resource within BODC so I now think we're OK.

Note: See TracTickets for help on using tickets.