The attributes marked with a * are confidential and should not be disclosed outside the service provider.

Service overview
Service nameOpen Information Linking for Environmental science research infrastructures (OIL-E)
Service areadata
Service phase

alpha

Service descriptionOIL-E is a developing framework for addressing the semantic linking requirements of environmental science e-RIs. Specifically, it is intended to provide a machine-readable bridge between the ENVRI Reference Model and other concept models related to research infrastructure, architecture and scientific (meta)data.

Customer group

RI data engineers/architects
User groupData-driven researchers
ValueOIL-E is intended to provide technical and methodological guidance for the linking of different controlled vocabularies in order to help the construction of cross-cutting services.
TaglineOpen linking between environmental science RI reference modelling and controlled vocabularies.
Features
  • Captures ENVRI RM as a multi-viewpoint OWL ontology for RI architecture.
  • Permits analysis and comparison of RI characteristics as the foundation for an ENVRI Knowledge Base.
  • Provides a linking framework for describing the different metadata schemes and technologies used by RIs as well as to identify any semantic mappings available to convert between schemes.
Service options
OptionNameDescriptionAttributes
1Add a name for this option Add a description for this option; this description is targeted to potential customers who need to understand what each option is about and being able to choose the best for their needs Add attributes as numbered bullet lists in the form of 1. attribute name: [possible values] 2. attribute name: [possible values]  ... 
2



3



Access policiesWide access
Service management information
Service owner *Paul Martin
Contact (internal) *p.w.martin@uva.nl
Contact (public)External contact (e.g., e-mail, phone) to ask information about the service
Request workflow *

Service request list
Terms of useURL to a document containing the rules which one must agree to abide by in order to use the service
SLA(s)Link to URL to a document containing information about the levels of performance that a service provider is expected to achieve (service level agreement)
Other agreementsList of agreement documents that are associated to this services (e.g. OLA, UA)
Support unit

email support: Paul Martin (p.w.martin@uva.nl), Zhiming Zhao (z.zhao@uva.nl)

open for new test data and test queries

User manualonline accessible documentation via http://www.oil-e.net/.
Service architecture
Service components

TRL3–4，development on-going.

#TypeNameDescriptionTRL [1]
1

Choose: Enabling or Enhancing

Definitions:

- Enabling service components are the minimum set of service components that make the service available

- Enhancing service components are any additional service components that improves the service, however, the service would still run without them, even if at lesser quality.  

 Name of the component

2



Finances & resources
Payment model(s)Free
PricingDescribe the price scheme for this service in case the customer is charged for access/usage
Cost *

The sustainability of the ENVRI RM ontology in OIL-E is partially tied to the sustainability of ENVRI RM itself.
Application of OIL-E, e.g. for the ENVRI Knowledge Base, creates a community of use for ontologies.
Publication of OIL-E in ontology repositories also increases exposure and provides limited curation tied to lifespan of repository.

Revenue stream(s) *e.g. public funding, membership fees, in-kind, paid (specify price)
Action requiredList the actions that are required to complete the service portfolio entry according to the specific service phase; if no actions are required, write 'no'


[1] Technology Readiness Levels (TRL) are a method of estimating technology maturity of components during the acquisition process. For non-technical components, you can specify “n/a”. For technical components, you can select them based on the following definition from the EC:

  • TRL 1 – basic principles observed
  • TRL 2 – technology concept formulated
  • TRL 3 – experimental proof of concept
  • TRL 4 – technology validated in lab
  • TRL 5 – technology validated in relevant environment (industrially relevant environment in the case of key enabling technologies)
  • TRL 6 – technology demonstrated in relevant environment (industrially relevant environment in the case of key enabling technologies)
  • TRL 7 – system prototype demonstration in operational environment
  • TRL 8 – system complete and qualified
  • TRL 9 – actual system proven in operational environment (competitive manufacturing in the case of key enabling technologies)