ISO/IEC 30106-2:2016
(Main)Information technology — Object oriented BioAPI — Part 2: Java implementation
Information technology — Object oriented BioAPI — Part 2: Java implementation
ISO/IEC 30106-2:2016 specifies an interface of a BioAPI Java framework and BioAPI Java BSP, which will mirror the corresponding components, specified in ISO/IEC 30106‑1. The semantic equivalent of this standard is maintained in this part of ISO/IEC 30106.
Technologies de l'information — Objet orienté BioAPI — Partie 2: Mise en oeuvre Java
General Information
Relations
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 30106-2
First edition
2016-03-15
Information technology — Object
oriented BioAPI —
Part 2:
Java implementation
Technologies de l’information — Objet orienté BioAPI —
Partie 2: Mise en oeuvre Java
Reference number
ISO/IEC 30106-2:2016(E)
©
ISO/IEC 2016
---------------------- Page: 1 ----------------------
ISO/IEC 30106-2:2016(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2016, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2016 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 30106-2:2016(E)
Contents Page
Foreword .vi
Introduction .vii
1 Scope . 1
2 Normative references . 1
3 BioAPI Java package structure . 1
3.1 Package org.bioapi . 1
3.1.1 Package description . 1
3.1.2 Structure . 1
3.2 Package org.bioapi.data . 2
3.2.1 Package description . 2
3.2.2 Structure . 2
4 Data types and constants . 2
4.1 Class ACBioParameters . 2
4.1.1 Description . . . 2
4.1.2 Method summary . 2
4.2 Class BFPListElement . . 2
4.2.1 Description . . . 2
4.2.2 Method summary . 3
4.3 Class BFPSchema. 3
4.3.1 Description . . . 3
4.3.2 Method summary . 3
4.4 Class BIR . 4
4.4.1 Description . . . 4
4.4.2 Method summary . 4
4.5 Class BSPSchema . 9
4.5.1 Description . . . 9
4.5.2 Method summary . 9
4.6 Class candidate .12
4.6.1 Description . . .12
4.6.2 Method summary .12
4.7 Class DataTypes .13
4.7.1 Description . . .13
4.7.2 Enumerations .14
4.8 Class date .20
4.8.1 Description . . .20
4.8.2 Method summary .21
4.9 Class FrameworkSchema .22
4.9.1 Description . . .22
4.9.2 Method summary .23
4.10 Class GUIBitmap .24
4.10.1 Description . . .24
4.10.2 Method summary .24
4.11 Class IdentifyPopulation .24
4.11.1 Description . . .24
4.11.2 Method summary .24
4.12 Class PopulationMember .25
4.12.1 Description . . .25
4.12.2 Method summary .25
4.13 Class RegistryID .25
4.13.1 Description . . .25
4.13.2 Method summary .25
4.14 Class SecurityProfileType .26
4.14.1 Description . . .26
© ISO/IEC 2016 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 30106-2:2016(E)
4.14.2 Method summary .26
4.15 Class UnitList .27
4.15.1 Description . . .27
4.15.2 Method summary .27
4.16 Class UnitListElement .27
4.16.1 Description . . .27
4.16.2 Method summary .27
4.17 Class UnitSchema .28
4.17.1 Description . . .28
4.17.2 Method summary .28
4.18 Class UUID .30
4.18.1 Description . . .30
5 Object oriented interfaces for supporting BioAPI_Units .30
5.1 General .30
5.2 Interface archive .30
5.2.1 Description . . .30
5.2.2 Method summary .31
5.3 Interface comparison .34
5.3.1 Description . . .34
5.3.2 Method summary .34
5.4 Interface processing .36
5.4.1 Description . . .36
5.4.2 Method summary .36
5.5 Interface sensor .37
5.5.1 Description . . .37
5.5.2 Method summary .38
6 BFP level .39
6.1 Interface BFP .39
6.1.1 Description . . .39
6.1.2 Imported interfaces .39
6.1.3 Method summary .40
7 BSP level .42
7.1 Interface BSP .42
7.1.1 Description . . .42
7.1.2 Imported interfaces .42
7.1.3 Method summary .42
8 Framework level .49
8.1 Interface ComponentRegistry .49
8.1.1 Description . . .49
8.1.2 Method summary .50
8.2 Interface framework .51
8.2.1 Description . . .51
8.2.2 Inherited interfaces .51
8.2.3 Method summary .52
9 Application interaction .56
9.1 class BioAPIException extends Exception .56
9.1.1 Description . . .56
9.1.2 Constructor summary .56
9.1.3 Method summary .57
9.2 GUI callback functions .57
9.2.1 Description . . .57
9.2.2 Callback interface specification .58
10 BSP Interaction .61
10.1 Interface BSPEventListener .61
10.1.1 Method summary .61
iv © ISO/IEC 2016 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 30106-2:2016(E)
11 BFP interaction .62
11.1 Interface BFPEnumerationListener .62
11.1.1 Method summary .62
11.2 Interface BFPEventListener .62
11.2.1 Method summary .62
11.3 Interface BFPGUIProgressEventListener .63
11.3.1 Method summary .63
Annex A (informative) Java requirements .64
Annex B (informative) Calling sequence examples and sample code .65
© ISO/IEC 2016 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC 30106-2:2016(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO 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. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work. In the field of information technology, ISO and IEC have established a joint technical committee,
ISO/IEC JTC 1.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for
the different types of document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical
Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/TC JTC1, Information technology, Subcommittee
SC 37, Biometrics.
ISO/IEC 30106 consists of the following parts, under the general title Information technology — Object
oriented BioAPI:
— Part 1: Architecture
— Part 2: Java implementation
— Part 3: C# implementation
vi © ISO/IEC 2016 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 30106-2:2016(E)
Introduction
In this part of ISO/IEC 30106, an application programming interface expressed in Java language is
specified. Java is intended to be a simple, general-purpose, object oriented programming language that
is aimed at enabling programmers to quickly build a wide range of applications for multiple platforms.
This Java implementation allows an easy use of Java BSPs, Java-based application servers or Java applets.
Therefore, it is the best way to write desktop and web applications/services and this specification
provides an advanced and well-designed remote framework.
Although the best practices of Java programming states that variables should be written in smallcase
letters, in the case of symbols, such as BSP or BFPs, it has been kept as uppercase letters.
© ISO/IEC 2016 – All rights reserved vii
---------------------- Page: 7 ----------------------
INTERNATIONAL STANDARD ISO/IEC 30106-2:2016(E)
Information technology — Object oriented BioAPI —
Part 2:
Java implementation
1 Scope
This part of ISO/IEC 30106 specifies an interface of a BioAPI Java framework and BioAPI Java BSP, which
will mirror the corresponding components, specified in ISO/IEC 30106-1. The semantic equivalent of
this standard is maintained in this part of ISO/IEC 30106.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 30106–1, Information technology — BioAPI for object oriented programming languages — Part 1:
Architecture
3 BioAPI Java package structure
The BioAPI Java interface will be divided into several packages. The following is the package structure:
— package org.bioapi: contains functionality to manage units, BSPs, BFPs, the Framework and
Applications;
— package org.bioapi.data: contains all the data structures.
3.1 Package org.bioapi
3.1.1 Package description
This package contains all the components responsible for managing and executing the functionality of
BioAPI. Component Registry interface is also defined in this package.
3.1.2 Structure
The description of this namespace is given explaining a bottom-up structure. In Clause 4, the interfaces
needed to be implemented for each of the Unit types are explained. It is important to note that such
interfaces do not refer to an implemented class by itself, as the accessible class will either be the
Biometric Service Provider (BSP) or the Biometric Function Provider (BFP), but the specifications in
such clause are common to the methods and properties to be added to the implemented BSP and/or BFP
classes.
This will be followed by the specification of the implementation of the BFP (Clause 5) and BSP (Clause 6)
interfaces. These two interfaces provide the lower layer interoperability level, equivalent to the SPI and
BFPI interfaces in ISO/IEC 19784-1.
The higher layer of interoperability level is provided by the specification of the Framework (Clause 7,
with the Framework Interface and the Component Registry) and the Application interaction (Clause 8,
© ISO/IEC 2016 – All rights reserved 1
---------------------- Page: 8 ----------------------
ISO/IEC 30106-2:2016(E)
with the specification of the Exceptions and Callback functions). This provides the equivalence to the
API interface in ISO/IEC 19784-1.
3.2 Package org.bioapi.data
3.2.1 Package description
This package contains all data structures needed for the implementation of OO BioAPI.
3.2.2 Structure
Several data structures are provided to comply with the requirements specified in this part of
ISO/IEC 30106. All the BioAPI.Data namespace is specified
...
DRAFT INTERNATIONAL STANDARD
ISO/IEC DIS 30106-2
ISO/IEC JTC 1/SC 37 Secretariat: ANSI
Voting begins on: Voting terminates on:
2014-12-04 2015-03-04
Information Technology — Object oriented BioAPI —
Part 2:
Java implementation
Titre manque
ICS: 35.040
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENT AND APPROVAL. IT IS
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/IEC DIS 30106-2:2014(E)
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
©
PROVIDE SUPPORTING DOCUMENTATION. ISO/IEC 2014
---------------------- Page: 1 ----------------------
ISO/IEC DIS 30106-2:2014(E)
Copyright notice
This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as
permitted under the applicable laws of the user’s country, neither this ISO draft nor any extract
from it may be reproduced, stored in a retrieval system or transmitted in any form or by any means,
electronic, photocopying, recording or otherwise, without prior written permission being secured.
Requests for permission to reproduce should be addressed to either ISO at the address below or ISO’s
member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Reproduction may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
ii © ISO 2014 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC DIS 30106-2
Contents Page
Foreword . xi
Introduction . xii
1 Scope . 1
2 BioAPI Java Package Structure . 1
2.1 Package org.bioapi . 1
2.1.1 Package description . 1
2.1.2 Structure . 1
2.2 Package org.bioapi.data . 2
2.2.1 Package description . 2
2.2.2 Structure . 2
3 Data types and constants . 3
3.1 Class ACBioParameters . 3
3.1.1 Description . 3
3.1.2 Method Summary . 3
3.1.2.1 int[] getChallenge() . 3
3.1.2.2 int[] getInitialBPUIOIndexOutput() . 3
3.1.2.3 int[] getSupremumBPUIOIndexOutput() . 3
3.2 Class BFPListElement . 3
3.2.1 Description . 3
3.2.2 Method Summary . 3
3.2.2.1 UUID getBFPID() . 3
3.2.2.2 UnitCategoryType getUnitCategory() . 4
3.2.2.3 void setBFPID(UUID bfpID) . 4
3.2.2.4 void setUnitCategory(UnitCategoryType unitCategory) . 4
3.3 Class BFPSchema . 4
3.3.1 Description . 4
3.3.2 Method Summary . 4
3.3.2.1 String getBFPDescription() . 4
3.3.2.2 Vector getBFPSupportedFormats() . 4
3.3.2.3 UUID getBFPUUID() . 4
3.3.2.4 Vector getFactorsMask() . 4
3.3.2.5 byte[] getFWProperty() . 5
3.3.2.6 UUID getFWPropertyID() . 5
3.3.2.7 String getPath() . 5
3.3.2.8 String getProductVersion() . 5
3.3.2.9 String getSpecVersion() . 5
3.3.2.10 UnitCategoryType getUnitCategory() . 5
3.3.2.11 String getVendor() . 6
3.4 Class BIR . 6
3.4.1 Description . 6
3.4.2 Method Summary . 6
3.4.2.1 void birFromByteArray(byte[] record) . 6
3.4.2.2 byte[] birToByteArray() . 6
3.4.2.3 void destroy() . 6
3.4.2.4 BiometricSubtype getBDBBiometricSubtype() . 6
3.4.2.5 BiometricType getBDBBiometricType(). 7
3.4.2.6 byte[] getBDBChallengeResponse() . 7
3.4.2.7 Date getBDBCreationDate() . 7
3.4.2.8 byte[] getBDBData() . 7
© ISO/IEC 2014 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC DIS 30106-2
3.4.2.9 RegistryID getBDBFormat() .7
3.4.2.10 byte[] getBDBIndex() .7
3.4.2.11 ProcessedLevel getBDBProcessedLevel() .7
3.4.2.12 Purpose getBDBPurpose() .7
3.4.2.13 byte getBDBQuality() .8
3.4.2.14 Vector getBDBValidityPeriod() .8
3.4.2.15 Date getBIRCreationDate() .8
3.4.2.16 byte[] getBIRCreator() .8
3.4.2.17 byte[] getBIRIndex() .8
3.4.2.18 byte[] getBIRAdditionalData() .8
3.4.2.19 Vector getBIRValidityPeriod() .8
3.4.2.20 byte getCBEFFVersion() .9
3.4.2.21 RegistryID getPatronFormat() .9
3.4.2.22 byte getPatronHeaderVersion().9
3.4.2.23 byte[] getSBData() .9
3.4.2.24 RegistryID getSBFormat() .9
3.4.2.25 boolean hasBDBEncription() .9
3.4.2.26 boolean hasBDBIntegrity() .9
3.4.2.27 boolean isBIRSigned() . 10
3.4.2.28 boolean isQualitySupported() . 10
3.4.2.29 boolean isQualityKnown() . 10
3.4.2.30 void setBDBBiometricSubtype(BiometricSubtype bdbBiometricSubtype) . 10
3.4.2.31 void setBDBBiometricType(BiometricType bdbBiometricType) . 10
3.4.2.32 void setBDBChallengeResponse(byte bdbChallengeResponse) . 10
3.4.2.33 void setBDBCreationDate(Date bdbCreationDate) . 10
3.4.2.34 void setBDBEncription(boolean bdbEncription) . 10
3.4.2.35 void setBDBFormat(RegistryID bdbFormat) . 10
3.4.2.36 void setBDBData(byte[] bdbData) . 11
3.4.2.37 void setBDBIndex(byte[] bdbIndex) . 11
3.4.2.38 void setBDBIntegrity(boolean bdbIntegrity) . 11
3.4.2.39 void setBDBQuality(byte bdbQuality) . 11
3.4.2.40 void setBDBProcessedLevel(ProcessedLevel bdbProcessedLevel) . 11
3.4.2.41 void setBDBPurpose(Purpose bdbPurpose) . 11
3.4.2.42 void setBDBValidityPeriod(Vector bdbValidityPeriod) . 11
3.4.2.43 void setBIRCreationDate(Date birCreationDate) . 11
3.4.2.44 void setBIRCreator(byte[] birCreator) . 12
3.4.2.45 void setBIRIndex(byte[] birIndex) . 12
3.4.2.46 void setBIRAdditionalData(byte[] birAdditionalData) . 12
3.4.2.47 void setBIRValidityPeriod(Vector birValidityPeriod) . 12
3.4.2.48 void setCBEFFVersion(byte cbeffVersion) . 12
3.4.2.49 void setPatronFormat(RegistryID patronFormat) . 12
3.4.2.50 void setPatronHeaderVersion(byte patronHeaderVersion) . 12
3.4.2.51 void setSBData(byte[] sbData) . 13
3.4.2.52 void setSBFormat(RegistryID sbFormat) . 13
3.5 Class BSPSchema . 13
3.5.1 Description . 13
3.5.2 Method Summary . 13
3.5.2.1 UUID getBSPAccessUUID() . 13
3.5.2.2 String getBSPDescription() . 13
3.5.2.3 Vector getBSPSupportedAlgorithms() . 13
3.5.2.4 Vector getBSPSupportedFormats(). 13
3.5.2.5 Vector getBSPSupportedTransformOperation() . 14
3.5.2.6 UUID getBSPUUID() . 14
3.5.2.7 int getDefaultCalibrateTimeout() . 14
3.5.2.8 int getDefaultCaptureTimeout() . 14
3.5.2.9 int getDefaultEnrolTimeout() . 14
3.5.2.10 int getDefaultIdentifyTimeout() . 14
3.5.2.11 int getDefaultVerifyTimeout() . 14
3.5.2.12 Vector getFactorsMask() . 15
3.5.2.13 byte[] getHostingEndpointIRI() . 15
iv © ISO/IEC 2014 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC DIS 30106-2
3.5.2.14 int getMaxBSPDbSize() . 15
3.5.2.15 int getMaxIdentify() . 15
3.5.2.16 int getMaxNumEnrolInstances() . 15
3.5.2.17 int getMaxAdditionalDataSize() . 15
3.5.2.18 Vector getOperations() . 16
3.5.2.19 Vector getOptions() . 16
3.5.2.20 String getPath() . 16
3.5.2.21 int getAdditionalDataPolicy() . 16
3.5.2.22 String getProductVersion() . 16
3.5.2.23 String getSpecVersion() . 16
3.5.2.24 String getVendor() . 17
3.6 Class Candidate . 17
3.6.1 Description . 17
3.6.2 Method Summary . 17
3.6.2.1 int getFMRAchieved() . 17
3.6.2.2 UUID getKey() . 17
3.6.2.3 void setFMRAchieved(int fmrAchieved) . 17
3.6.2.4 void setKey(UUID key) . 17
3.7 Class DataTypes . 18
3.7.1 Description . 18
3.7.2 Enumerations . 18
3.7.2.1 BiometricSubtype . 18
3.7.2.2 BiometricType . 18
3.7.2.3 BIRDatabaseAccess. 19
3.7.2.4 BSPSchemaOperations . 19
3.7.2.5 BSPSchemaOptions. 19
3.7.2.6 EventKind . 20
3.7.2.7 Facility . 20
3.7.2.8 GUIEnrolType . 20
3.7.2.9 GUIMoment . 20
3.7.2.10 GUIOperation . 21
3.7.2.11 GUIResponse . 21
3.7.2.12 GUISuboperation . 21
3.7.2.13 ProcessedLevel . 21
3.7.2.14 Purpose . 21
3.7.2.15 ResultOptions . 22
3.7.2.16 SecurityOptionsType . 22
3.7.2.17 UnitCategoryType . 22
3.7.2.18 UnitIndicatorStatus . 22
3.7.2.19 UnitPowerMode . 22
3.8 Class Date . 23
3.8.1 Description . 23
3.8.2 Method Summary . 23
3.8.2.1 int getDayOfMonth() . 23
3.8.2.2 int getHour() . 23
3.8.2.3 int getMinute() . 23
3.8.2.4 int getMonth() . 23
3.8.2.5 int getSecond() . 23
3.8.2.6 int getYear() . 23
3.8.2.7 boolean isLowerOrEqual (int day, int month, int year) . 24
3.8.2.8 boolean isLowerOrEqual (int day, int month, int year, int hour, int minute,
int second) . 24
3.8.2.9 boolean isLowerOrEqual (Date date) . 24
3.8.2.10 boolean isHigherOrEqual (int day, int month, int year) . 24
3.8.2.11 boolean isHigherOrEqual (int day, int month, int year, int hour, int
minute, int second) . 24
3.8.2.12 boolean isHigherOrEqual (Date date) . 24
3.8.2.13 void setDayOfMonth(int dayOfMonth) . 24
3.8.2.14 void setHour(int hour). 24
3.8.2.15 void setMinute(int minute) . 24
© ISO/IEC 2014 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC DIS 30106-2
3.8.2.16 void setMonth(int month) . 25
3.8.2.17 void setSecond(int second). 25
3.8.2.18 void setYear(int year) . 25
3.9 Class FrameworkSchema . 25
3.9.1 Description . 25
3.9.2 Method Summary . 25
3.9.2.1 UUID getFrameworkUUID() . 25
3.9.2.2 String getFWDescription() . 25
3.9.2.3 byte[] getFWProperty() . 25
3.9.2.4 UUID getFWPropertyID() . 26
3.9.2.5 byte[] getPath() . 26
3.9.2.6 String getProductVersion() . 26
3.9.2.7 String getSpecVersion() . 26
3.9.2.8 String getVendor() . 26
3.10 Class GUIBitmap . 26
3.10.1 Description . 26
3.10.2 Method Summary . 26
3.10.2.1 BIRSubtype getBIRSubtype() . 26
3.10.2.2 int getHeight() . 27
3.10.2.3 byte[][] getPixel() . 27
3.10.2.4 int getWidth(). 27
3.11 Class IdentifyPopulation . 27
3.11.1 Description . 27
3.11.2 Method Summary . 27
3.11.2.1 void addMember(PopulationMember member) . 27
3.11.2.2 void destroy() . 27
3.11.2.3 Vector getIdentifyPopulation() . 28
3.11.2.4 bool isBound() . 28
3.11.2.5 void unbind() . 28
3.12 Class PopulationMember . 28
3.12.1 Description . 28
3.12.2 Method Summary . 28
3.12.2.1 UUID getKey(). 28
3.12.2.2 BIR getTemplate() . 28
3.12.2.3 void setKey(UUID key) . 28
3.12.2.4 void setTemplate(BIR template) . 29
3.13 Class RegistryID . 29
3.13.1 Description . 29
3.13.2 Method Summary . 29
3.13.2.1 short getOwner() . 29
3.13.2.2 short getType() . 29
3.13.2.3 void setOwner(short owner) . 29
3.13.2.4 void setType(short type) . 29
3.14 Class SecurityProfileType .
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.