[occi-wg] Issue 13

Gary Mazz garymazzaferro at gmail.com
Fri Oct 9 01:45:12 CDT 2009

Hi Michael,

In these urls, you basically have the right idea. However, we don't have 
a element following a machine address. We also do not have a resource 
for "application control". This is currently out of scope this this 
version of occi.. I believe Sam Johnston is working a language 
explaining "foreign" markup, where provider specific extensions can be 

We would expect to the the following in urls:

http://example.com/compute <http://example.com/%3Cmyresource/compute>		Define and configure machines
http://example.com/network <http://example.com/myresource/network>		Network configuration
http://example.com/storage <http://example.com/myresource/storage>		Storage services (SANs, etc)
 <http://example.com/myresource/application>TBD: "foreign" markup                   Application control


Michael Behrens wrote:
> For paragraph 2.2 Basics, under the URL Namespace paragraph, is this the sort of
> table desired/accurate?
> The following table is a list of recommended URLs and their purpose:
> http://example.com/<myresource/compute <http://example.com/%3Cmyresource/compute>		Define and configure machines
> http://example.com/myresource/network		Network configuration
> http://example.com/myresource/storage		Storage services (SANs, etc)
> http://example.com/myresource/application	Application control
> -- 
> Michael Behrens
> ------------------------------------------------------------------------
> _______________________________________________
> occi-wg mailing list
> occi-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/occi-wg

More information about the occi-wg mailing list