{"id":352193,"date":"2024-10-20T00:51:12","date_gmt":"2024-10-20T00:51:12","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-iso-iec-15944-12011\/"},"modified":"2024-10-26T00:49:38","modified_gmt":"2024-10-26T00:49:38","slug":"bs-iso-iec-15944-12011","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-iso-iec-15944-12011\/","title":{"rendered":"BS ISO\/IEC 15944-1:2011"},"content":{"rendered":"

The Open-edi Reference Model (ISO\/IEC 14662:2010, Clause 4) states:<\/p>\n

\n

“The intention is that the sending, by an Open-edi Party, of information from a scenario, conforming to Open-edi standards, shall allow the acceptance and processing of that information in the context of that scenario by one or more Open-edi Parties by reference to the scenario and without the need for agreement. However, the legal requirements and\/or liabilities resulting from the engagement of an organization in any Open-edi transaction may be conditioned by the competent legal environment(s) or the formation of a legal interchange agreement between the participating organizations. Open-edi Parties need to observe rule-based behaviour and possess the ability to make commitments in Open-edi (e.g., business, operational, technical, legal, and\/or audit perspectives).”<\/i><\/p>\n<\/blockquote>\n

This part of ISO\/IEC 15944 addresses the fundamental requirements of the commercial and legal frameworks and their environments on business transactions, and also integrates the requirements of the information technology and telecommunications environments.<\/p>\n

In addition to the existing strategic directions of “portability” and “interoperability”, the added strategic direction of ISO\/IEC JTC 1 of “cultural adaptability” is supported in this part of ISO\/IEC 15944. It also supports requirements arising from the public policy\/consumer environment, cross-sectorial requirements and the need to address horizontal issues.12)<\/sup> It integrates these different sets of requirements. See Figure 3.<\/p>\n

This part of ISO\/IEC 15944 allows constraints [which include legal requirements, commercial and\/or international trade and contract terms, public policy (e.g. privacy\/data protection, product or service labelling, consumer protection), laws and regulations] to be defined and clearly integrated into Open-edi through the BOV. This means that terms and definitions in this part of ISO\/IEC 15944 serve as a common bridge between these different sets of business operational requirements, allowing the integration of code sets and rules defining these requirements to be integrated into business processes electronically.<\/p>\n

This part of ISO\/IEC 15944 contains a methodology and tool for specifying common business practices as parts of common business transactions in the form of scenarios, scenario attributes, roles, Information Bundles and Semantic Components. It achieves this by 1) developing standard computer processable specifications of common business rules and practices as scenarios and scenario components; and thus 2) maximizing the re-use of these components in business transactions.<\/p>\n

