atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <>
Subject [jira] [Commented] (ATLAS-1062) suggested model improvement
Date Wed, 27 Jul 2016 10:31:20 GMT


Hemanth Yamijala commented on ATLAS-1062:

[~davidrad], there is some implementation of this in ATLAS-819. We do have a couple of base
classes that model these common attributes, and there are some system attributes that are
mandatorily available in all attributes. There was feedback from the community that other
than system attributes, the base classes with common attributes are more advisory and not
mandatory (,
which seemed a more flexible model to adopt.

Also, the type system documentation has been updated but not pushed to public site with details
about these system defined classes and attributes. Until there is a doc push, you could possibly
use the docs that come up with the local build as reference - or even just look up

> suggested model improvement
> ---------------------------
>                 Key: ATLAS-1062
>                 URL:
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: David Radley
> I look at the Type architecture and I see that many elements have a name - it seems there
should be a higher abstraction for named things. 
> I suggest the highest thing IDataType in the Types architecture diagram have : 
> - a manditory name
> - a manditory global unique identifier
> - an optional short and long description
> - a curator / owner 
> - associated notes (notes are free form text that could be added we track, author, date
, version if we allow notes to be updated). 
> It would make sense to have a higher level object that contains these attributes, where
 IDataType is a subtype and a Term interface are subtypes.  

This message was sent by Atlassian JIRA

View raw message