[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Catalog Of Core Processes
Nita, Edwin, Dave, and Jim: The document looks good. I certainly appreciate all your efforts! Here's some feedback to the document. Keep in mind that these are all suggestions even though it may not read that way (e.g. my comment may say "rename to xyz" when I mean "You may want to consider renaming abc to xyz.") Title Page: You have redundant titles: "ebXML Core Process Catalog ebXML BP Team" and "Catalog of Core Processes For Electronic Business XML (ebXML)." At this point (without having looked at many other ebXML documents, I would recommend that the main title (above the line, paragraph style "Title Cover"), be "ebXML Core Process Catalog" or "ebXML Catalog of Core Processes." There does not need to be a subtile (below the line, paragraph style "Subtitle Cover"); however, if one is desired, what about something like "Generic (or "Reusable") Business Processes for Electronic Business"? Version Number: Start with 0.1 and go from there. Section 1: The first paragraph should read, at this point: This document specifies an ebXML WORK IN PROGRESS - NOT FOR IMPLEMENTATION for the eBusiness community. Section 5, Design Objectives: Delete this section. Section 6, System Overview: Rename to "Catalog of Core Processes" or just "Core Processes." Add introductory text, borrowing from section 4 as necessary. For example: "The ebXML Catalog of Core Processes desicribes the set of core business processes that are generic in nature and can be used across various industries. The core processes are identified, classified, described, and cross-referenced to other standards in the sections that follow. Section 6.1, 6.2, 6.3: Delete these sections. Section 6.4, Catalog of Core Processes: This section becomes section 6.1 after deleting current sections 6.1, 6.2, and 6.3. If section 6 is renamed to "Catalog of Core Processes," then this section should be renamed to, say, "Core Process Cross Reference" or "List of Core Processes." Add an introductory paragraph that states that a brief description of each core process will be provided elsewhere in the document (like the section that follows). Section 6.2 (following current section 6.4, Catalog of Core Processes): Title this section, "Description of Core Processes" or "Core Process Descriptions." If the team does not provide any descriptions by next week, this section can just have an opening paragraph that states "descriptions to be provided at a later date." Section 7, References. The content in this section should be paragraph style "List." Delete the [BL73] reference since there is no reference in the document to it. We should discuss if this section should contain references to the RosettaNet PIPs (or perhaps just RosettaNet web site), EDIFACT, X12, etc. Respectfully, Brian -----Original Message----- From: Sharma, Nita [mailto:nsharma@netfish.com] Sent: Wednesday, October 18, 2000 6:17 PM To: ebXML-CCBP-Analysis (E-mail) (E-mail); Ebxml-Bp (E-mail); Ebxml-Core (E-mail) Subject: Catalog Of Core Processes Hi, Here is the updated list of core processes with cross reference across some industry standards - Rosettanet PIPs, X12, EDIFACT, JiPDEC/CII(Center for information of Industry of JAPAN Information Processing Development Center), BOD. Identification of the core processes were influenced by various industry initiatives like ROSETTANET , EIDX, CPFR , EIAJ, OAG etc. More will be included. Quite a challenge !! I look forward to your constructive feedback at the teleconference or via e-mail to the mailing list ebxml-ccbp-analysis@lists.ebxml.org <<COREPROCESS_ebxml.doc>> thanks - Nita (Nita Sharma) Netfish Technologies
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC