ISO/IEC 10728:1993/Amd 3:1996

Information technology — Information Resource Dictionary System (IRDS) Services Interface — Amendment 3: CORBA IDL binding

Replaces the wording of some clauses and subclauses of ISO/IEC 10728:1993 and adds a new annex E.

Technologies de l'information — Interface de services du gestionnaire de ressources du système d'informations (IRDS) — Amendement 3: Liaison CORBA IDL

General Information

• Status: Published
• Publication Date: 25-Dec-1996
• ICS: 35.240.01 - Application of information technology in general
• Technical Committee: ISO/IEC JTC 1/SC 32 - Data management and interchange
• Drafting Committee: ISO/IEC JTC 1/SC 32/WG 2 - MetaData
• Current Stage: 6060 - International Standard published
• Completion Date: 26-Dec-1996

Relations

• Amends: ISO/IEC 10728:1993 - Information technology — Information Resource Dictionary System (IRDS) Services Interface
• Effective Date: 06-Jun-2022
• Child: ISO/IEC 10728:1993 - Information technology — Information Resource Dictionary System (IRDS) Services Interface
• Effective Date: 15-Apr-2008
• Consolidated By: ISO 945-1:2008 - Microstructure of cast irons — Part 1: Graphite classification by visual analysis
• Effective Date: 06-Jun-2022

Standards Content (Sample)

ISO/IEC
INTERNATIONAL
10728
STANDARD
First edition
1993-04-I 5
AMENDMENT 3
1996-l 2-l 5
Information technology - Information
Resource Dictionary System (IRDS)
Services Interface
AMENDMENT 3: CORBA IDL binding
Technologies de /‘information - Interface de services du gestionnaire de
ressources du systkme d ’informations (IRDS)
AMENDEMENT3: Liaison CORBA IDL
Reference number
ISO/l EC 10728: 1993/Amd.3: 1996(E)

---------------------- Page: 1 ----------------------
ISO/IEC 10728: 1993/Amd.3: 1996(E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the Inter-
national Electrotechnical Commission) form the specialized system for worldwide
standardization. National bodies that are members of IS0 or IEC participate in the
development of International Standards through technical committees established
by the respective organization to deal with particular fields of technical activity.
IS0 and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with
IS0 and IEC, also take part in the work.
In the field of information technology, IS0 and IEC have established a joint
technical committee, ISO/IEC JTC 1. Draft International Standards adopted by the
joint technical committee are circulated to national bodies for voting. Publication
as an International Standard requires approval by at least 75 % of the national
bodies casting a vote.
Amendment 3 to International Standard ISO/IEC 10728:1993 was prepared by
Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 21, Open systems interconnection, data management and open
distributed processing.
0 ISO/IEC 1996
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or
utilized in any form or by any means, electronic or mechanical, including photocopying and micro-
film, without permission in writing from the publisher.
ISO/IEC Copyright Office l Case postale 56 l CH-1211 Geneve 20 l Switzerland
Printed in Switzerland

---------------------- Page: 2 ----------------------
0 ISO/IEC ISO/IEC 10728: 1993/Amd.3: 1996(E) ’
- Information Resource Dictionary
Information technology
System (IRDS) Services Interface
AMENDMENT 3: CORBA IDL binding
Page v
Contents
Add a new entry to the Table of Contents as follows:
“Annex E - CORBA IDE binding”
Page 1
Clause 1
Add a new sentence in Clause 1 paragraph 2, before the last sentence.
“A language binding for CORBA IDL is provided in Annex E.”
Page 5
Subclause 4.4
Add a new sentence in subclause 4.4.
“Data structures for use with COMA IDL are defined in Annex E.”
Page 5
Subclause 4.5
Add a new sentence in subclause 4.5.
“CORBA IDL b’ m d’ mgs for the services are provided in Annex E.”
Page 71
Subclause 8.1
Amend the first sentence of the NOTE in clause 8.1 to read:
“For the Pascal language binding specified in this clause, the C language binding specified in
Annex C, the Ada language binding specified in Annex D and the CORBA IDL binding specified
in Annex E, enumerated types are . . . ‘I
Page 75
Clause 9
Amend the first sentence of the second paragraph of Clause 9 to read:
“The service formats are specified in this clause using IS0 standard Pascal. Alternative service
formats for use with the C language binding are specified in Annex C, for the Ada language
binding in Annex D and the CORBA IDE, binding in Annex E.”
1

