atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nigel Jones (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-1698) Create Glossary OMAS API
Date Tue, 15 Aug 2017 14:47:00 GMT

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

Nigel Jones commented on ATLAS-1698:
------------------------------------

I thought I'd try and summarise some of my thoughts around OMAS design in general (not specific
to glossary or indeed GAF) through a series of statements at https://cwiki.apache.org/confluence/display/ATLAS/Standards+for+OMAS+interfaces

Agree or not, hopefully this could be the start of documenting our "standards" of how to define
an OMAS interface?

> Create Glossary OMAS API
> ------------------------
>
>                 Key: ATLAS-1698
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1698
>             Project: Atlas
>          Issue Type: Sub-task
>            Reporter: David Radley
>            Assignee: David Radley
>              Labels: VirtualDataConnector
>         Attachments: apidocs-5.zip, Atlas Glossary OMAS API proposal v1.0 .pdf, Atlas
Glossary OMAS API proposal v1.1.pdf, Atlas Glossary OMAS API proposal v1.2.pdf
>
>
> The Glossary OMAS provides a specialized API for glossary applications to retrieve and
store their glossary metadata and link assets of different types to these glossary entries.
> The Glossary OMAS makes heavy use of the Area 2 open metadata model.  See https://cwiki.apache.org/confluence/display/ATLAS/Area+2+-+Glossary



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

Mime
View raw message