[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: OASIS - Spam: failure notice
Hello,
My colleague is facing problem while posting messages to [soa-blueprint]
TC. Pls see below mail.
She initial request to join this TC was dated 2nd Nov and it was approved.
I have again approved her joining request.
Can you please check why she is facing such problem ?
Details are as follows :
Member Company - Polaris Software Lab Limited
Member Name - Radha Arur
Primary Contact - Pravin Gupta (i.e. myself)
Please treat this with priority.
Regards,
Pravin
----- Forwarded by pravin.gupta/Polaris on 11/29/2005 06:26 PM -----
radha.arur
11/29/2005 06:19 PM
To: pravin.gupta@polaris.co.in
cc:
Subject: OASIS - Spam: failure notice
Pravin,
Below is the failure notice i received today from OASIS, inspite of your
confirmation mail on partcipation yesterday. I will resend the mail to
admin@lists.oasis-open.org copying you and if the problem recurr again,
may be if you could send a mail to them after that it will be helpful.
Regards
----- Forwarded by radha.arur/Polaris on 29/11/2005 18:12 -----
MAILER-DAEMON@mail.oasis-open.org
29/11/2005 18:10
To: radha.arur@polaris.co.in
cc:
Subject: Spam: failure notice
Hi. This is the qmail-send program at mail.oasis-open.org.
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<soa-blueprints@lists.oasis-open.org>:
Sorry, only subscribers may post. If you are a subscriber, please forward
this message to admin@lists.oasis-open.org to get your new address
included (#5.7.2)
--- Below this line is a copy of the message.
Return-Path: <radha.arur@polaris.co.in>
Received: (qmail 30960 invoked by uid 60881); 29 Nov 2005 12:40:21 -0000
Received: from radha.arur@polaris.co.in by hermes by uid 0 with
qmail-scanner-1.15
(clamscan: 0.83. spamassassin: 2.64. Clear:SA:0(1.6/7.0
tests=NO_REAL_NAME autolearn=no ):.
Processed in 9.349022 secs); 29 Nov 2005 12:40:21 -0000
Received: from unknown (HELO trend-smtp.polaris.co.in) (202.54.189.10)
by mail.oasis-open.org with SMTP; 29 Nov 2005 12:40:11 -0000
Received: from psldns.polaris.co.in ([192.168.111.3])
by trend-smtp.polaris.co.in (Lotus Domino Release 6.5.1)
with ESMTP id 2005112918192541-274492 ;
Tue, 29 Nov 2005 18:19:25 +0530
Received: from psldns.polaris.co.in ([192.9.200.28]) by
psldns.polaris.co.in
with InterScan Messaging Security Suite; Tue, 29 Nov
2005 18:08:31 +0530
Subject: Re: [soa-blueprints] Primer
To: Ken Laskey <klaskey@mitre.org>
Cc: <marchadr@wellsfargo.com>,
<soa-blueprints@lists.oasis-open.org>
X-Mailer: Lotus Notes Release 5.0.4 June 8, 2000
Message-ID: <OFEA1642A7.B24BA877-ON652570C8.0040E54E@polaris.co.in>
From: radha.arur@polaris.co.in
Date: Tue, 29 Nov 2005 18:08:27 +0530
MIME-Version: 1.0
X-imss-version: 2.029
X-imss-result: Passed
X-imss-approveListMatch: *@polaris.co.in
X-MIMETrack: Serialize by Router on psldns.polaris.co.in/Polaris(Release
6.5.4FP1|June19, 2005) at
11/29/2005 06:08:31 PM,
Itemize by SMTP Server on Trend-Smtp/Orion/IN(Release
6.5.1|January 21, 2004) at
11/29/2005 06:19:25 PM,
Serialize by Router on Trend-Smtp/Orion/IN(Release
6.5.1|January 21, 2004) at
11/29/2005 06:20:40 PM,
Serialize complete at 11/29/2005 06:20:40 PM
Content-transfer-encoding: quoted-printable
Content-type: text/plain;
charset=ISO-8859-1
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on
hermes.oasis-open.org
X-Spam-Status: No, hits=1.6 required=7.0 tests=NO_REAL_NAME autolearn=no
version=2.64
X-Spam-Level: *
Ken,
Thanks for the comments. With reference to your question on reference of
W3C standard i was referring to w3c working draft on "per fee links". W3C
had come up with a recommendation and there were few implementations
based
on those recommendation. Though there is no work proceeding on those
recommendation, w3c continue to improvize on Xml security notation to
improvize the infrastructure for the atomic services.
Also, the new - Key Information System Service recommendation which
leverage the PKI can also be the reference for the working group to enable
thin client encryption.
Regards
=
=0D
Ken Laskey =
=0D
<klaskey@mitre.o To: =
radha.arur@polaris.co.in =
=0D
rg> cc: =
<marchadr@wellsfargo.com>, <soa-blueprints@lists.oasis-open.org> =
=0D
Subject: Re:=
[soa-blueprints] Primer =
=0D
25/11/2005 02:32 =
=0D
=
=0D
=
=0D
some comments inline.
On Nov 24, 2005, at 7:39 AM, radha.arur@polaris.co.in wrote:
Ken,
While i agree a blueprint has to be simple and start with a context
in
mind, majority of the time SOA implementation issue starts in the
beginning
when the service defn itself is in a flux even in a single context.
e.g
when a loan / credit appln says they are different or when
overlapping
services exist. This issues will become more when the blueprint has
to be
followed in scenarios where overlapping services offered in a multi
vendor
scenario and where exactly an SOA appln is warranted.
SOA provides a way to connect capabilities; the decision on what
capabilities to connect is still a domain-specific decision.=A0 Currently,
there is probably a human in the loop but hopefully we will eventually
create robust decision capabilities.=A0 SOA does not make domain-specific
decisions and it is wishful thinking to say it will make intelligent
decisions when humans haven't figured out what they would do.
As for an SOA blueprint, it can indicate the pieces that will be needed no
matter what the domain decision.=A0 For example, you probably want to=
monitor
what services are being used and how they perform.=A0 What level of
security/access control do you want to see?=A0 What level of assurance do=
you
want that messages go through?
In my opinion a blue print for a long running process=A0 and hence
their
process defn should have the following in mind.
a. Should not stop the service implementation in stage 1 itself for
want of
accurate service defn. The adaptive blueprint defn shared with us by
ebsoa
group for the adaptive, basic and dynamic service pattern for
collaborative
process may be adopted=A0 even in a single appln context.
This would seem to be a basic requirement for a blueprint.
b. The long running process by Ken example since it needs to be
able/capable of utilizing an atomic service, should in my opinion be
capable of sourcing plug in services. While a manual entry as stated
by
Ebsoa comitte is o.k in a non mission critical appln , it may not be
desirable in a mission critical situation.
Would a BPEL let us do that?
In following the previous item, a blueprint should allow domain-specific
service to be "plugged in" but we should consider the generic attributes
of
the long-running transaction.
c. The blueprint should also be able to relate pattern to an
architecture.
Ex - one should be able to gauge from the blueprint=A0 what type of
basic
service patterns could be used.
I think we need to decide the relationship between a blueprint and a
(reference) architecture.
d. I would also like to know the=A0 opinion on interoperability of=
w3c
standard=A0 for microcommerce market viz a viz=A0 SOA basic service=
defn
when
we like to apply it for portfolio charges.
Which W3C standard are you referring to?=A0 There was work several years=
ago
on micropayments but that never resulted in a Recommendation.
regards
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Ken
Laskey=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <klaskey@mitre.o =A0 =A0
=
=A0 =A0 To:=A0 =A0 =A0 <
marchadr@wellsfargo.com>, <jinu.joseph@polaris.co.in
>,
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 rg>=A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 <
soa-blueprints@lists.oasis-open.org
>
=A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 cc:=A0 =A0 =A0 (bcc:
radha.arur/Polaris) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 23/11/2005 21:09 =A0 =A0
=
=A0 =A0 Subject: RE:
[soa-blueprints]
Primer
OK, now we're getting to some meaty issues :-)
It would seem that a useful pattern would be a long-running business
process, where the "business" could as likely be technical as
commercial.=A0 What are the requirements of such a process?=A0 What
assumptions do we make about the process?=A0 What are the notional
pieces of a solution?=A0 How do these pieces notionally work
together?=A0 Where are there alternatives?=A0 Finally, what=
combination
of completed standards, specifications within standards committees,
and private specifications will likely enable such a blueprint?
Note, part of the output of this thought process could be feedback
to
existing committees on what is needed from their specs or how the
process needs to be curtailed to fit the current and evolving
standards.
Ken
At 10:24 AM 11/23/2005, marchadr@wellsfargo.com wrote:
Jinu these are good points.
Something I would say to this would be that in most
implementations
of SOA there are basic structures that could be followed with
the
variation being the actual business logic.
Even within a certain space there are multiple blueprint
needs.
For instance,
- Fulfilling a loan may be a long running process that might
take
into account a workflow with certain security requirements
etc...
- While making a wires transfer would have to be highly
available
and have routing based on fraud and security rules without the
need
of long running process
To apply them to some of the cases within the soalogic
approach
you
could see the following:
1. Based on the process of developing a product within
soalogic
they
need a managed long running process. This pattern without the
specific business logic could be applied to the loan case. Or
could
even be applied to strategic budget planning, etc...
2. The retail store is using a pos process that needs to be
secure
and have fraud detection for purchases made by the customer
this
could be applied without the specific business logic to a wire
transfer
case.
The actual blueprints could be extracted for 1 that state:
- WS-BPEL - manage the long running process
- Transport types that could apply (HTTP/HTTPS/MQ)
- WS-Security - for managing who is able to update from a
client
auth perspective
- WS-Coordination - to coordinate with different SORs
- WS-Notification - to alert either an operation or customer
service
agent of an issue within the process through an intermediary
service
- WS-Profile - for indentify the service
- WS-CAF - to provide context around who the requestor is
- Fault Management - how and what type of responses would
happen,
sending an WSN event?
- XACML - for determining the rights of the user invoking the
service
- etc...
So what you end up doing is creating a stack of patterns that
could
be applied to a problem area that involves long running
operations
or short fast operations, etc...
Of course the specific technology may not be decided upon
within the
blueprint but the concepts within WS-BPEL will be abstracted
with an
example implementation of how WS-BPEL fulfills the specific
request.
Essentially think of the types of services you have ever
created and
think about a lot of the common problems you had to solve
along
the
way to get specific business logic to be invoked within a
service
context. There are a lot of problems that are common across
implementations such as security, event management, auditing,
even
in some cases accounting to chargeback for a service
invocation
to a
specific customer or internal client. Some of these could be
in
a
ESB or some could reside with the service and it may be
worthwhile
to come up with a sample deployment for each blueprint that
may
determine the type of system needs associated with the
blueprint.
I'll try and come up with an example at the end of the week or
next
week so you don't think I am crazy :)
- Dan
-----Original Message-----
From: jinu.joseph@polaris.co.in [
mailto:jinu.joseph@polaris.co.in]
Sent: Tuesday, November 22, 2005 7:58 PM
To: soa-blueprints@lists.oasis-open.org
Subject: RE: [soa-blueprints] Primer
Hi Folks
I am just thinking aloud here.=A0 I feel that while a
blueprint
does give a
kind of basic map while moving into uncharted territory, it
still has the
following limitations
- Blueprints as discussed are limited to a category of
contexts. Going by
the house analogy the blueprint i need for the house will be
dependent on
who I am and where I want to build the house. If I am the
President of the
United States, then I cannot build the house using the same
blueprint that
you and me would use, Similarly if I would use different
blueprints to
build my house in the Sahara Dessert=A0 and my house in
Antarctica. What I
am
trying to say is that the Blueprint might applicable for a
type
of system
and may not be useable for all software systems wanting to go
the SOA way.
The SOA blueprint for the Financial Services Systems used by
Banks would
be
different from that used by Corporates for their Inventory
Management
System.
- Trying to make a generalized blueprint will lead to such a
high level of
abstraction that the blueprint itself might not be of much
use.
Going back
to the house analogy trying to make a generalized blueprint
might lead to
the blueprint only containing guidelines like, there should be
a
foundation, there should be a ceiling, there should be windows
etc...
- What I feel is that we should have SOA blueprints based on
software
segments such BFSI segment, ERP segment, Services like
Utilities etc.
What do you say ??
Regards
Jinu Joseph
Polaris Software Lab Ltd
e-mail: jinu.joseph@polaris.co.in
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <marchadr@wellsf
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 argo.com>=A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 To:
<klaskey@mitre.org>
=A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 cc:
<soa-blueprints@lists.oasis-open.org>, (bcc:
jinu.joseph/Polaris)
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 23-11-05 03:53 =A0
=
=A0 =A0 =A0 =A0 Subject: RE:
[soa-blueprints] Primer
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 AM
See comments below. Good feedback Ken.
=A0 =A0 =A0 -----Original Message-----
=A0 =A0 =A0 From: Ken Laskey [mailto:klaskey@mitre.org]
=A0 =A0 =A0 Sent: Tuesday, November 22, 2005 12:07 PM
=A0 =A0 =A0 To: Marchant, Dan R.
=A0 =A0 =A0 Cc: soa-blueprints@lists.oasis-open.org
=A0 =A0 =A0 Subject: Re: [soa-blueprints] Primer
=A0 =A0 =A0 At 09:50 AM 11/22/2005, marchadr@wellsfargo.com=
wrote:
=A0 =A0 =A0 =A0 =A0 =A0 Ken these are questions that I am
sure=
with be
concretely
=A0 =A0 =A0 =A0 =A0 =A0 established by this tc. Here is my
take=
(keep in
mind I am on
a
=A0 =A0 =A0 =A0 =A0 =A0 blackberry so it might be more terse=
than normal).
=A0 =A0 =A0 =A0 =A0 =A0 1. A blueprint in my mind is to=
establish a
structure to an
=A0 =A0 =A0 =A0 =A0 =A0 other wise disorganized approach to=
developing
software. I
have
=A0 =A0 =A0 =A0 =A0 =A0 typically called blueprints a
reference
architecture (not to
be
=A0 =A0 =A0 =A0 =A0 =A0 confused w/reference model).
=A0 =A0 =A0 =A0 =A0 =A0 2. Think of the scenario of buying=
building
blueprints from a
=A0 =A0 =A0 =A0 =A0 =A0 house designer and than having though=
blueprints
tweaked by a
=A0 =A0 =A0 =A0 =A0 =A0 local architect of the house. Maybe
for=
your
requirements you
=A0 =A0 =A0 =A0 =A0 =A0 need the kitchen closer to the family=
room or a
water closet
=A0 =A0 =A0 =A0 =A0 =A0 turned into a walk in closet.
Whatever=
the changes
the basic
=A0 =A0 =A0 =A0 =A0 =A0 structure is defined for what you
need=
to
accomplish building
a
=A0 =A0 =A0 =A0 =A0 =A0 house with N number of rooms that
each=
have a
function.
=A0 =A0 =A0 You might find this analogy interesting:
Go back to our house analogy. The RM captures concepts
related to
what makes up a house, e.g. room, window, door. It might
include
the concepts of food preparation area and personal
hygiene area
and
the relationship that there should be physical
separation
between
the two. Note that this provides a very North
American/western
Europe reference and not necessarily one that covers a
tent. So a
given RM already provides a perspective.
Given RM concepts, various RAs show how these concepts
can be
arranged in a useful pattern. So RA examples would be
(sorry for
the American terms) a colonial, a split-level, a
rambler,
etc.
You
can play with the pattern but one can say that any given
pattern
serves a particular set of purposes (e.g. a rambler is
on
one
level
for those who want/need to avoid stairs).
An architecture is then a specific plan to build a house
or set
of
houses. There can still be some variations but you don't
do
things
like moving fireplaces or structural walls, else you
have
a new
architecture.
=A0 =A0 =A0 [Marchant, Dan R.] Sounds a lot like the movie=
"Kitchen
Stories"
=A0 =A0 =A0 about the period of time where sweden was=
conducting
studies on the
=A0 =A0 =A0 usability of a kitchen to identify patterns of=
usage. In
some ways
=A0 =A0 =A0 the development of a blueprint is similar in
nature=
to
the kitchen
=A0 =A0 =A0 studies in the 50s.
=A0 =A0 =A0 Is a rambler a ranch style house? I agree with the
structural
=A0 =A0 =A0 statement creating a bit of constraints that take=
care of
the
=A0 =A0 =A0 reduntant nature of developing an SOA. Everyone
in=
the US
probably
=A0 =A0 =A0 has a water closet (bathroom) in the master
bedroom=
a
pattern that
is
=A0 =A0 =A0 identified based on the experience of the=
architects in
finding the
=A0 =A0 =A0 needs of the consumer of the house. Likewise the
blueprints can
=A0 =A0 =A0 evolve by building on the reference model.
=A0 =A0 =A0 =A0 =A0 =A0 3. To establish direction or rudder
the=
ship. You
need to
=A0 =A0 =A0 =A0 =A0 =A0 establish the pie in the sky and a=
blueprint can
help get a
=A0 =A0 =A0 =A0 =A0 =A0 handle on that pie.
=A0 =A0 =A0 If you have a ship without a rudder, you are
likely
beyond being
=A0 =A0 =A0 saved by a blueprint :-)
=A0 =A0 =A0 =A0 =A0 =A0 4. There is a type of tracability
that=
can be
accomplished
=A0 =A0 =A0 =A0 =A0 =A0 through following a blueprint. Also
it=
may be
important to
use
=A0 =A0 =A0 =A0 =A0 =A0 a third-party blueprint to establish
a=
motive for
changing
the
=A0 =A0 =A0 =A0 =A0 =A0 way a business does things, not sure
if=
this
applicable for
=A0 =A0 =A0 =A0 =A0 =A0 everyone but there is definely value
in=
having
something to
=A0 =A0 =A0 =A0 =A0 =A0 refer too.
=A0 =A0 =A0 Good points.=A0 Now can someone craft those into a
paragraph or two
=A0 =A0 =A0 that any of us can present to a client and they=
would
feel they
know
=A0 =A0 =A0 something they didn't know before?
=A0 =A0 =A0 [Marchant, Dan R.]=A0 Wiki ?
=A0 =A0 =A0 =A0 =A0 =A0 My take is this on the blueprint=
roadmap so to
speak.
=A0 =A0 =A0 =A0 =A0 =A0 1. Establish a couple different=
scenarios where
services
would
=A0 =A0 =A0 =A0 =A0 =A0 help and how the service would be=
structured within
that
=A0 =A0 =A0 =A0 =A0 =A0 context and including supporting=
services.
=A0 =A0 =A0 =A0 =A0 =A0 2. Take the scenarios and generalize=
them into
patterns with
=A0 =A0 =A0 =A0 =A0 =A0 some technology choices as and
example=
of
implementing
pattern.
=A0 =A0 =A0 =A0 =A0 =A0 3. Establish an overview of how all
the=
supporting
services
=A0 =A0 =A0 =A0 =A0 =A0 could be structure to support the=
various patterns.
=A0 =A0 =A0 =A0 =A0 =A0 It would essentially turn into a type=
of framework,
a service
=A0 =A0 =A0 =A0 =A0 =A0 could follow and establish the need
for=
supporting
services
in
=A0 =A0 =A0 =A0 =A0 =A0 a formal way.
=A0 =A0 =A0 Step 2 after you define a blueprint is to lay out=
how you
would
=A0 =A0 =A0 create one.=A0 Your roadmap looks like a good=
initial
approach, both
=A0 =A0 =A0 for motivating a blueprint and showing how one=
blueprint
=A0 =A0 =A0 can/should/might support more than one scenario.
=A0 =A0 =A0 =A0 =A0 =A0 I could see it on the same lines of=
developing
anything
spring
=A0 =A0 =A0 =A0 =A0 =A0 or a portal. You have a set of=
facilities that are
applicable
=A0 =A0 =A0 =A0 =A0 =A0 for certain scenarios that than could=
be
implemented of
=A0 =A0 =A0 =A0 =A0 =A0 configured appropriately.
=A0 =A0 =A0 =A0 =A0 =A0 The great unknown being what business=
logic is
performed but
=A0 =A0 =A0 =A0 =A0 =A0 most of it could be generalized into=
some type of
pattern.
For
=A0 =A0 =A0 =A0 =A0 =A0 example, transaction based, inquiry=
based,
aggregation, or
even
=A0 =A0 =A0 =A0 =A0 =A0 everyone's favorite semantic service.
=A0 =A0 =A0 =A0 =A0 =A0 Thoughts from the group?
=A0 =A0 =A0 =A0 =A0 =A0 Dan
=A0 =A0 =A0 =A0 =A0 =A0 -----Original Message-----
=A0 =A0 =A0 =A0 =A0 =A0 From: Ken Laskey <klaskey@mitre.org>
=A0 =A0 =A0 =A0 =A0 =A0 To: Marchant, Dan R.=
<marchadr@imc.wellsfargo.com>
=A0 =A0 =A0 =A0 =A0 =A0 CC:
soa-blueprints@lists.oasis-open.org
=A0 =A0 =A0 =A0 =A0 =A0 <soa-blueprints@lists.oasis-open.org>
=A0 =A0 =A0 =A0 =A0 =A0 Sent: Mon Nov 21 22:42:48 2005
=A0 =A0 =A0 =A0 =A0 =A0 Subject: Re: [soa-blueprints] Primer
=A0 =A0 =A0 =A0 =A0 =A0 I have not been following the email=
carefully
enough, so
=A0 =A0 =A0 =A0 =A0 =A0 forgive me if this has already been=
established but
=A0 =A0 =A0 =A0 =A0 =A0 1. Exactly what is a blueprint?
=A0 =A0 =A0 =A0 =A0 =A0 2. What purpose does it serve?
=A0 =A0 =A0 =A0 =A0 =A0 3. Why should I think one will be=
generally
applicable?
=A0 =A0 =A0 =A0 =A0 =A0 4. Why do I care?
=A0 =A0 =A0 =A0 =A0 =A0 Do we expect that a blueprint will be
a=
sort of
turnkey
=A0 =A0 =A0 =A0 =A0 =A0 formula?=A0 How do we determine the=
limits of
applicability for
a
=A0 =A0 =A0 =A0 =A0 =A0 given blueprint?=A0 Are there=
underlying assumptions
that all
=A0 =A0 =A0 =A0 =A0 =A0 blueprints have in common, or is each=
blueprint
fundamentally
=A0 =A0 =A0 =A0 =A0 =A0 different (a very possible=
construction), or are
there
=A0 =A0 =A0 =A0 =A0 =A0 fundamental groupings with multiple=
non-redundant
examples in
=A0 =A0 =A0 =A0 =A0 =A0 each group?
=A0 =A0 =A0 =A0 =A0 =A0 I think agreeing on a clear strawman=
definition of
blueprint
is
=A0 =A0 =A0 =A0 =A0 =A0 essential.=A0 It can be modified as
we=
learn more but
we need a
=A0 =A0 =A0 =A0 =A0 =A0 clear starting point.
=A0 =A0 =A0 =A0 =A0 =A0 Ken
=A0 =A0 =A0 =A0 =A0 =A0 On Nov 21, 2005, at 9:12 PM, <
marchadr@wellsfargo.com>
=A0 =A0 =A0 =A0 =A0 =A0 <marchadr@wellsfargo.com> wrote:
=A0 =A0 =A0 =A0 =A0 =A0 One question to pose to the group is=
maybe the case
study
=A0 =A0 =A0 =A0 =A0 =A0 actually becomes a type of primer for=
the
blueprints once the
=A0 =A0 =A0 =A0 =A0 =A0 blueprints are defined.
=A0 =A0 =A0 =A0 =A0 =A0 Thoughts?
=A0 =A0 =A0 =A0 =A0 =A0 Dan
=A0 =A0 =A0 =A0 =A0 =A0 ---
=A0 =A0 =A0 =A0 =A0 =A0 Ken Laskey
=A0 =A0 =A0 =A0 =A0 =A0 MITRE Corporation, M/S H305 =A0 =A0=
phone:
703-983-7934
=A0 =A0 =A0 =A0 =A0 =A0 7515 Colshire Drive=A0 =A0 =A0 =A0 =A0
=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 fax:
=A0 =A0 =A0 =A0 =A0 =A0 703-983-1379
=A0 =A0 =A0 =A0 =A0 =A0 McLean VA 22102-7508
=A0 =A0 =A0 --
=
--------------------------------------------------------------------------=
-------
=A0 =A0 =A0 =A0 / =A0 Ken Laskey
=A0 =A0 =A0 \
=A0=A0 =A0 =A0 |=A0 =A0 MITRE Corporation, M/S H305=A0 =A0=
phone:
703-983-7934 =A0 |
=A0=A0 =A0 =A0 |=A0 =A0 7515 Colshire Drive=A0 =A0 =A0 =A0 =A0
=
=A0 =A0 =A0 =A0 =A0 fax:
703-983-1379
=A0 =A0 =A0 |
=A0 =A0 =A0 =A0 \ =A0 McLean VA 22102-7508
=A0 =A0 =A0 /
=
--------------------------------------------------------------------------=
--------
This e-Mail may contain proprietary and confidential
information and
is sent for the intended recipient(s) only.
If by an addressing or transmission error this mail has been
misdirected to you, you are requested to delete this mail
immediately.
You are also hereby notified that any use, any form of
reproduction,
dissemination, copying, disclosure, modification,
distribution and/or publication of this e-mail message,
contents or
its attachment other than by its intended recipient/s is
strictly
prohibited.
Visit Us at http://www.polaris.co.in
--
=
--------------------------------------------------------------------------=
-------
=A0=A0 / =A0 Ken
Laskey
\
=A0 |=A0 =A0 MITRE Corporation, M/S H305=A0 =A0 phone:=A0=
703-983-7934 =A0 |
=A0 |=A0 =A0 7515 Colshire Drive=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=
=A0 fax:
703-983-1379 =A0 |
=A0=A0 \ =A0 McLean VA
22102-7508=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /
=
--------------------------------------------------------------------------=
--------
This e-Mail may contain proprietary and confidential information and
is sent for the intended recipient(s) only.
If by an addressing or transmission error this mail has been
misdirected to you, you are requested to delete this mail
immediately.
You are also hereby notified that any use, any form of reproduction,
dissemination, copying, disclosure, modification,
distribution and/or publication of this e-mail message, contents or
its attachment other than by its intended recipient/s is strictly
prohibited.
Visit Us at http://www.polaris.co.in
---
Ken Laskey
MITRE Corporation, M/S H305=A0 =A0 =A0phone:=A0 703-983-7934
7515 Colshire Drive=A0 =A0=A0 =A0=A0 =A0=A0 =A0=A0 =A0=A0 =A0=A0 =A0=A0 =
=A0fax:=A0 =A0 =A0=A0 =A0703-983-1379
McLean VA 22102-7508
This e-Mail may contain proprietary and confidential information and is=
sent for the intended recipient(s) only.=0D
If by an addressing or transmission error this mail has been misdirected
to=
you, you are requested to delete this mail immediately.
You are also hereby notified that any use, any form of reproduction,=
dissemination, copying, disclosure, modification,
distribution and/or publication of this e-mail message, contents or its=
attachment other than by its intended recipient/s is strictly prohibited.
Visit Us at http://www.polaris.co.in
This e-Mail may contain proprietary and confidential information and is sent for the intended recipient(s) only.
If by an addressing or transmission error this mail has been misdirected to you, you are requested to delete this mail immediately.
You are also hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification,
distribution and/or publication of this e-mail message, contents or its attachment other than by its intended recipient/s is strictly prohibited.
Visit Us at http://www.polaris.co.in
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]