Reminder - UCM (Unified Context Methodology Projkect)]

This just came up on todays' CPPA call - so I'm forwarding this
along.

 

I see a happy synergy here - in that CEFACT
team are defining the business functional and conceptual needs - that
then within OASIS we can develop formal XML mechanisms to support that
- and enhance out the ones we already have.

 

Of course please feel free to contact Jim
Wilson or Mary-Kay (emails below) if you are interested in
participating yourself.

 

Thanks, DW

-------- Original Message
--------
Subject: RE: [UNCEFACT-TMG - 2] Call for Participation -
UCM (Unified
Context Methodology Projkect)
From: "David RR Webber
(XML)" <>
Date: Tue, May 09, 2006 11:22
am
To: UN/CEFACT Techniques and Methodologies
Group
<>
Cc: "Stuhec,Gunther"
<>, ,

, 

Gunther,

This
is very excellent news indeed!

I have long championed the need
for this inside OASIS - however this has
largely fallen on fallow
ground because - unlike the CEFACT CCTS work -
there is no basis and
understanding of why role and context are so
indespensible tools in
defining consistent ebusiness interaction
systems!

The
closest that OASIS has come to this is defining a
variable
definition system in BPSS v2.0.3 so now context variables
can be set. 
Of course the CAM TC work fully supports use of common
context - and
indeed we have both a draft set of criteria and
factors that are
associated with common context management and also
a draft XSD schema
for a layout in XML to be
used.

http://www.oasis-open.org/committees/download.php/7254/Context%20Mechanism%20Synopsis%20and%20Proposal%20-%20draft.doc

http://www.oasis-open.org/committees/download.php/7253/ebContext-v1-draft.xsd

http://www.oasis-open.org/committees/download.php/7252/OASIS-BPSS-Specifications-Context-Management%20May15.doc

Also
- OASIS has now formally adopted the BCM V1.0 specification that
also
clearly lays out the use of role and context.

Clearly the
UNCEFACT UCM recognises the same essential needs.

I'd be happy
to coordinate this with OASIS too - because to be
successful this
needs to be something that both the design and
implementation worlds
are working off the same script to!

Thanks,
DW

-------- Original Message --------
Subject:
[UNCEFACT-TMG - 2] Call for Participation - UCM (Unified
Context
Methodology Projkect)
From: "Stuhec, Gunther"
<>
Date: Thu, April 27, 2006 10:41
am
To: 

Dear all, 

the TMG
is pleased to announce the approval of a project to define
context
methodology.  Please forward this announcement to all
groups
within your area of
responsibility.

Unified Context Methodology
Project

Context, as a key driver to precisely determine business
meaning and
intent of information definition and exchange, requires a
formal
structure and methodology.  Although context has been
identified as a
key component of the UN/CEFACT standard, a formal
mechanism for defining
and using context has not been in place. With
an increasing maturity of
a number of standards (CCTS, CCMA, UMM,
etc.) within UN/CEFACT that all
have strong needs to define and use
context, now is the time to form a
project to tackle this
problem.

Attached is the approved Project Proposal for the
development of the
technical specification for Context Methodology.
 This project has been
named Unified Context Methodology, or
UCM. 

This project is a joint project of TMG (under CCWG), TBG
(primarily
TBG14), and ICG.  The project will be led by TMG
member Joe Zhou,

<mailto:> , from Xtensible
Solutions.
 

Anyone else who would like to participate is asked to
send the following
Participation Information to 

Jim Wilson
at  <mailto:>  and

Mary Kay Blantz at  

<mailto:>  
  

by 5-MAY-2006  indicating your desired level of
participation in this
project.  

Participation
Information

UN/CEFACT, OASIS, and ISO TC 154 (and others) are
committed to
maintaining open standards.  Accordingly,
participation in this project
is open to all interested parties.
 Participation can be at the member
or observer level.
 Observers will be allowed full access to and
involvement in
all discussions.  Voting is restricted to members. Your
email
should include:

         
Name

         
Organization

          Email
address

          Phone
number

          Indication of level of
participation:  active member
or
observer

Regards,

Gunther Stuhec

TMG
Chair