[
https://issues.apache.org/jira/browse/ATLAS-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Radley updated ATLAS-2133:
--------------------------------
Description:
Adding external type identifications (ExternalTypeIdDefs) as a new array
associated with attributes, structures (and the otehr defs). We are thinking
the elements would be specified in the typeDefs in the form:
ExternalTypeIdDefs [
{ "scheme":"O-DEF",
"value":"123-456",
"description":"Relational Database",
"ResponsibleOrg":"Open Group",
"ReferenceDocumentationURL":"http://xxx.yyy.zzz";
},
{
...
}
]
Scheme and value would be manditory.
One way to handle type aliases would be using the above mechanism:
{ "scheme":"alias",
"value":"RDB",
"description":"short hand relational database key for consumer A",
"ResponsibleOrg":"Consumer A organisation",
"ReferenceDocumentationURL":"http://aaa.bbb.bbb";
},
or
{ "scheme":"alias",
"value":"RDB"
},
There has been some discussion on this in the comments associated with
https://reviews.apache.org/r/62244/
was:
Adding external type identifications (ExternalTypeIdDefs) as a new array
associated with attributes, structures (and the otehr defs). We are thinking
the elements would be specified in the typeDefs in the form:
ExternalTypeIdDefs [
{ "scheme":"O-DEF",
"value":"123-456",
"description":"Relational Database",
"ResponsibleOrg":"Open Group",
"ReferenceDocumentationURL":"http://xxx.yyy.zzz";
},
{
...
}
]
Scheme and value would be manditory.
One way to handle type aliases would be using the above mechanism:
{ "scheme":"alias",
"value":"RDB",
"description":"short hand relational database key for consumer A",
"ResponsibleOrg":"Consumer A organisation",
"ReferenceDocumentationURL":"http://aaa.bbb.bbb";
},
or
{ "scheme":"alias",
"value":"RDB"
},
> Add ExternalTypeIdDefs to every Def element
> -------------------------------------------
>
> Key: ATLAS-2133
> URL: https://issues.apache.org/jira/browse/ATLAS-2133
> Project: Atlas
> Issue Type: Bug
> Reporter: David Radley
> Assignee: David Radley
>
> Adding external type identifications (ExternalTypeIdDefs) as a new array
> associated with attributes, structures (and the otehr defs). We are thinking
> the elements would be specified in the typeDefs in the form:
> ExternalTypeIdDefs [
> { "scheme":"O-DEF",
> "value":"123-456",
> "description":"Relational Database",
> "ResponsibleOrg":"Open Group",
> "ReferenceDocumentationURL":"http://xxx.yyy.zzz";
> },
> {
> ...
> }
> ]
> Scheme and value would be manditory.
> One way to handle type aliases would be using the above mechanism:
> { "scheme":"alias",
> "value":"RDB",
> "description":"short hand relational database key for consumer A",
> "ResponsibleOrg":"Consumer A organisation",
> "ReferenceDocumentationURL":"http://aaa.bbb.bbb";
> },
> or
> { "scheme":"alias",
> "value":"RDB"
> },
> There has been some discussion on this in the comments associated with
> https://reviews.apache.org/r/62244/
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
