[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: fyi, ebxml regrep requirements
>From the EBXML Requirements Specification, v 0.6. I need not point out that this is an ambitious list. 3.7 Registry and Repository The Registry and Repository Project Team detailed requirements and deliverables will: * Identify the long-term maintainer of this repository. * Develop detailed blueprints for an ebXML repository that - uses open management processes, - has open access, - has interfaces with other existing and planned XML business standards repositories, - accommodates - * versioning * metadata Registry * model interchange (e.g. UML - XML schemas) * tool-to-tool queries and exchanges * repository to repository queries and exchanges * tool to repository queries and exchanges * repository to tool queries and exchanges - enables model integration (e.g., how to create an XML schema from a UML diagram and vice-versa without loss or gain), - supports Web access, - includes - * a glossary of terms related to business process methodology: vocabulary (e.g., functional, non-functional, vertical, message, segment, data type using TMWG Unified Modeling Methodology document Annex 1) * a glossary of terms specific to each business process to be modeled * a glossary of ebXML semantic tags * archives of previous ebXML technical specifications. * archives of previous ebXML technical specifications - develops open XML based structures for storing information within a repository, - supports legacy information, including historical EDI directories (X12, UN/EDIFACT, etc.), - stores a legacy data model (e.g., IDEF-1X) and retrieves it back out as a UML class diagram, - stores 100% of a UML model (OCL, use cases, state diagrams, interaction diagrams, etc.) and retrieves it back out in its entirety, - enables businesses to interactively map internal application semantics to horizontal and vertical industry semantics (semantic equivalent mappings), - identifies data context with respect to where it is being used in the business process, - supports change or enhancement to an as a result of implementation issues, - supports exact and fuzzy search capabilities, - supports electronic work item proposals in any format, - identifies all the vertical domains for each artifact (UML classes, XML declarations), - differentiates work in progress to that which is an actual standard, - supports existing software and standards that are already in place. (reuse-buy-build principle), - ensures changes in repository content are restricted to authorized individuals, - ensures access is restricted as necessary, - provides predictable naming conventions based on a formal scheme, - provides predictable version identifiers based on a formal scheme, - provides dynamic mapping tools that automatically retrieve the most current file specification from a repository, - supports real time file specification retrieval to understand how to correctly parse a file and write out a conformant file, - identifies which trading partners are capable of engaging into a given electronic business transaction, - identifies which trading partners provide certain products and services, - identifies what networking schemes must be used to physically communicate with a trading partner, - facilitates discovery by intelligent information agents, - supports Internet 24x7 access, and - has repository performance levels that support real-time interaction with business applications. regards, Terry
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC