RE: Classifications

["Nieman, Scott" <Scott.Nieman@NorstanConsulting.com>]

-----Original Message-----
From: Terry Allen [mailto:tallen@sonic.net]
Sent: Thursday, April 13, 2000 6:49 PM
To: ebxml-regrep@lists.oasis-open.org;
Scott.Nieman@NorstanConsulting.com
Subject: Re: Classifications


Please resend in plain text or HTML.  Thanks.

regards, Terry

Title: Classifications

Proposed ebXML Registration Classifications

Tuesday, April 11, 2000

Name	Type ("/" implies OR)	Examples
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
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
stateOfSubmission [determines where in the development process the submission, in the view of the SO]	string/enum	inception, elaboration, construction, deployment
versionIndicator [based on a versioning scheme]	string	v1.0, v2.0 etc.
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
coreBusinessDomain [if the registry supports multiple domains, this should be used]	string/enum	automotive, aerospace, transportation, electronics, government
affectedInternalBusinessProcess [this could affect MANY internal business processes]	string/enum	purchasing, shipment, manufacturing process, finance
countSubmittedItems [if the submission is a package of items, then a count should be provided]	integer
indicatorPrimaryItem [if the submission is a package of items, ONE item is primary and others are supporting]	string/enum	primary, supporting
isTransformableToXML [based on the format, an item may be transformable to XML]	boolean
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
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