Re: [regrep-semantic] common terms for SCM and questions on DW scenarios

["David RR Webber" <david@drrw.info>]

Evan,

Good questions.  In a nutshell this is the fusion of the
registry package capability + some yet-to-be-determined
XML instance that carries useful semantics about the
package.  And then a taxonony organizing these by
business domain, purpose, context, and so on.

How this gets done using the existing registry services
is what we need to document - this is probably
straightforward - but we need to just spell it out.

The idea of pluggable ebXML component sets was
an original requirement of the ebXML architecture - so
we're finally getting to realize that here.

We're not shooting completely in the dark here however.
The ebXML BPSS work has long sought to have registry
delivery of business process objects as a catalogue -
(aka dictionary/catalogue of BP objects).

They have useful semantics for this - spreadsheets -
but we'd have to ask the BPSS team to provide us
with a latest and greatest - (BTW - this did come up
 at the F2F last week - so its current again for them).

I'm intending for the BPSS catalogue folks to drive the
requirements here for us - I've cc:d Nita Sharma as the
point person.

I mentioned CPA - but these are really CPPs that you
tailor to become your CPA of course - but you need
those sample ones.

Then your question on "physical nouns" as opposed to
"conceptual nouns" - aka core components.  So these
are realization of core components as actual elements
in an XML business transaction with attendent properties
and use semantics that are tied to the physical domain
implementation.

Hope that all helps!

Thanks, DW

----- Original Message ----- 
From: <ewallace@cme.nist.gov>
To: <regrep-semantic@lists.oasis-open.org>
Sent: Tuesday, February 10, 2004 12:06 PM
Subject: [regrep-semantic] common terms for SCM and questions on DW
scenarios


>
> I think that we are rapidly approaching the point where we must address
> the concern that Zach brought up before.  That is, we need a common
> understanding of the terms we are using in our goal statements, scenarios,
> design documents, presentations and any other work product of this group.
> The ultimate form for this would be a SCM ontology, but I would be happy
> with a glossary.  Certainly, some of the terms that I find foreign are
> defined in other ebXML/OASIS documents.  It would be helpful for me if
> the sources for each of these terms were identified.
>
> Below are some questions regarding David Weber's two use cases.  Many
> of these questions stem from the terminology issue.
>
> **************************************************************************
>
> Questions regarding DW scenarios:
>
> BPcatalog scenario:
>
>   "By defining semantics for BP catalogue entries in Registry we can
>   provide a consistent way to package a BP definition, including all
>   the necessary components (CPA, BPSS, Transactions, Context use
>   rules) so that industry groups can quickly build re-usable
>   dictionaries of BP catalogues."
>
> - What is the form for these semantics?
> - Why would such a catalog include a CPA?  Aren't these dependent on
> participants in a Business Process?
> - What is a dictionary of catalogues?
>
> Basic Flow:
>   "analyst #1 assembles a collection of BP components, such as CPA,
>   BPSS, business transaction definitions, and context mechanism
>   details and publishes as a semantic object in XML to registry"
>
> Where are the semantics?
>
>   "analyst #1 assigns classification and taxonomy to BP catalogue entry"
>
> Does this step correspond to "insert a RIM:Classification object into
> the repository as a component of a RegistryObject instance?"  It
> appears that such an object should include associations with a
> ClassificationNode and the ClassificationScheme which contains that
> node.
>
> Alternate Flow:
>   "1.machine process retrieves semanticdetails of BP catalogue entry
>   as XML and then automatically configures ebXML components
>   accordingly (CPA - directs ebMS, BPSS - directs BP engine, et al)."
>
> Can you provide some example semanticdetails?
>
> =====
>
> Dictionary scenario
>
> What are "physical nouns"?
>
> **************************************************************************
>
> -Evan
>