ANSI INCITS ISO 19119 AMD 1-2008 Geographic information Services AMENDMENT 1.pdf

1、INCITS/ISO 19119:2005/Amd.1:2008 (ISO 19119:2005/Amd.1:2008, IDT) Geographic information Services AMENDMENT 1INCITS/ISO 19119:2005/Amd.1:2008(ISO 19119:2005/Amd.1:2008, IDT)INCITS/ISO 19119:2005/Amd.1:2008 ii ITIC 2008 All rights reserved PDF disclaimer This PDF file may contain embedded typefaces.

2、In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing A

3、dobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized f

4、or printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. Adopted by INCITS (InterNational Committee for Information Technolo

5、gy Standards) as an American National Standard. Date of ANSI Approval: 8/22/2008 Published by American National Standards Institute, 25 West 43rd Street, New York, New York 10036 Copyright 2008 by Information Technology Industry Council (ITI). All rights reserved. These materials are subject to copy

6、right claims of International Standardization Organization (ISO), International Electrotechnical Commission (IEC), American National Standards Institute (ANSI), and Information Technology Industry Council (ITI). Not for resale. No part of this publication may be reproduced in any form, including an

7、electronic retrieval system, without the prior written permission of ITI. All requests pertaining to this standard should be submitted to ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of America INCITS/ISO 19119:2005/Amd.1:2008 ITIC 2008 All rights reserved iii Foreword

8、 ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical

9、 committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of elec

10、trotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the

11、 member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for iden

12、tifying any or all such patent rights. Amendment 1 to ISO 19119:2005 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics. Amendement 1 to ISO 19119:2005 focuses on extensions of the service metadata model, concerning a more detailed description of associated dataset of a

13、 service instance. INCITS/ISO 19119:2005/Amd.1:2008 ITIC 2008 All rights reserved 1 Geographic information Services AMENDMENT 1: Extensions of the service metadata model Page 19, 7.4.1, Para 3 (starting with “A service instance may be tightly coupled with a dataset instance, ”) Add the following. A

14、single service instance may have both kinds of data associated, loosely and tightly coupled. In this case, the instance is “mixed coupled”. The coupling type is formalised by the SV_CouplingType class. Page 20, Figure 8 Replace with the following UML model. Figure 8 Services and service metadata INC

15、ITS/ISO 19119:2005/Amd.1:2008 2 ITIC 2008 All rights reserved Page 21, Figure 9 Replace with the following UML model. Figure 9 Service metadata class diagram INCITS/ISO 19119:2005/Amd.1:2008 ITIC 2008 All rights reserved 3 Page 51, Table C.1 Add the following to Table C.1 “Data dictionary for SV_Ser

16、viceIdentification”. Table C.1 Data dictionary for SV_ServiceIdentification Attribute name/Role name Definition Obligation/ Condition Maximum occurrence Data type 1. extent the geographic/temporal region where the service is valid, including the bounding box, bounding polygon, vertical, or temporal

17、extent of the service C/ if couplingType equals “mixed” or “tight” either extent.geographicElement.EX_GeographicBoundingBox or extent.geographicElement.EX_GeographicDescription is required N EX_Extent 2. coupledResource further description of the data coupling in the case of tightly coupled services

18、 O N SV_CoupledResource 3. couplingType type of coupling between service and associated data (if exists) M 1 SV_CouplingType Pages 52 and 53 Delete C.2.4. and renumber C.2.5, C.2.6 and C.2.7 as C.2.4, C.2.5 and C.2.6, and Tables C.4 and C.5 as C.3 and C.4 respectively. Add the following subclauses a

19、fter C.2.6. Page 53 C.2.7 Data dictionary for SV_CoupledResource SV_CoupledResource links a given operationName (mandatory attribute of SV_OperationMetadata) with a data set identified by an “identifier”, as shown in Table C.5. Table C.5 Data dictionary for SV_CoupledResource Attribute name/Role nam

20、e Definition Obligation/ Condition Maximum occurrence Data type 1. operation name name of the service operation M 1 CharacterString 2. identifier name of the identifier of a given tightly coupled dataset M 1 CharacterString SV_CoupledResource requires that a given operationName or identifier shall r

21、efer to an existing operationName given by SV_OperationMetadata.operationName or an identifier given by _MD_Identification.citation.identifier.code, respectively. INCITS/ISO 19119:2005/Amd.1:2008 4 ITIC 2008 All rights reserved C.2.8 Data dictionary for SV_CouplingType The data dictionnary for SV_Co

22、uplingType is provided in Table C.6. Table C.6 Data dictionary for SV_CouplingType Name Domain code Definition 1 SV_CouplingType CouplingTypeCd class of information to which the referencing entity applies 1. loose 001 service instance is loosely coupled with a data instance, i.e. no MD_DataIdentific

23、ation class has to be described 2. mixed 002 service instance is mixed coupled with a data instance, i.e. MD_DataIdentification describes the associated data instance and additionally the service instance might work with other external data instances 3. tight 003 service instance is tightly coupled

24、with a data instance, i.e. MD_DataIdentification class MUST be described C.2.9 Data dictionary for SV_ParameterDirection The data dictionary for SV_ParameterDirection is provided in Table C.7. Table C.7 Data dictionary for SV_ ParameterDirection Name Domain code Definition 1 SV_ ParameterDirection P

25、arameterDirectionCd class of information to which the referencing entity applies 1. in 001 the parameter is an input parameter to the service instance 2. out 002 the parameter is an output parameter to the service instance 3. in/out 003 the parameter is both an input and output parameter to the service instance INCITS/ISO 19119:2005/Amd.1:2008 ICS 35.240.70 Price based on 4 pages ITIC 2008 All rights reserved