Minor editorial comments on TA v0.95

[Brian Eisenberg <BrianE@DataChannel.com>]

Title: RE: TA Specification Review

I just did another run through the spec and would like to log the following minor editorial comments. These will be fixed after the QRT approves the spec, and releases the document to the ebXML community for comments and review (as per Anders schedule). These changes, SHALL in no way delay the vote to APPROVE the TA spec for submission to the QRT.

 

--Brian

 

>>>>>>>>>

 

line 168 - Add title for RFC 2119 "Keywords for use in RFCs to Indicate Requirment Levels"

 

line 222 - Last sentence - add "level of detail required ...to build ebXML compliant applications, components, and services."

 

line 241 - change "information model" to "Information Meta Model"

 

line 258 - change "parties" to "Trading Partners"

 

line 274 - un-italicize "information"

 

line 276 - capitalize and italicize "Business Processes"

 

line 313 - add "Architecture" to "ebXML Reference Model"

 

line 369 - delete carriage return

 

line 390 - replace "Business Objects" with "Business Information Entities"

 

line 415 - add "MAY" to "mechanisms <> include"

 

line 432 - delete "and Repository" as we are simply referring to RegRep as "Registry Services" to avoid confustion

 

line 456 - remove "Object" 

 

line 472 - remove "Object"

 

line 485 - remove "as"

 

line 501 - italicize CPP

 

line 510 - italicize CPP + Trading Partners

 

line 517 - italicize Registry + CPP

 

line 518 - italicize Trading Partner

 

line 519 - Capitalize and italicize Business Processes

 

line 561-568 - change to "Business ProcessES" and italicize CPP + CPA + Registry instances, expand BP to Business Processes

 

line 570 capitalize MUST, italicize Messaging Service + CPP, capitalize MAY, Capitalize + italicize Message Header

 

line 576-589 - italicize CPP + CPA + Trading Partner instances

 

line 580 - add "The definition of..." to ...what a trading partner "will do" MUST...

 

line 596 - replace "parties" with "Trading Partners"

 

line 611 - change Business Objects to "Business Information Entities"

 

line 616 - replace objects with "information entities"

 

line 617 - capitalize and italicize "Business Process"

 

line 619 - italicize Meta Model

 

line 624 - italicize UML + DTD

 

line 637 - replace partners with "Trading Partners"

 

line 641 - capitalize and italicize Business Processes

 

line 655 - capitalize and italicize "Business Process and Information Meta Models"

 

line 670 - capitalize and italicize "Information Meta Model"

 

line 675 - replace data with information

 

line 695 - replace partners with Trading Partners

 

line 702 - delete carriage return

 

line 710 - replace component with "Information Entity"

 

line 720 - italicize Registry

 

line 727 - figure 12 - replace "Business Objects" with "Business Information Entities"

 

line 743 - capitalize MAY

 

line 746 - replace can with MAY, insert: ...be either an individual piece of business information <insert>, called a Business Information Entity"</insert>, or..

 

line 751 - capitalize MAY

 

line 760 - replace mechanism with system

 

line 770 - add "Entities" to ...Business Information"

 

line 773 - same as 770

 

line 780 - capitalize and italicize Core Components

 

lines 740, 755, 778, 788, 791 - delete carriage return

 

line 795 - capitalize and italicize Business Context

 

line 802 - replace "object" with "Information Entity"

 

line 810 - capitalize and italicize Aggregate or Business Context

 

line 818 - italicize APIs

 

line 852 - italicize Registry Clients

 

line 878 - italicize Registry

 

line 893 - add "Meta" to Information <insert/> Model

 

line 902 - italicize Registry

 

line 921 - capitalize and italicize Business Messages

 

line 928-929 - capitalize and italicize Transport Services; change interface to Service Interface

 

line 955, 961 - capitalize and italicize Payload

 

line 957-958 - capitalize and italicize "Simplex", "Request/Response", "Synchronous", and "Asynchronous"

 

line 967 - replace party with "Trading Partner"

 

line 992 - italicize Message

 

line 1005 - add carriage return before figure 17

 

lines 1012-1012 - italicize references to MIME

 

line 1017 - replace objects with "Information Entities"

 

section 10 - capitalize and italicize all instances of Conformance, Technical Architecture Specification, ebXML Infrastructure, Conformance Clause, Conformance Testing, Conformance Requirements.

 

line 1086, 1090-1091 - unitalicize applicaitons and implementations - fix ebXML (from EbXML)

 

line 1098 - replace will with SHALL