Proposed ebXML Registration Classifications

Wednesday, April 19, 2000

Version

Editor

Date

v0.001

[base document]

Scott Nieman, Norstan Consulting

4/13/2000

v0.002

[Added Responsible entity column; provided feedback]

Scott Hinkelman, IBM

4/13/2000

v0.003

[added versionOfSubmittedItem, rename stateOfSubmittedItem to processStepOfSubmittedItem]

Scott Nieman, Norstan Consulting

4/19/2000

 

Name

Type ("/" implies OR)

Examples

Responsible entity

formatOfSubmittedItem

[some items can be parsed; this would allow the trigger to parse the submitted items. This should be set for each item in the submission]

string/enum

UML model,

XMI,

DTD,

XML Schema,

SGML DTD,

IDEF-0 model,

IDEF-1X,

Powerpoint,

Visio

SO

versionOfSubmittedItem

[this is the version of the submitted item in the format above]

string

XMI 1.1

Zip 2.04G

SO

typeOfSubmittedItem

[each item in the submission should have this set]

string/enum

business pattern,

business process model,

data interchange standard,

utility class,

core component

semantic mapping

SO

processStepOfSubmission

[determines where in the development process the submission, in the view of the SO]

string/enum

inception,

elaboration,

construction,

deployment

SO/RegRep

versionIndicator

[based on a versioning scheme]

string

v1.0,

v2.0 etc.

RegRep

intentOfSubmission

[the SO intend for the submission, whether it is to evolve into an ebXML standard, remain as a company standard, etc.]

  

ebxml Standard for consideration,

industry convention,

corporate standard

SO

coreBusinessDomain

[if the registry supports multiple domains, this should be used]

string/enum

automotive,

aerospace,

transportation,

electronics,

government

SO

affectedInternalBusinessProcess

[this could affect MANY internal business processes]

string/enum

purchasing,

shipment,

manufacturing process,

finance

SO

countSubmittedItems

[if the submission is a package of items, then a count should be provided]

integer

  

SO

indicatorPrimaryItem

[if the submission is a package of items, ONE item is primary and others are supporting]

string/enum

primary,

supporting

SO

isTransformableToXML

[based on the format, an item may be transformable to XML]

boolean

  

RegRep

scoreQuality

[based on format, and ability to parse the submission, the submission item or package can be evaluated by software against the ebXML Metamodel. Missing items can be flagged, weighted scores can be computed]

string/double

based on parsing of submission; assigned weighting factor

RegRep

isPresentProcessSpec

[since Process models are the primary requirement in next generation XML based EDI, this flag should be set as a result of the quality check. If the SO believes that they have provide sufficient process information but the format cannot be parsed, this flag can be checked but scoreQuality is NULL]

boolean

  

SO