You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "Nigel Jones (JIRA)" <ji...@apache.org> on 2017/08/15 14:45:00 UTC

[jira] [Commented] (ATLAS-1691) OMAS Interfaces for Atlas

    [ https://issues.apache.org/jira/browse/ATLAS-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127323#comment-16127323 ] 

Nigel Jones commented on ATLAS-1691:
------------------------------------

I thought I'd start putting together a set of statements that relate to what OMAS is and how we build it.
See https://cwiki.apache.org/confluence/display/ATLAS/Standards+for+OMAS+interfaces
Comments welcome ... it's just a start......

> OMAS Interfaces for Atlas
> -------------------------
>
>                 Key: ATLAS-1691
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1691
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Nigel Jones
>            Assignee: Mandy Chessell
>              Labels: VirtualDataConnector
>
> The Open Metadata Access Services (OMAS) provide consumer specific interfaces to the metadata repository.   The hope is to have a community of vendor tools developing around each OMAS interface.   The OMAS interfaces are independent from one another to allow each community to evolve their own API at their pace.
> Related Jira will cover the list of OMAS interfaces that are oriented to particular tools & usage.
> Each OMAS JIRA needs to cover:
> * The Java and REST API for the OMAS call-response API
> * The appropriate OMAS Event Publisher and Listener



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)