[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (CAMP-44) Clarify resource type issues and API
[ http://tools.oasis-open.org/issues/browse/CAMP-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Chapman updated CAMP-44: -------------------------------- Summary: Clarify resource type issues and API (was: Clarify type issues and API) Priority: Minor (was: Major) link to CAMP-1 and CAMP-39 > Clarify resource 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 > Components: Spec > Reporter: Alex Heneveld > Priority: Minor > > 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]