PDF Catalog<\/h4>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PDF Pages<\/th>\nPDF Title<\/th>\n<\/tr>\n
15<\/td>\nPurpose and overview <\/td>\n<\/tr>\n
17<\/td>\nRequirements on the business operational view aspects of Ope <\/td>\n<\/tr>\n
19<\/td>\nBusiness operational view (BOV), Open-edi and e-commerce, e- <\/td>\n<\/tr>\n
20<\/td>\nUse of \u201cPerson\u201d, \u201cperson\u201d, and \u201cparty\u201d in the context of bus <\/td>\n<\/tr>\n
21<\/td>\nOrganization and description of the document
Registration aspects of Open-edi scenarios, scenario attribu <\/td>\n<\/tr>\n
23<\/td>\nScope <\/td>\n<\/tr>\n
24<\/td>\nNormative references
Terms and definitions\ufffd) <\/td>\n<\/tr>\n
34<\/td>\nSymbols and abbreviated terms
Characteristics of Open-edi <\/td>\n<\/tr>\n
35<\/td>\nActions based on following clear, predefined rules
Commitment of the parties involved
Communications among parties are automated
Parties control and maintain their states <\/td>\n<\/tr>\n
36<\/td>\nParties act autonomously
Multiple simultaneous transactions can be supported
Components of a business transaction\ufffd)
Introduction
Overview <\/td>\n<\/tr>\n
37<\/td>\nStandard based on rules and guidelines <\/td>\n<\/tr>\n
38<\/td>\nBusiness transaction: commitment exchange added to informati <\/td>\n<\/tr>\n
42<\/td>\nBusiness transaction: unambiguous identification of entities\ufffd) <\/td>\n<\/tr>\n
45<\/td>\nBusiness transaction model: key components
Business transaction model: classes of constraints <\/td>\n<\/tr>\n
48<\/td>\nRules governing the Person component\ufffd)
Introduction
Person, personae, identification and Person signature\ufffd) <\/td>\n<\/tr>\n
53<\/td>\nPerson – identity and authentication <\/td>\n<\/tr>\n
56<\/td>\nPerson and roles: buyer and seller <\/td>\n<\/tr>\n
57<\/td>\nPerson and delegation to \u201cagent\u201d and\/or \u201cthird party” <\/td>\n<\/tr>\n
58<\/td>\nPerson and external constraints: the “regulator”
Person and external constraints: individual, organization, a <\/td>\n<\/tr>\n
62<\/td>\nPerson and external constraints: consumer and vendor <\/td>\n<\/tr>\n
63<\/td>\nRules governing the process component\ufffd)
Introduction <\/td>\n<\/tr>\n
64<\/td>\nPlanning <\/td>\n<\/tr>\n
65<\/td>\nIdentification
Negotiation <\/td>\n<\/tr>\n
66<\/td>\nActualization\ufffd)
Post-actualization <\/td>\n<\/tr>\n
67<\/td>\nRules governing the data component\ufffd)
Recorded information <\/td>\n<\/tr>\n
69<\/td>\nPredefined and structured data elements <\/td>\n<\/tr>\n
72<\/td>\nBusiness requirements on the FSV (Business demands on Open-Edi Support Infrastructure)\ufffd)
Introduction <\/td>\n<\/tr>\n
73<\/td>\nInternal constraints (self-imposed) <\/td>\n<\/tr>\n
74<\/td>\nExternal constraints <\/td>\n<\/tr>\n
75<\/td>\nBOV requirements on the FSV for security methods and techniq
Liability of repositories\ufffd) <\/td>\n<\/tr>\n
76<\/td>\nPrimitive classification and identification of Open-edi scenarios\ufffd)
Introduction
Classification of Open-edi scenarios
Requirements for classification of Open-edi scenarios <\/td>\n<\/tr>\n
77<\/td>\nMarket type on business boundary
Settlement type in business process
Roles in business transactions: primitive or complex <\/td>\n<\/tr>\n
78<\/td>\nTrade models based on three classification factors
Trade models by market type: defined and undefined <\/td>\n<\/tr>\n
79<\/td>\nTrade models by settlement type: immediate and separate <\/td>\n<\/tr>\n
80<\/td>\nTrade models by participation type: bilateral and mediated
Classification and scenario types of Open-edi scenarios
Classification on Open-edi scenarios <\/td>\n<\/tr>\n
81<\/td>\nScenario types
Basic primitive trade scenario: (a) <\/td>\n<\/tr>\n
82<\/td>\nBasic complex trade scenario: (b)
Defined primitive trade scenario: (i)
Defined complex trade scenario: (j) <\/td>\n<\/tr>\n
83<\/td>\nPrimitive agreement scenario: (c)
Defined primitive agreement scenario: (k)
Complex agreement scenario: (g) <\/td>\n<\/tr>\n
84<\/td>\nDefined complex agreement scenario: (m)
Separate delivery scenario: (d)
Separate payment scenario: (e)
Authentication scenario: (f) <\/td>\n<\/tr>\n
85<\/td>\nDefined authentication scenario: (l)
Remarks on scenario classification
Continuous transaction:
Services transaction:
Auction transaction:
Bidding transaction:
Credit payment transaction:
Regulatory constraints: <\/td>\n<\/tr>\n
86<\/td>\nGuidelines for scoping Open-edi scenarios
Introduction and basic principles\ufffd) <\/td>\n<\/tr>\n
87<\/td>\nRules for scoping Open-edi scenarios <\/td>\n<\/tr>\n
89<\/td>\nTemplate for specifying scope of an Open-edi scenario
Introduction to template <\/td>\n<\/tr>\n
90<\/td>\nTemplate\ufffd) <\/td>\n<\/tr>\n
93<\/td>\nRules for specification of Open-edi scenarios and their comp
Introduction and basic principles <\/td>\n<\/tr>\n
96<\/td>\nOES demands on interoperability <\/td>\n<\/tr>\n
97<\/td>\nRules for specification of Open-edi scenarios and scenario a
Open-edi scenario rules
Open-edi scenario (OeS) attributes and associated rules <\/td>\n<\/tr>\n
98<\/td>\nScenario attribute: OeS identifier
Scenario attribute: OeS name(s) <\/td>\n<\/tr>\n
99<\/td>\nScenario attribute: OeS purpose
Scenario attribute: OeS set of roles
Scenario attribute: OeS set of Information Bundles
Scenario attribute: OeS set of requirements on Open-edi Part <\/td>\n<\/tr>\n
100<\/td>\nScenario attribute: OeS set of external constraints on busin
Scenario attribute: OeS inheritance identifier(s) and cross-
Scenario attribute: OeS security service requirements <\/td>\n<\/tr>\n
101<\/td>\nScenario attribute: OeS communication – quality of service r
Scenario attribute: OeS role requirements and constraints
Scenario attribute: OeS dependency among roles in a scenario
Scenario attribute: OeS dependency among Information Bundles
Scenario attribute: OeS dependency among Semantic Components
Scenario attribute: OeS demands on Open-edi Parties <\/td>\n<\/tr>\n
102<\/td>\nScenario attribute: OeS demands on Open-edi infrastructure
Rules for specification of Open-edi roles and role attribute
Rules governing roles <\/td>\n<\/tr>\n
103<\/td>\nRole attributes and associated rules <\/td>\n<\/tr>\n
104<\/td>\nRole attribute: role identifier (ID)
Role attribute: role name(s)
Role attribute: role purpose <\/td>\n<\/tr>\n
105<\/td>\nRole attribute: role business goal(s)
Role attribute: role business rules and constraints
Role attribute: role inheritance identifiers and cross-refer <\/td>\n<\/tr>\n
106<\/td>\nRole attribute: role external constraints on business requir
Role attribute: role security service requirements <\/td>\n<\/tr>\n
107<\/td>\nRole attribute: role communications and quality of service r
Role attribute: Role demands on Open-edi Support Infrastruct
Role demands on Open-edi Parties <\/td>\n<\/tr>\n
108<\/td>\nInteroperability demands among roles
Role states
Role transitions <\/td>\n<\/tr>\n
109<\/td>\nRole events <\/td>\n<\/tr>\n
110<\/td>\nRole actions
Role internal function
Role demand on Open-edi Support Infrastructure (OeSI) <\/td>\n<\/tr>\n
111<\/td>\nRules for specification of Open-edi Information Bundles (IBs
Rules governing Information Bundles (IBs) <\/td>\n<\/tr>\n
112<\/td>\nInformation Bundle (IB) attributes and associated rules
Information Bundle attribute: IB identifier
Information Bundle attribute: IB name(s) <\/td>\n<\/tr>\n
113<\/td>\nInformation Bundle attribute: IB purpose
Information Bundle attribute: business rules controlling con
Information Bundle attribute: IB external constraints on bus
Information Bundle attribute: IB contents
Information Bundle attribute: IB security service requiremen <\/td>\n<\/tr>\n
114<\/td>\n Information Bundle attribute: IB recorded information retent
Information Bundle attribute: IB time validity characteristi <\/td>\n<\/tr>\n
115<\/td>\nIB information for interoperability
IB demands on Open-edi Support Infrastructure (OeSI)
Rules for the specification of Semantic Components and Seman
Rules governing Semantic Components <\/td>\n<\/tr>\n
117<\/td>\nRules governing Semantic Component attributes
Semantic Component attribute: SC identifier
Semantic Component attribute: SC name(s)
Semantic Component attribute: SC definition <\/td>\n<\/tr>\n
118<\/td>\nSemantic Component attribute: SC security service requiremen
Business requirements on FSV (business demands on Open-edi S <\/td>\n<\/tr>\n
119<\/td>\nPrimitive Open-edi scenario template
Purpose
Template structure\ufffd) and content <\/td>\n<\/tr>\n
120<\/td>\nIT-interface needs perspective\ufffd)
Human interface needs perspective\ufffd)
Consolidated template of attributes of Open-edi scenarios, r <\/td>\n<\/tr>\n
123<\/td>\nRequirements on Open-edi description techniques
General requirements on Open-edi description techniques <\/td>\n<\/tr>\n
124<\/td>\nRequirements on OeDTs for roles <\/td>\n<\/tr>\n
125<\/td>\nRequirements on OeDTs for Information Bundles <\/td>\n<\/tr>\n
126<\/td>\nReferences <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

Information technology. Business operational view – Operational aspects of Open-edi for implementation<\/b><\/p>\n\n\n\n\n
Published By<\/td>\nPublication Date<\/td>\nNumber of Pages<\/td>\n<\/tr>\n
BSI<\/b><\/a><\/td>\n2011<\/td>\n318<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":352200,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[698,2641],"product_tag":[],"class_list":{"0":"post-352193","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-35-240-60","7":"product_cat-bsi","9":"first","10":"instock","11":"sold-individually","12":"shipping-taxable","13":"purchasable","14":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/352193","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/352200"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=352193"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=352193"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=352193"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}