OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Created: (CAMP-44) Clarify type issues and API


Clarify type issues and API
---------------------------

                 Key: CAMP-44
                 URL: http://tools.oasis-open.org/issues/browse/CAMP-44
             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
          Issue Type: Task
            Reporter: Alex Heneveld


There were several key questions about types that have come up in today's F2F:

What type hierarchy will we use?  Mark requests ability to define e.g. MyGreatDatabase which extends Database.  (We could also have multiple inheritance / interface / etc.)

How do we explore the type hierarchy?  (The apidoc suggestion in CAMP-1 could come in here.)

And do we permit dynamic attribute extensions -- e.g. a resource instance has values for other attributes not on its type?  (Yes please!)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]