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 Wed, 19 Jul 2017 14:22:00 GMT

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

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

Thanks for sharing. For next steps a few more thoughts (this is more general OMAS discussion)
 a) WHat does the community think is the best way to review the APIs? Should we be swagger-first?
swagger.io? standalone yaml or json? Or generate from a java skeleton? Review with review
board tool? wiki? Maybe it doesn';t matter?
 b) I'm thinking to link best practices (wiki) /discussion (jira/ml) from the parent OMAS
JIRA

> 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