Yes we do, and you are vely welcome here, dear H.Ozawa-san. You talked about two contracts - business and technical. This was unclear to me. Who participates in each of them?
Service Contract is a document derived from the Service Description document. The major difference is in that Service Contract is agreed between service consumer and producer; it may contain a full Service Description document or a sub-set of it. In one of my previous message a few days ago I listed sections of the Service Description, the same may be in the Contract. One of the sections is about service interfaces which have to inform consumer about logical and physiscal communication attributes with the service, including the protocol. We cannot say if it is a business or technical Contract because producer promises to preserve technical SLA and business functionality and RWE, all together. - Michael ----- Original Message ---- From: htshozawa <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, July 2, 2008 11:45:03 AM Subject: [service-orientated-architecture] Re: Goodson & Jason on Building a Data Services Layer My dear Michael, that depends on what you imply by Service Contract document. Taking Miko's pizza example, an user orders a pizza. She probably doesn't care what kind of vehicle the delivery person uses or which route he takes. She, however, probably do care when it is to be delivered and whether it is still hot or not. It seems like you people are all having a good time on the other side of the ocean. I have to swim over like Miko did and meet you in person sometimes. :) H.Ozawa --- In service-orientated- architecture@ yahoogroups. com, Michael Poulin <[EMAIL PROTECTED] .> wrote: > > Am I right, dear > H.Ozawa, that you do not mean Service Contract document? > - Michael > > > ----- Original Message ---- > From: htshozawa <[EMAIL PROTECTED] ..> > To: service-orientated- architecture@ yahoogroups. com > Sent: Tuesday, July 1, 2008 9:30:40 PM > Subject: [service-orientated -architecture] Re: Goodson & Jason on Building a Data Services Layer > > > This bring up a good point. There are two kinds of contracts - a > technical contract and business contract. As you stated, protocol is > part of a technical contract, but is often not part of a business > contract for a service. > > H.Ozawa > > --- In service-orientated- > architecture@ yahoogroups. com, "Karandikar, Amit" <amit.karandikar@ ...> > wrote: > > > > The protocol should be part of the technical contract of a service, > kind > > of like what the WSDL is today for web services. The formal contract > for > > the service wouldn't state the protocol (IMO). > > > > - Amit > > >
