XML for sure, since I don't think we're contemplating returning lots of data or objects. I'd like to think of the OSDash services as reasonably lightweight from a bandwidth standpoint.
Encapsulating it in the /osdash tags is what would make it the osdash data standard. Interchanges that involve <osdash></osdash>. Should it *always* return the session ID for security purposes?
Maybe a good way to define what is in it is to explain what we want it to do. For example, I'd like eventually to be able to load the elements of a skin from a skinning service. Does that mean it has to define things like <button> or <textbox> or image locations or are those more specific to the actual service and consumer of the service?
Should we have external and internal resources like URL's or file locations or are those more useful on a service by service perspective? Maybe it would be useful to 'point' to an adaptation or configuration file in the standard so that if the client is a mobile phone or headless (Sheeva) that it would use those files for consuming services?