RE: [soa-rm] 08 draft publicly available

[Ken Laskey <klaskey@mitre.org>]

Robin,

I have been putting off people who have been asking for an early copy 
because I'm afraid of causing more confusion on things that may still 
radically change.  For example, although I believe a lot of the 
thinking is consistent, the description of "service" has gone through 
several incarnations from different perspectives.  I'd hate to finish 
the RM and find people sending around Powerpoint with descriptions 
from two versions back.

As for the archives being public, I only wish someone would read them 
in detail and summarize all the great things hidden in 2500 email 
messages.  Heck, I can't even remember half the stuff I said.

I am certainly glad to have the publicity (I think we're doing some 
really good work) and thanks for clarifying public availability issue.

Ken


At 02:29 PM 9/13/2005, Robin Cover wrote:
>On Tue, 13 Sep 2005, Chiusano Joseph wrote:
>
> > My understanding is that all drafts are supposed to be publicly
> > available, per OASIS policy. But Duane and/or Jamie can confirm for us.
>
>Indeed, Jamie Clark can confirm this, or one can inspect the TC Process.
>
>Not just "all drafts".  OASIS TC Process (2.8) "Visibility" specifies:
>
>"All web pages, documents, ballot results and email archives of all TCs
>and SCs shall be publicly visible."
>
>In other words, working in OASIS TCs means transparency, openness,
>and visibility to the public.  It's part of accountability and
>auditability -- as opposed to some standards venues in which the
>public cannot see what's being done, as it's being done in the
>back room, by the pay-for-play players: at OASIS, it is generally
>pay-to-play [modulo public feedback channels] but NOT pay-to-see.
>
>It's unfortunate [IMO] that the default setting on the Kavi tool
>makes it so easy for people to forget to ensure that materials
>uploaded into Kavi are accessible at a publicly-visible URI.  What
>often gets published in email to the list is a URI like:
>
>http://www.oasis-open.org/apps/org/workgroup/soa-rm/download.php/14353/wd-soa-rm-08.pdf
>
>which the "public" cannot see unless the public-person knows how to
>rewrite the URI to:
>
>http://www.oasis-open.org/committees/download.php/14353/wd-soa-rm-08.pdf
>
>Hope this helps,
>
>[completely unofficially]
>
>Robin Cover
>XML Cover Pages
>http://xml.coverpages.org/
>
>PS  Having noted Joe Chiusano's "-08, great job" and remembering that I
>had made a public reference to the Semantion FERA-based SOA Information
>Model, I wanted to ensure that the SO-RM TC's work was adequately known
>
>... Semantion FERA-based SOA Information Model and its
>reference architecture -- "The main components of the FERA reference
>architecture are: federates, interfaces, and SOA Federation. Each
>participant involved in the collaboration is called a federate. Federates
>can be systems or people..."
>
>http://xml.coverpages.org/soa.html#Semantion
>
>---------------------------------------------------------------------
>
> >
> > Joe
> >
> > Joseph Chiusano
> > Booz Allen Hamilton
> > O: 703-902-6923
> > C: 202-251-0731
> > Visit us online@ http://www.boozallen.com
> >
> >
> > > -----Original Message-----
> > > From: Ken Laskey [mailto:klaskey@mitre.org]
> > > Sent: Tuesday, September 13, 2005 2:17 PM
> > > To: SOA-RM
> > > Subject: [soa-rm] 08 draft publicly available
> > >
> > > Someone sent me the following
> > >
> > > Reference Model for Service Oriented Architectures.
> > > by
> > > OASIS SOA Reference Model TC, Working Draft 08
> > >
> > > This Service Oriented Architecture Reference Model is an
> > > abstract framework for understanding significant entities and
> > > relationships amongst them within a service-oriented
> > > environment, and for the development of consistent standards
> > > or specifications supporting that environment. It is based on
> > > unifying concepts of SOA and may be used by architects
> > > developing specific services oriented architectures or for
> > > education and explaining SOA. A reference model is not
> > > directly tied to any standards, technologies or other
> > > concrete implementation details, but it does seek to provide
> > > a common semantics that can be used unambiguously across and
> > > between different implementations.
> > > http://xml.coverpages.org/soa.html#SOA-RM-WD08
> > > http://xml.coverpages.org/SOA-RM-WD08.pdf
> > > http://www.oasis-open.org/committees/soa-rm/
> > >
> > > where the pdf link is our 08 draft.  I was under the
> > > impression that we were not supposed to be handing out draft
> > > that were not intended for public review.  Am I mistaken?
> > >
> > > Ken
> > >
> > > --
> > >
> > > --------------------------------------------------------------
> > > -------------------
> > >    /   Ken
> > > Laskey
> > >         \
> > >   |    MITRE Corporation, M/S H305    phone:  703-983-7934   |
> > >   |    7515 Colshire Drive                    fax:
> > > 703-983-1379   |
> > >    \   McLean VA 22102-7508
> > >            /
> > >
> > > --------------------------------------------------------------
> > > --------------------
> > >
> > >
> > >
> > >
> >
>
>--

--
      ---------------------------------------------------------------------------------
   /   Ken 
Laskey                                                                \
  |    MITRE Corporation, M/S H305    phone:  703-983-7934   |
  |    7515 Colshire Drive                    fax:      703-983-1379   |
   \   McLean VA 22102-7508                                              /
     ----------------------------------------------------------------------------------