2 messages in org.oasis-open.lists.safRE: [saf] Interfaces| From | Sent On | Attachments |
|---|---|---|
| Stav...@uk.fujitsu.com | Jun 9, 2010 7:48 am | |
| Lipton, Paul C | Jun 10, 2010 7:34 am |
| Subject: | RE: [saf] Interfaces | |
|---|---|---|
| From: | Lipton, Paul C (Paul...@ca.com) | |
| Date: | Jun 10, 2010 7:34:56 am | |
| List: | org.oasis-open.lists.saf | |
+1. The evolution of our thinking appears to be moving towards the collaborative
nature of SAF. In that case, the catalog is key. Given the interest/move towards
REST, a more abstract set of interfaces (that work well with REST MEPs and
principles) seems essential.
Thanks, Paul Paul Lipton VP, Industry Standards and Open Source Member, CA Council for Technical Excellence Phone (preferred number!): +1 215 867-9231 Mobile: +1 267 987-6887 Email: paul...@ca.com
-----Original Message----- From: Stav...@uk.fujitsu.com [mailto:Stav...@uk.fujitsu.com] Sent: Wednesday, June 09, 2010 10:49 AM To: sa...@lists.oasis-open.org Subject: [saf] Interfaces
Hi again,
not sure how much we want to move away from the Cloud profile, but going back to
more technical stuff is lots of fun, so if time permits tomorrow, perhaps we
should discuss about the catalogue interfaces as well. What is currently in the
spec, I think is too coarse (get catalogue and set catalogue!).
Also, if we do put interfaces in the spec, I think this should be done in a more
abstract level, e.g. what and how it can be manipulated, and not in any way that
mandates the use of specific technologies (e.g. WS).
Then maybe we could provide guidelines, samples, appendixes, on more concrete
interfaces for example using HTTP in a REST-like manner, or using WS-RF, etc.
Does this make sense? In any case, more in the call tomorrow.
Cheers,
Stavros