1、B CReference numberISO/IEC 13235-3:1998(E)INTERNATIONALSTANDARDISO/IEC13235-3First edition1998-12-01Information technology Open DistributedProcessing Trading Function Part 3:Provision of Trading Function using OSIDirectory serviceTechnologies de linformation Traitement distribu ouvert Fonctioncommer
2、ciale Partie 3: Fourniture de fonction commerciale utilisant le service dannuaireOSIAdopted by INCITS (InterNational Committee for Information Technology Standards) as an American National Standard.Date of ANSI Approval: 11/25/2002Published by American National Standards Institute,25 West 43rd Stree
3、t, New York, New York 10036Copyright 2002 by Information Technology Industry Council (ITI).All rights reserved.These materials are subject to copyright claims of International Standardization Organization (ISO), InternationalElectrotechnical Commission (IEC), American National Standards Institute (A
4、NSI), and Information Technology Industry Council(ITI). Not for resale. No part of this publication may be reproduced in any form, including an electronic retrieval system, withoutthe prior written permission of ITI. All requests pertaining to this standard should be submitted to ITI, 1250 Eye Stree
5、t NW,Washington, DC 20005.Printed in the United States of AmericaISO/IEC 13235-3:1998(E) ISO/IEC 1998All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic ormechanical, including photocopying and microfilm,
6、without permission in writing from the publisher.ISO/IEC Copyright Office Case postale 56 CH-1211 Genve 20 SwitzerlandPrinted in SwitzerlandiiContents Page1 Scope and field of application. 12 Normative References. 12.1 Identical Recommendations | International Standards. 13 Definitions. 24 Abbreviat
7、ions 45 Overview. 46 Schema 56.1 General. 66.2 Trader Entry. 76.2.1 commonName. 76.2.2 traderInterface. 86.2.3 dsaName . 86.2.4 typeRepos . 86.2.5 defSearchCard. 86.2.6 maxSearchCard. 86.2.7 defMatchCard . 96.2.8 maxMatchCard 96.2.9 defReturnCard. 96.2.10 maxReturnCard. 96.2.11 defHopCount. 106.2.12
8、 maxHopCount. 106.2.13 defFollowPolicy 106.2.14 maxFollowPolicy 116.2.15 maxLinkFollowPolicy 116.2.16 supportsModifiableProperties. 116.2.17 supportsDynamicProperties 116.2.18 supportsProxyOffers . 126.2.19 maxList . 126.2.20 requestIdStem . 126.2.21 description. 126.2.22 userPassword 126.2.23 Other
9、 X.500 attributes. 126.3 Trader Policy Entry . 136.3.1 commonName. 136.3.2 typeManagementConstraint 136.3.3 searchConstraint 146.3.4 offerAcceptanceConstraint . 146.3.5 Other X.500 attributes. 14 ISO/IEC ISO/IEC 13235-3:1998(E)iiiPage6.4 Service Offer Entry . 146.4.1 sOfferId 156.4.2 serviceInterfac
10、eId . 166.4.3 serviceTypeId . 166.4.4 hasDynamicProperties 166.4.5 hasModifiableProperties. 176.4.6 dynamicProps . 176.4.7 Other X.500 attributes 176.5 Trader Link Entry 186.5.1 linkName 186.5.2 linkId 186.5.3 targetTraderInterfaceId. 196.5.4 defPassOnFollowRule 196.5.5 limitingFollowRule. 196.5.6 O
11、ther X.500 attritubes 196.6 Proxy Offer Entry 206.6.1 proxyOfferId. 206.6.2 proxyLookUpInterfaceId 216.6.3 constraintRecipe . 216.6.4 ifMatchAll 216.6.5 Other X.500 attributes 216.7 Other X.500 entries used by the T-DUA. 227 Operations. 227.1 Initialisation. 237.2 Client operations 237.3 Register op
12、erations 237.3.1 Export . 237.3.2 Withdraw 257.3.3 Modify 257.3.4 Describe 267.3.5 Withdraw with constraint . 267.3.6 Resolve . 277.4 Look up operations 277.4.1 Query operation 277.4.2 Policies . 287.4.3 Searching locally 287.4.4 Searching Federated Traders 297.4.5 Searching Proxy Offers 297.4.6 Ser
13、vice Offer returned 297.5 Link operations 297.5.1 Add Link. 297.5.2 Remove Link 307.5.3 Modify Link . 307.5.4 Describe Link . 317.5.5 List Links 317.6 Proxy Offer operations 317.6.1 Export Proxy. 317.6.2 Withdraw Proxy 327.6.3 Describe Proxy . 33ISO/IEC 13235-3:1998(E) ISO/IECivPage7.7 Trader Attrib
14、ute Operations. 337.8 Administrative operations 337.8.1 List Offers. 337.8.2 List Proxies . 347.9 Dynamic Property Evaluation operations 347.9.1 EvalDP 348 Type Repository 358.1 X.500 schema and the Minimal Type Repository .359 Dynamic Properties. 369.1 Exporting a Service Offer 369.2 Importing a Se
15、rvice Offer 36Annex A Trader definitions schema definition . 37Annex B Sample service description schema definition . 47 ISO/IEC ISO/IEC 13235-3:1998(E)vForewordISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) formthe specialized system
16、 for worldwide standardization. National bodies that are members of ISO or IEC participate in thedevelopment of International Standards through technical committees established by the respective organization to dealwith particular fields of technical activity. ISO and IEC technical committees collab
17、orate in fields of mutual interest.Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in thework.In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. DraftInternational Standard
18、s adopted by the joint technical committee are circulated to national bodies for voting. Publicationas an International Standard requires approval by at least 75 % of the national bodies casting a vote.International Standard ISO/IEC 13235-3 was prepared by Joint Technical Committee ISO/IEC JTC 1, In
19、formationtechnology, Subcommittee SC 33, Distributed application services, in collaboration with ITU-T. The identical text ispublished as ITU-T Recommendation X.952.ISO/IEC 13235-3 consists of the following parts, under the general title Information technology Open DistributedProcessing Trading Func
20、tion: Part 1: Specification Part 2: (TBD) Part 3: Provision of Trading Function using OSI Directory serviceAnnex A forms an integral part of this part of ISO/IEC 13235. Annex B is for information only.vi,QWURGXFWLRQThe ODP Trading Function (see ITU-T Rec. X.950-Series | ISO/IEC 13235) provides the m
21、eans to offer a service andthe means to discover services that have been offered. ITU-T Rec. X.950 | ISO/IEC 13235-1 defines an enterpriseSpecification, an information Specification and a computational Specification of this Trading Function. No engineeringSpecification is defined in ITU-T Rec. X.950
22、 | ISO/IEC 13235-1. This Recommendation | International Standarddescribes how the Specifications of the Trading Function in ITU-T Rec. X.950 | ISO/IEC 13235-1 can be engineeredusing OSI Directory Service (see ITU-T Rec. X.500 | ISO/IEC 9594-1) to store information and to provide supportmechanisms. T
23、his Specification does not prescribe that a trader must be engineered by using OSI Directory. But if OSIDirectory is used, this Specification defines standardised templates for information entries (e.g. service offer and linkinformation objects) in the Directory DIT.Clause 5 gives an overview of how
24、 the Trading Function is implemented as a combination of X.500 DUA and DSA. TheX.500 DSA is used to store the Trader Information Object and a Trader DUA (T-DUA) implements the functionalityrequired by a Trader, which is difficult, or impossible, to implement using OSI Directory services.Clause 6 def
25、ines the standardised templates for information entries of the Trader Information Object, the informationknown to a particular Trader.Clause 7 describes mapping of Trading Function operations to appropriate Directory operations.Clause 8 specifies a minimal Type Repository Function necessary to enabl
26、e the correct functioning of the X.500Directory for Trading.Clause 9 describes the mechanisms used to enable the handling of dynamic properties of a Traders service offers.This Specification contains two annexes.Annex A is a normative schema definition of Trader definitions.Annex B is an informative
27、 schema definition of a sample service description.ISO/IEC 13235-3:1998(E) ISO/IECAAAAAAAA,62 ,( ( 1,17(51$7,21$/ 67$1$5ISO/IEC 13235-3 : 1998 (E)ITU-T Rec. X.952 (1997 E),78 7 5( trading; type; viewpoint._1)To be published.Notation One (ASN.1): Parameterization of ASN.1 specifications. Information
28、technology_Abstract,62 ,( ( 3This Recommendation | International Standard makes use of the following terms defined in ITU-T Rec. X.903 |ISO/IEC 10746-3: administrator; community; computational viewpoint; engineering interface reference; engineering viewpoint; enterprise viewpoint; exporter; importer
29、; information viewpoint; service export; service import; service offer; technology viewpoint; Trading Function; Type Repository Function.This Recommendation | International Standard makes use of the following terms defined in ITU-T Rec. X.950 |ISO/IEC 13235-1: federated traders; iterator; link; prox
30、y offer; service type; service property; trader; trader attribute; trading graph.This Recommendation | International Standard makes use of the following terms defined in ITU-T Rec. X.500 |ISO/IEC 9594-1: Directory; Directory Information Base; (Directory) User.This Recommendation | International Stan
31、dard makes use of the following terms defined in ITU-T Rec. X.501 |ISO/IEC 9594-2: attribute; attribute type; attribute value; Directory Information Tree; Directory System Agent; Directory User Agent; distinguished name; (Directory) entry; filter;,62 ,( ( matching rule; (Directory) name; name form;
32、object; object class; object entry; relative distinguished name; structure rule; subclass; subordinate; superclass.This Recommendation | International Standard makes use of the following operations defined in ITU-T Rec. X.511 |ISO/IEC 9594-3: addEntry; modifyEntry; read; removeEntry; search.This Rec
33、ommendation | International Standard makes use of the following terms defined in ITU-T Rec. X.509 |ISO/IEC 9594-8: authentication; password.$EEUHYLDWLRQVFor the purposes of this Recommendation | International Standard, the following abbreviations apply:DIB Directory Information BaseDIT Directory Inf
34、ormation TreeDN Distinguished NameDSA Directory System AgentDUA Directory User AgentODP Open Distributed ProcessingOID Object IdentifierRDN Relative Distinguished NameT-DUA Trader Directory User Agent2YHUYLHZIn this Specification, the Trading Function is implemented as a combination of X.500 DUA and
35、 DSA. As far aspossible, the features of X.500 are used to directly implement the Trading Function, but not all Trader features can bedirectly supported by X.500. For this reason, the Trader (the object that provides the Trading Function) is composed oftwo components: an X.500 Directory which stores
36、 the Trader Information and a Trader DUA (T-DUA) whichimplements the functionality required by a Trader which is difficult, or impossible, to implement in X.500. The X.500Directory is used to store the Trader Information Object. Requests from trader clients (importers and exporters) aremapped into o
37、perations on the X.500 database. Figure 1 shows the components of a Trader and its interactions with itsclients.,62 ,( ( 5T0727990-97/d01Trader clientsTrader clientsTrader clientsT-DUATraderX.500DSADIT)LJXUH 7KH WUDGHU ZLWK LWV FRPSRQHQWV DQG FOLHQWVFIGURE 1/X.052.D01 = 7 CMThe T-DUA and the trader
38、clients (importers and exporters) communicate using a Trader protocol. The Trader protocolis not defined in this Specification. It may be any protocol which implements the functionality specified byITU-T Rec. X.950 | ISO/IEC 13235-1. The purpose of this Specification is to specify how the T-DUA uses
39、 an X.500Directory to support the functionality specified by ITU-T Rec. X.950 | ISO/IEC 13235-1.The information stored by the X.500 Directory comprises: The Trader Attributes (i.e. information about the Trader itself). The Trader Enterprise policies (i.e. rules to determine and guide Trader behaviou
40、r). The set of Service Offers (i.e. information used by Trader when acting as a server). The set of Trader Links (i.e. information used by Trader when acting as a client). The set of Proxy Offers (i.e. information used by Trader when acting as a server for Proxy Offers).X.500 is used to store this i
41、nformation for several reasons: The information model required by the ODP Trader is very similar to that provided by X.500. X.500 provides significant flexibility in allowing the definition of new X.500 attributes at runtime. It makes sense to use the existing investment in X.500 rather than to atte
42、mpt to create a completely newinfrastructure. It allows the Trader to use the general X.500 infrastructure to look up presentation addresses of linkedTraders and Clients, and to use the security features of X.500 to authenticate users.NOTE Details of how to provide the X.500 infrastructure and the s
43、ecurity features of X.500 for the TradingFunction are outside the scope of this Specification.It is not possible to implement an ODP Trader completely using X.500 because of the significant differences in theoperational model used by the ODP Trader. These include: The Trader operations that do not d
44、irectly map to X.500 operations. Distributed operations that are implemented using information stored in Trader Links and TraderAttributes whose meaning differ from the distribution implemented in X.500.6FKHPDThis X.500 schema describes the portion of an X.500 DIT used to store the information known
45、 to one Trader. Theschema is based on the X.500 Directory model and is given in Annex A.,62 ,( ( *HQHUDOThe information known to a particular Trader (the Trader Information Object) is kept in a subtree of the X.500 DIT.This subtree can be attached anywhere in the global DIT and no Structure Rules ar
46、e defined for controlling its position.It is expected that the Trader subtree would be commonly attached beneath organisational and organisational unit entries(representing, respectively, the information known to organisational and organisational unit Traders). The informationknown to each trader is
47、 kept separately in the DIT and no attempt is made to map the distribution model used in X.500to the very different distribution model of federated Traders.Trader Information is stored in the X.500 DIT as self contained parcels. Each parcel contains the information known toone Trader. In the example
48、 shown in Figure 2, there are two Traders: one for the organisation as a whole and a secondfor a unit within the organisation. Linkages between these two Traders is via the Trader protocol, not via X.500protocol.The Trader Information Object (see Figure 3) is composed of five types of entries: The T
49、rader Entry contains details about the Trader itself. The Trader Policy Entry contains details about the Trader enterprise policies. The Service Offer Entries contain details about the Service Offers known to the Trader. The Trader Link Entries contain details about the Links with other Traders. The Proxy Offer Entries contain details about the Proxy Offers known to the Trader.NOTE 1 The structuring of the Service Offers, Links,
