{"id":372560,"date":"2024-10-20T02:29:53","date_gmt":"2024-10-20T02:29:53","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-iso-15000-12021\/"},"modified":"2024-10-26T04:21:36","modified_gmt":"2024-10-26T04:21:36","slug":"bs-iso-15000-12021","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-iso-15000-12021\/","title":{"rendered":"BS ISO 15000-1:2021"},"content":{"rendered":"
This document provides a communication-protocol neutral method for exchanging electronic business messages. It defines specific enveloping constructs supporting reliable, secure delivery of business information. Furthermore, this document defines a flexible enveloping technique, permitting messages to contain payloads of any format type.<\/p>\n
It specifies each of the following:<\/p>\n
Messaging model<\/p>\n<\/li>\n
Message pulling and partitioning<\/p>\n<\/li>\n
Processing modes<\/p>\n<\/li>\n
Message packaging<\/p>\n<\/li>\n
Error handling<\/p>\n<\/li>\n
Security module<\/p>\n<\/li>\n
Reliable messaging module<\/p>\n<\/li>\n<\/ul>\n
This document is applicable to all types of organizations (e.g., commercial enterprises, government agencies, not-for-profit organizations) that exchange documents or data electronically using messaging.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
5<\/td>\n | Contents <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 1. Scope 2. Normative references <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 3. Terms and definitions <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 4. Relevant messaging concepts 4.1. Web services and their role in an eBusiness messaging framework <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 4.2. Caveats and assumptions 4.3. XML notation 4.4. Namespace prefixes <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 4.5. Example domains 5. Messaging model 5.1. Model components 5.1.1. Components of the model <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 5.1.2. Messaging roles <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 5.1.3. Abstract messaging operations 5.2. Message exchange patterns 5.2.1. Rationale <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 5.2.2. General definition 5.2.3. MEP bindings <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 5.2.4. Relationship to SOAP MEPs 5.2.5. The One-Way\/Push MEP <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 5.2.6. The One-Way\/Pull MEP <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 5.2.7. The Two-Way\/Sync MEP <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 5.2.8. Other transport-channel-bound MEPs <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 6. Message pulling and partitioning 6.1. Objectives 6.2. Supporting message pulling <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 6.3. Combining pulling with security and reliability <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 6.4. Message partition channels 6.4.1. Concept and purpose <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 6.4.2. Some use cases <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 6.4.3. Definition and usage requirements <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 7. Processing modes 7.1. General <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 7.2. Messaging service processing model <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 7.3. Processing mode features <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 7.4. Default features for processing mode <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 8. Message packaging 8.1. Message envelope and message parts 8.1.1. MIME structure and SOAP profile <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 8.1.2. MIME and XML considerations 8.1.2.1. Additional MIME parameters 8.1.2.2. Reporting MIME errors 8.1.2.3. XML prolog 8.1.2.4. XML declaration 8.1.2.5. Encoding declaration <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 8.1.3. ebXML SOAP envelope extension 8.1.3.1. General 8.1.3.2. namespace pseudo attribute 8.1.3.3. xsi:schemaLocation attribute <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 8.1.3.4. SOAP header element 8.1.3.5. SOAP body element 8.1.3.6. ebXML SOAP extensions 8.1.4. ebMS header <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 8.1.5. Payload containers <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 8.2. The eb:Messaging container element 8.2.1. General <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 8.2.2. eb:Messaging element specification <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | 8.2.3. eb:Messaging\/eb:UserMessage 8.2.3.1. General 8.2.3.2. eb:Messaging\/eb:UserMessage\/eb:MessageInfo <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 8.2.3.3. eb:Messaging\/eb:UserMessage\/eb:PartyInfo 8.2.3.4. eb:Messaging\/eb:UserMessage\/eb:PartyInfo\/eb:From 8.2.3.5. eb:Messaging\/eb:UserMessage\/eb:PartyInfo\/eb:From\/eb:PartyId <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 8.2.3.6. eb:Messaging\/eb:UserMessage\/eb:PartyInfo\/eb:To 8.2.3.7. eb:Messaging\/eb:UserMessage\/eb:CollaborationInfo 8.2.3.8. eb:Messaging\/eb:UserMessage\/eb:CollaborationInfo\/eb:AgreementRef <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 8.2.3.9. eb:Messaging\/eb:UserMessage\/eb:CollaborationInfo\/eb:Service <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 8.2.3.10. eb:Messaging\/eb:UserMessage\/eb:CollaborationInfo\/eb:Action 8.2.3.11. eb:Messaging\/eb:UserMessage\/eb:CollaborationInfo\/eb:ConversationId 8.2.3.12. eb:Messaging\/eb:UserMessage\/eb:MessageProperties <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 8.2.3.13. eb:Messaging\/eb:UserMessage\/eb:PayloadInfo 8.2.3.14. eb:Messaging\/eb:UserMessage\/eb:PayloadInfo\/eb:PartInfo <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 8.2.4. eb:Messaging\/eb:SignalMessage 8.2.4.1. General <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 8.2.4.2. eb:Messaging\/eb:SignalMessage\/eb:PullRequest 8.2.4.3. eb:Messaging\/eb:SignalMessage\/eb:Error 8.2.4.4. eb:Messaging\/eb:SignalMessage\/eb:Receipt 8.2.5. Message unit bundling <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 8.3. Examples of ebMS messages (informative) 8.3.1. General 8.3.2. UserMessage example <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 8.3.3. PullRequest message example 8.3.4. Error message example <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 8.3.5. Receipt message example 8.3.6. “Bundled” message example <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 9. Error handling 9.1. General 9.2. Packaging of ebMS errors 9.2.1. eb:Error element 9.2.2. eb:Error\/@origin <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 9.2.3. eb:Error\/@category 9.2.4. eb:Error\/@errorCode 9.2.5. eb:Error\/@severity 9.2.6. eb:Error\/@refToMessageInError 9.2.7. eb:Error\/@shortDescription 9.2.8. eb:Error\/Description 9.2.9. eb:Error\/ErrorDetail 9.3. ebMS Error message <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 9.4. Extensibility of the eb:Error element 9.4.1. Adding new ebMS errors 9.5. Generating ebMS errors 9.6. Error reporting <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | 9.7. Standard ebMS errors 9.7.1. General 9.7.2. ebMS processing errors <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | 9.7.3. Security processing errors <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 9.7.4. Reliable messaging errors 10. Security module 10.1. General 10.2. Security element <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 10.3. Signing messages 10.4. Signing SOAP with attachments messages <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | 10.5. Encrypting messages 10.6. Encrypting SOAP with attachments messages 10.7. Signing and encrypting messages 10.8. Security token authentication 10.9. Security policy errors <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | 10.10. Secured message examples 10.10.1. Digitally signed and encrypted ebXML message <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | 10.10.2. Digitally signed and encrypted ebXML SOAP with attachments message <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | 10.10.3. Digitally signed receipt signal message <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | 10.11. Message authorization <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | 10.12. Securing the PullRequest signal 10.12.1. Authentication 10.12.2. Authorization 10.12.3. Preventing replay attacks 10.13. Countermeasure technologies 10.13.1. Persistent digital signature <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | 10.13.2. Persistent signed receipt 10.13.3. Non-persistent authentication 10.13.4. Non-persistent integrity 10.13.5. Persistent confidentiality 10.13.6. Non-persistent confidentiality 10.13.7. Persistent authorization 10.13.8. Non-persistent authorization 10.14. Security considerations <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | 11. Reliable messaging module 11.1. The reliable messaging model 11.1.1. General 11.1.2. Message processing 11.1.3. The reliable messaging processor in the MSH <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | 11.2. Reliable delivery of ebMS messages 11.2.1. General 11.2.2. Reliability contracts for the RMP <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | 11.2.3. Reliability contracts for the MSH <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | 11.2.4. Reliability for signal messages 11.2.5. Handling of delivery failures <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | 11.3. Reliability of ebMS MEPs 11.3.1. General <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 11.3.2. Reliability of the One-Way\/Push MEP <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | 11.3.3. Reliability of the One-Way\/Pull MEP <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | 11.3.4. Reliability of the Two-Way\/Sync MEP <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | 11.3.5. Reliability of other transport-channel-bound MEPs <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | Annex A. (informative) The ebXML SOAP extension element schema <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Annex B. (informative) Reliable messaging bindings B.1. General B.2. WS-Reliability binding B.2.1. Operations and contracts binding B.2.2. Complement to the reliability of the One-Way\/Push MEP <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | B.2.3. Complement to the reliability of the One-Way\/Pull MEP <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | B.2.4. Complement to the reliability of the Two-Way\/Sync MEP <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | B.3. WS-ReliableMessaging binding B.3.1. Operations and contracts binding <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | B.3.2. Complement to the reliability of the One-Way\/Push MEP B.3.3. Complement to the reliability of the One-Way\/Pull MEP <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | B.3.4. Complement to the reliability of the Two-Way\/Sync MEP <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Annex C. (informative) SOAP format and bindings C.1. General C.2. Using SwA with SOAP-1.1 <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | C.3. Using SwA with SOAP-1.2 <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | C.4. SMTP binding <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Annex D. (informative) Processing modes D.1. Objectives and usage <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | D.2. Model for processing modes D.2.1. General <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | D.2.2. Notation <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | D.3. Processing mode parameters D.3.1. General D.3.2. General P-Mode parameters <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | D.3.3. PMode[1].Protocol D.3.4. PMode[1].BusinessInfo <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | D.3.5. PMode[1].ErrorHandling <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | D.3.6. PMode[1].Reliability <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | D.3.7. PMode[1].Security <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | Annex E. (informative) P-Mode values and ebMS MEP bindings E.1. General E.2. P-Mode Values and the One-Way\/Push MEP <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | E.3. P-Mode Values and the One-Way\/Pull MEP E.4. P-Mode Values and the Two-Way\/Sync MEP <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | Annex F. (informative) Compatibility mapping to ebMS 2.0 F.1. Objectives and approach F.2. Compatibility mapping rules F.2.1. General <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | F.2.2. (CM1) Header mapping rules F.2.2.1. General F.2.2.2. Rule CM1-a: Mapping general message information F.2.2.3. Rule CM1-b: Mapping party information F.2.2.4. Rule CM1-c: Mapping collaboration information F.2.2.5. Rule CM1-d: Mapping agreement reference <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | F.2.3. Rule CM2-a: mapping attachments F.2.4. (CM3) Reliability mapping rules F.2.4.1. General F.2.4.2. Rule CM3-a: acknowledgments F.2.4.3. Rule CM3-b: reliability contracts <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | F.2.4.4. Rule CM3-c: duplicate elimination F.2.4.5. Rule CM3-d: Use of sequences and sequence numbers F.2.4.6. Rule CM3-e: message ordering F.2.4.7. Rule CM3-f: expiration timeout F.2.5. (CM4) MEP mapping rules F.2.5.1. General <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | F.2.5.2. Rule CM4-a: One-Way\/Push with no signals F.2.5.3. Rule CM4-b: One-Way\/Push with signals F.2.5.4. Rule CM4-c: Two-Way\/Sync with no signals F.2.5.5. Rule CM4-d: Two-Way\/Sync with signals F.2.5.6. Rule CM4-e: Two-Way\/Push-and-Push <\/td>\n<\/tr>\n | ||||||
123<\/td>\n | F.2.6. (CM5) Signal mapping rules F.2.6.1. Rule CM5-a: Error metadata mapping F.2.6.2. Rule CM5-b: Error value mapping <\/td>\n<\/tr>\n | ||||||
124<\/td>\n | F.2.6.3. Rule CM5-c: ping and pong services <\/td>\n<\/tr>\n | ||||||
125<\/td>\n | F.2.7. (CM6) Processing mode mapping rules <\/td>\n<\/tr>\n | ||||||
126<\/td>\n | Annex G. (informative) Conformance <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Electronic business eXtensible Markup Language (ebXML) – Messaging service core specification<\/b><\/p>\n |