Difference between revisions of "API Special Interest Group/Current Design/Service Catalog"
| Line 13: | Line 13: | ||
Why are both needed? | Why are both needed? | ||
Which are guaranteed to be unique? | Which are guaranteed to be unique? | ||
| + | |||
| + | == JSON structure == | ||
| + | |||
| + | Does there need to be a top-level "access" property? | ||
Revision as of 16:33, 2 December 2014
The format of the service catalog needs to be fixed. The de facto standard is currently DevStack. We need to define a proper format for the service catalog.
Entry Points
How are entry points currently done for all the services?
Versions
How are versions currently done for all the services?
Name and Type
Why are both needed? Which are guaranteed to be unique?
JSON structure
Does there need to be a top-level "access" property?