---------------------- Page: 3 ----------------------
0 ISO/IEC
ISO/IEC 10728: 1993/Amd.3: 1996(E)
Add a new Annex E as follows:

---------------------- Page: 4 ----------------------
ISO/IEC 10728: 1993/Amd.3: 1996(E)
0 ISO/IEC
Annex E
(normative)
CORBA IDL Binding
The IRDS Services Interface language bindings for the CORBA Interface Definition Language are
presented in the form of a .idl file as set out in clause E.4 below.
E. 1 Strategy for the Language Binding
In this binding the data names and data structures defined in clause 8 have been adhered to except where
the CORBA IDL does not provide an appropriate construct.
In this binding the proccdurc names and their parameters defined in clause 8 have been adhered to except
where the CORBA IDL does not provide an appropriate construct.
‘or various limits instead because CORBA IDL compilers will not
#define statements have been used 1 of
accept a as an array leng th specifier.
Use of this language bindin, ~7 requires the USC of a CORBA IDL compiler that conforms to ISO/IEC
{Editor to insert reference] level (Editor to insert level identification).
E. 2 Class Architecture
The following class architecture is proposed. Note that these are only the classes that wed to be
visible across the CORBA intcrfacc. A finci grained class structure may be appropriate in future, but
that this probably ought to be a starting point. Moving to further classes such as IRDDefinition, IRD,
WorkingSet and IRDObjcct would be a natural next step and not inconsistent with the objects defined
.
below.
Class Services 10728 Clause
Refer ence
IrdsServiccsIntcrfaccPr-occssoi IrdsCreateIRDDefinition
9.1.1
IrdsDropIRDDefinition
9.1.2
IrdsOpen
9.1.3
IrdsPrcpare
IrdsScssion 9.1.4
IrdsCommit 9.1.5
IrdsRollback
9.1.6
IrdsClose
9.1.7
IrdsGetDiagnostics
9.1.8
IrdsSetContext 9.2.1
IrdsAddObject
9.2.2
IrdsOpenCursoi
9.2.3

---------------------- Page: 5 ----------------------
0 ISO/IEC
ISO/IEC 10728: 1993/Amd.3: 1996(E)
Services 10728 Clause
Class Name
Reference
IrdsSession (continued)
IrdsRetrieveObject 9.2.4
9.2.5
IrdsModifyObject
9.2.6
IrdsDeleteObject
IrdsDeclassifyObject 9.2.7
IrdsReclassify 9.2.8
9.2.9
IrdsCloseCursor
9.2.10
IrdsCreateWorkingSet
IrdsDropWorkingSet 9.2.1 I
IrdsModifyContentStatus 9.2.12
IrdsCreateReferencePath 9.2.13
IrdsModifyReferencePath 9.2.14
IrdsDropReferencePath 9.2.15
IrdsCreateIRD 9.3.1
IrdsDropIRD 9.3.2
IrdsDeactivateIRD 9.3.3
IrdsReac tivateIRD 9.3.4
IrdsVal idateIRDSchemaGroup 9.3.5
E.3 General Rules
1. Those data names in E.4 below that also appear in Clause 8 shall have the same meaning as is
defined in Clause 8. The same rules for the use of separators as defined in Clause 8 shall apply.
2. The function and parameter names in E.4 below shall have the same meaning as is defined in
Clause 9.
3. The Service Return Codes returned shall be those defined by Clause 9 and Annex A and they
shall have the same meaning.

