-
Type: Task
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Spec
-
Labels:None
-
Proposal:
-
Resolution:
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!)