Sam,
I presume that interested clients would parse for the value of the
"rel" parameter in order to know the purpose of the link. If so, then
I think that all the life-cycle values should also be listed in table 2
- Link Relations. I inserted the type="action" in the example below -
I did not see "class" as a link-parameter in the draft-nottingham draft
on web-linking. Also, I presume the title parameter would be optional.
< Link: </us-east/webapp/vm01;start>;
< rel="http://purl.org/occi/action/start";
type="action"
< title="Start"
Good discussion on this thread!....looking forward to the telecons and
the future F2F (good idea Andre!).
PS: We are going to be implementing a small portion of the spec soon -
initially will be coding up the GET verb. We'll share our experiences
as soon as we can. I'll be coding up the client - so it should be able
to hit our implementation and others too.
--
Michael Behrens