---------------------- Page: 6 ----------------------
ISO/IEC 10728: 1993/Amd.3:1996(E)
0 ISO/IEC
The fi,llowing mappings fi-om SQL data types to CORBA IDL data types have been used:
4.
CORBA IDL DATA TYPE
SQL DATA TYPE
string /* See 8.2.1 */
CHARACTER
string /* See 8.2.1 */
CHARACTER VARYING
string /* See 8.2.1 *l
NATIONAL CHARACTER
string /* See 8.2.1 */
mTIONAL CHARACTERVARYING
float
double
D3UBLE PRECISION
float
F'LOAT
long
LIINTEGER
short
bsJwLLINT
long
NUMEEU-C
long
DEclMAL
/* See 8.2.1 */
Ird.sI&te
DATE
/* See 8.2.1 */
IrdsTirne
TIME
IrdsTimeStamp /* See 8.2.1 */
TIMESTW
IrdsInterval /* See 8.2.1 */
lLIJmTRs?AL
s 5 . Every function returns an int which is to be set to the value of the NumStates field of the
R&ode rcturncd by the function.
E. 4. IDL Interface Definition
The following is the IDL interface definition for the object classes set out in clause E. 1.
module irds
{
/* Clause 8.1.1 */
*
tl */
/
const short IrdsNarneLim = 255
*/
/* IrdsNameLim is used in 8.2.2 below
3;
t2 */
/
const short IrdsVarLim = 255
*
/
/* IrdsVxLim is used in 8.2.2 below

---------------------- Page: 7 ----------------------
0 TSO/IEC
ISO/IEC 10728: 1993/Amd.3: 1996(E)
/* Clause 8.1.2 */
*
t3 */
const short IrdsTextLim = 30728 /
*
Note that although no use is made of IrdsTextLim in this
/
it is included so that a program may
language binding,
refer
to the value to test the length of a string. */
these definitions are used in 8.2.3 below */
/* Clause 8.1.3 -
*
The numeric values in this clause will be
/
n2, n3, n4 as in clause 8.1.3 in
replaced @ nl,
Actual values
the final version of this Annex.
are retained in this draft to facilitate testing
of the text by corrrpilation against a range of
cowilers. *l
* nl*/
/
const short IrdsSessIdLim = 255;
*
/
/* IrdsSessIdLim used in 8.2.3 below
* n2 *
/ /
const short ~rdsCu.rIdLirn = 255;
/* IrdsCurIdLim used in 8.2.3 below */
/ * n3 */
short IrdsIrrp?DicNameLen = 255;
const
/* IrdsmDicNameLen used in 8.2.3 below */
*
n4 */
short IrdsKeyLen = 255; /
const
*/
/* IrdsKqLen used in 8.2.1 below
*/
/* Clause 8.1.4 Data Types
typedefenum
1
/* SQLCHARACTER /
IrdsDataTypeChar,
*/
/* SQL CHARACTER VARYING*
IrdsData?LpeCharVar,
*/
IrdsData?LpeNatChar, /* SQL NATIONAL CHARACTER
IrdsDataTypeNatCharVar,
*/
/* SQL NATIONAL CHARACTER VARYING
*
/
/* SQL REAL
IrdsDataTypeReal,
IrdsIBtaTypeIBuble,
/* SQL IBUBLE PRECISION */
*
/* SQL FLQAT /
IrdsDataTypeFloat,
*
/
/* SQL INTEGER
Ird.sData?LpeInteger,
*
/
/* SQLSMALLINT
IrdsDataTypeSmallint,
*
/
/* SQL NUMERIC
IrdsI&ta?LpeDJumeric,
*
/
/* SQL DEUMAL
IrdsDataTypeIXcirnal,
*
/
/* SQL DATE
IrdsDataTypeDate,
*
/
/* SQL TIME
IrdsIBtaTypeTime,
*
/
/* SQLTIMESTAMP
IrdsDataTypeTimestamp,
*
/
/* SQL INTERVAL
IrdsDataTypeInterva1,
*
/
/* SQL IRDS KEY
IrdsDataTypeIrdsKey
} IrdsIXtaType;

---------
...