Classification and discovery

[Bob Haugen <linkage@interaccess.com>]

As promised on Tuesday Sept 12 BP metamodel conference call:
this is my current sketch on how the ebXML metamodel could 
be used as a classification scheme for discovery.  I didn't spend
any time agonizing over this; feel free to criticize in any way;
it is only presented as a stimulus for discussion.

* The metamodel could be used as a schema for registering
information in repositories.

* The schema itself could be used as a vocabulary and grammar
for composing queries against the respositories.

* Here is a narrative example of a series of queries against
repositories, using a combination of the most-recent 
work-in-process metamodel and the context table elements
from the San Jose BP-CC alignment meetings.  
(List of useful elements at the end of this message.)

_Starting out_

A newbie wants to find how to do business using ebXML.

The first query is about how to query.  This needs to be posted
very prominently somewhere and also be promoted to all the
major search engines and directories.  Should be on the
first page on Google when searching for "ebXML".
The result page should include the vocabulary and grammar
hinted at above, maybe in the form of query-by-example.

The goal of many business queries is to exchange resources, 
e.g., to buy or sell a product or service. 
(In this message, I use "service" in the sense of work-for-hire,
not a web service or technical interface).

_Buying_

If the goal is to buy something, then the newbie will probably
want to search for the desired product or service.
(Curiously, UDDI says it does not provide such a query.)
They might start with some general classification like computers
or vegetable oil, or they might start with something very 
specific like a Palm Pilot.  The general classification for
products and services in the ebXML metamodel is
EconomicResourceDefinition.  (Called EconomicResourceType
in V2.0.)  I think ebXML should specify a level or two of
hierarchy below that, because it is too abstract for people
to understand.  So maybe:
    EconomicResourceDefinition
        ProductDefinition
        EconomicServiceDefinition
            TransportationServiceDefinition
        FinancialInstrumentDefinition
        ResourceFamily
        ...etc...

Once the desired product or service is found, then the
search might go for Parties who provide the product or
service.

Once a Party is found, then the newbie will need to
query for the BusinessCollaboration protocols used
to buy the desired product or service.  The Business
Collaboration should contain all the information required
to make the deal.

_Supply Chains_ 

If the goal is to trade repeatedly, for example
in a supply chain context, the newbie might want
to join a community or marketplace and negotiate
EconomicContracts, so the BusinessCollaboration
will be more elaborate and will probably involve
establishing TradingPartyAgreements.

_Selling_

If the goal is to sell something, then the newbie might 
start with high-level categories like Industry or Region
or Market.  

In this case, the newbie will want to find a repository
and register their information, so they will query for
the BusinessCollaboration protocol for registering
themselves in the repository.  They might look for
CommonBusinessProcesses and CoreComponents
from which to compose their own BusinessCollaborations
and BusinessDocuments.  They will probably want
to register their own TradingPartyProfile showing
how they like to do business.  They may also
want to register the products and services
they offer.

* From the metamodel and context table, here is a
list of possibly-useful classification and discovery elements:

Market
Industry
PhysicalGeography or Region
Geo-Political or Community
Regulatory(Authority?)

Party
PartnerType

EconomicResourceDefinition
    ProductDefinition
    EconomicServiceDefinition
        TransportationServiceDefinition
        ...etc...
    FinancialInstrumentDefinition
    ...etc...
    ResourceFamily

BusinessCategory
BusinessArea
ProcessCategory

CommonBusinessProcess
BusinessCollaboration (once called BusinessProcess)

BusinessDocument
CoreComponents

Respectfully,
Bob Haugen