OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [soa-rm] Types of Services (RE: [soa-rm]Definitionof"Service Consumer")

Duane et al,

The onus is on me to 'walk the talk.'

I have an interesting slide and a few thoughts I can share tomorrow. 

In no way are my comments supposed to denigrate the discussions currently underway. I just think as most of us do that our definitions and terminology must be precise and our concepts must be contexted.


 -----Original Message-----
From: 	Duane Nickull [mailto:dnickull@adobe.com] 
Sent:	April 14, 2005 1:38 PM
Cc:	soa-rm@lists.oasis-open.org
Subject:	Re: [soa-rm] Types of Services (RE: [soa-rm]Definitionof"Service Consumer")

McGregor.Wesley@tbs-sct.gc.ca wrote:

>II firmly believe that if we do not define service and SOA within the context of time (amongst a host of other domains as a set of constraints) the model will be too thin to be viable. For example, security is a domain that need not be concretely defined except as a set of constraints(s1, s2, s3...) where, say s1 is the authentication constraint,  that bound the system but allow for infinite derivations. We cannot ignore reality, but we can describe it abstractly and we must be able to show we have considered those things that keep dragging us into the concrete (nice pun here)

Please make a suggestion to the group.  How would you word an axiom to 
declare this?


Senior Standards Strategist - Adobe Systems, Inc. - http://www.adobe.com
Vice Chair - UN/CEFACT Bureau Plenary - http://www.unece.org/cefact/
Adobe Enterprise Developer Resources  - http://www.adobe.com/enterprise/developer/main.html

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]