Ok so for attributes I have thus far been adding them directly to the atom <entry> elements to keep things nice and flat and the <content> free for other purposes (e.g. expanding on a simple OCCI description of a compute or network resource with DMTF/OVF and SNIA standard descriptors respectively). For example:
<entry>
<id>...</id>
<compute:cores>4</compute:cores>
<compute:memory>16Gb</compute:memory>
...
</entry>
If you're worried about burning 1's and 0's on namespaces then you can trim them back:
<entry>
<id>...</id>
<c:cores>4</c:cores>
<c:memory>16Gb</c:memory>
...
</entry>
For the state transition links you need a few things:
- The link itself (URL)
- A machine-readable identifier for the link (e.g. http://purl.org/occi/state#start)
- A human-friendly identifier for the link in requested/local language (e.g. "Take Snapshot")
How this looks in atom:
<link title="Start" rel="http://purl.org/occi/state#start" href="http://example.com/{uuid}/state/start" />
Note that anybody can create new transitions but those that may need to be interoperable would end up in our registries.
Cheers,
Sam (sending offline)