ISO PAS 22853-2005 Ships and marine technology - Computer applications - Specification of Maritime Safety Markup Language (MSML)《船舶和海上技术 计算机应用 海上安全标记语言(MSML)的规范.pdf

《ISO PAS 22853-2005 Ships and marine technology - Computer applications - Specification of Maritime Safety Markup Language (MSML)《船舶和海上技术 计算机应用 海上安全标记语言(MSML)的规范.pdf》由会员分享，可在线阅读，更多相关《ISO PAS 22853-2005 Ships and marine technology - Computer applications - Specification of Maritime Safety Markup Language (MSML)《船舶和海上技术 计算机应用 海上安全标记语言(MSML)的规范.pdf（102页珍藏版）》请在麦多课文档分享上搜索。

1、 Reference number ISO/PAS 22853:2005(E) ISO 2005PUBLICLY AVAILABLE SPECIFICATION ISO/PAS 22853 First edition 2005-10-01 Ships and marine technology Computer applications Specification of Maritime Safety Markup Language (MSML) Navires et technologie maritime Applications informatiques Spcification du

2、 language de la scurit maritime ISO/PAS 22853:2005(E) PDF disclaimer This PDF file may contain embedded typefaces. 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 compu

3、ter performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes 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 creat

4、e this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for 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

5、Central Secretariat at the address given below. ISO 2005 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 microfilm, without permission in writing from either I

6、SO at the address below or ISOs 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 copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2005 All rights reservedISO/PAS 22853:2005(E) ISO 2

7、005 All rights reserved iii Contents Page Foreword vi 0 Introduction . vii 1 Scope . 1 1.1 Inclusions 1 1.2 Limitations. 2 1.3 Exclusions . 2 1.4 Summary 3 2 Normative references . 3 3 Terms and definitions. 3 4 Symbols and abbreviated terms . 4 5 MSML design. 5 5.1 General. 5 5.2 Data model. 6 5.3

8、Perspectives 8 5.4 Administrative support. 9 5.5 Security support . 9 5.6 Successive information build-up 9 5.7 MSML vs. standardized maritime technology 10 5.8 MSML processor . 10 6 MSML specification 12 6.1 General. 12 6.2 Referencing . 12 6.3 Security report 13 6.4 Relation to XML Schema 14 6.5 S

9、pecial considerations. 14 6.6 simpleType: units_type 15 6.7 simpleType: element_identity_algorithm_type . 16 6.8 simpleType: vessel_type_reference_type 17 6.9 simpleType: waste_type_reference_type. 17 6.10 simpleType: dangerous_goods_type_reference_type . 17 6.11 simpleType: non_dangerous_cargo_type

10、_reference_type 17 6.12 simpleType: MSML_non_dangerous_cargo_type. 17 6.13 simpleType: certificate_type . 18 6.14 simpleType: propolusion_power_type. 19 6.15 simpleType: propolusion_principle_type. 20 6.16 simpleType: network_power_source_type 20 6.17 simpleType: hull_material_type 20 6.18 simpleTyp

11、e: damage_status_type 21 6.19 simpleType: supply_shortage_type 21 6.20 simpleType: manoeuvrability_type. 21 6.21 simpleType: manual_plan_type 22 6.22 simpleType: record_type . 22 6.23 simpleType: shore_base_type 23 6.24 simpleType: shore_base_arrival_passing_type 23 6.25 simpleType: vessel_hindrance

12、_reason_type 24 6.26 simpleType: deficiencies_rectified_limit_type 25 6.27 simpleType: cargo_passenger_transfer_type . 25 6.28 simpleType: repair_and maintenance_reason_type. 25 6.29 complexType: detailed_information_type 26 ISO/PAS 22853:2005(E) iv ISO 2005 All rights reserved6.30 complexType: shor

13、e_base_identity_type. 26 6.31 complexType: vessel_type. 27 6.32 complexType: waste_type 27 6.33 complexType: dangerous_goods_type 27 6.34 complexType: date_and_time_type 28 6.35 complexType: address_information_type 28 6.36 complexType: timed_address_information_type 29 6.37 complexType: address_his

14、tory_type 29 6.38 complexType: timed_item_type. 29 6.39 complexType: item_history_type 30 6.40 complexType: wire_rope_type. 30 6.41 complexType: engine_type 30 6.42 complexType: network_type 31 6.43 complexType: room_type. 31 6.44 complexType: hull_mechanical_securing_type 32 6.45 complexType: equip

15、ment_type . 32 6.46 complexType: crew_group_capability_type 33 6.47 complexType: environmental_condition_type. 34 6.48 complexType: dangeros_goods_type 34 6.49 complexType: non_dangerous_goods_cargo_type 35 6.50 complexType: damage_type 35 6.51 complexType: vessel_hindrance_type . 36 6.52 complexTyp

16、e: shore_base_service_type . 36 6.53 complexType: vessel_id_type . 37 6.54 complexType: vessel_assistance_type 37 6.55 complexType: route_type. 38 6.56 complexType: derived_EncryptedType 39 6.57 Element: MSML 39 6.58 Element: administrative_support 40 6.59 Element: security_report 41 6.60 Element: e

17、ncrypted_element . 41 6.61 Element: data_model 42 6.62 Element: vessel_static_type 42 6.63 Element: description. 42 6.64 Element: administration . 45 6.65 Element: certificate . 48 6.66 Element: constituent. 50 6.67 Element: hull 50 6.68 Element: mooring 51 6.69 Element: network 51 6.70 Element: con

18、struction 51 6.71 Element: propulsion . 53 6.72 Element: safety_equipment . 53 6.73 Element: communication_equipment . 54 6.74 Element: navigation_equipment 55 6.75 Element: supervision_equipment 55 6.76 Element: emergency_equipment. 56 6.77 Element: cargo_passenger_equipment 57 6.78 Element: vessel

19、_dynamic_data. 58 6.79 Element: crew 58 6.80 Element: route_at_sea 59 6.81 Element: cargo_passenger 60 6.82 Element: status . 61 6.83 Element: constituent_status 61 6.84 Element: emergency_status 63 6.85 Element: document_status 64 6.86 Element: overall_status 65 6.87 Element: previous_tasks 65 6.88

20、 Element: shore_base_static_data . 66 6.89 Element: description. 67 ISO/PAS 22853:2005(E) ISO 2005 All rights reserved v 6.90 Element: administration. 68 6.91 Element: service . 68 6.92 Element: shore_base_dynamic_data74 6.93 Element: service_status. 75 6.94 Element: overall_status . 76 6.95 Element

21、: vessel_shore_base_relation 76 6.96 Element: administration. 77 6.97 Element: status . 77 6.98 Element: vessel_shore_task 78 6.99 Element: perspective 80 6.100 Element: repair_and_maintenance . 80 6.101 Element: ashore 81 6.102 Element: onboard . 83 6.103 Element: status . 85 6.104 Element: inspect

22、ion 86 7 MSML instance processing . 88 Bibliography . 89 ISO/PAS 22853:2005(E) vi ISO 2005 All rights reservedForeword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is

23、 normally carried out through ISO technical committees. Each member body interested in a subject for which a technical 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

24、 in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical 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 pr

25、epare International Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. In other circumstances, particularly when

26、there is an urgent market requirement for such documents, a technical committee may decide to publish other types of normative document: an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical experts in an ISO working group and is accepted for publication if it i

27、s approved by more than 50 % of the members of the parent committee casting a vote; an ISO Technical Specification (ISO/TS) represents an agreement between the members of a technical committee and is accepted for publication if it is approved by 2/3 of the members of the committee casting a vote. An

28、 ISO/PAS or ISO/TS is reviewed after three years in order to decide whether it will be confirmed for a further three years, revised to become an International Standard, or withdrawn. If the ISO/PAS or ISO/TS is confirmed, it is reviewed again after a further three years, at which time it must either

29、 be transformed into an International Standard or be withdrawn. 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 identifying any or all such patent rights. ISO/PAS 22853 was prepared by Technic

30、al Committee ISO/TC 8, Ships and marine technology, Subcommittee SC 10, Computer applications. ISO/PAS 22853:2005(E) ISO 2005 All rights reserved vii 0 Introduction 0.1 General This Publicly Available Specification specifies the XML application MSML (Maritime Safety Markup Language). MSML is a langu

31、age for structuring information and the goal is to create an open standard that can be used generally in the maritime sector. MSML is implemented using XML Schema, which is contained in a separate document that could be used at validation. The first purpose of MSML is to make it possible to record s

32、afety related information in relation to repair and maintenance. The second purpose is to define an extensible structure that could be developed in future versions of MSML. Note that MSML should not primarily be seen as a support for normal work onboard. Instead, it is an add-on support for transfer

33、s of safety related information to/from the vessel. MSML enables security handling and since MSML concerns safety aspects there is information support for preventing accidents; minimizing extent of damage; minimizing criticality of consequences. These aspects concern both vessel and bases ashore (de

34、noted shore bases in this Publicly Available Specification). MSML consists of the following constituents: data model that defines the data of interest. The basic parts of the data model are vessel static and dynamic areas, shore base static and dynamic areas and vessel shore base relation. Each of t

35、hese can be created successively and thus validation can be made even if information is not complete; administrative support that defines the handling of the XML application instance as a file; security support that defines the handling of data security. MSML enables digital signatures and encryptio

36、n via the W3C recommendations “XML Encryption Syntax and Processing” and “XML-Signature Syntax and Processing”. The data model can be seen from different perspectives and the following are defined: inspection that contains information related to externally made inspections; repair and maintenance th

37、at contains the corresponding information; A fundamental property of MSML is that it does not consider the actual use of data, e.g. there is no specification of MSML messages. This makes it practical to use MSML in a large variety of applications and without modifying the definition of MSML. This Pu

38、blicly Available Specification contains nearly the same information as the XML Schema representation but expressed in plain English. In this way, it is possible to discuss and evaluate MSML without knowing the syntax details of XML Schema. This Publicly Available Specification also contains rules an

39、d guidelines associated with MSML. Planning, performing, recording and evaluating repair and maintenance are crucial for safe transports at sea. Preventive actions are especially cost-effective; is it possible to plan repair and maintenance at the optimal place and time? Fulfilling these aspects wil

40、l prevent accidents and thus save money and effort for all involved parties. For these reasons the Maritime Safety Markup Language (MSML) is defined. It is an XML application specified using XML Schema (see 10 and 11). ISO/PAS 22853:2005(E) viii ISO 2005 All rights reservedSince the purpose of MSML

41、is to handle safety aspects in relation to repair and maintenance, there is information support for preventing accidents, e.g. vessel status, previous repairs, remaining deficiencies; minimizing extent of damage, e.g. personnel training, personal equipment, and pollution control; minimizing critical

42、ity of consequences, e.g. status of emergency equipment. The information support concerns both vessel and shore base (e.g. a port) and is valid also for other safety related aspects than repair and maintenance; thus, future extensions can be made smoothly. MSML is vessel-centric in the sense that al

43、l relevant aspects of the vessel and its task are included while only one of possibly many tasks of a port is included (only the berth used for the vessel). Port is a typical example of a shore base as defined in this Publicly Available Specification. By using MSML it is also possible to associate a

44、 vessel and a shore base and the information can flow in the following ways: vessel-to-vessel, e.g. support information if communication with shore base cannot be made; vessel-to-shore base, e.g. sending status information; shore base-to-vessel, e.g. sending recommended actions such as go to nearest

45、 drydock for inspection; shore base-to-shore base, e.g. preparing the next port to visit for the vessel. However, there is no support in MSML for relating a vessel with another vessel and relating a shore base with another shore base, i.e. there is no support for storing information that describes s

46、uch a relation. For example, a vessel giving instructions to another vessel must be handled outside MSML (but of course a vessel could just send its information to another vessel if necessary).This means that more than one MSML instance has to be used for relating more than one vessel with a shore b

47、ase; relating more than one shore base with a vessel; relating a vessel with another vessel; relating a shore base with another shore base. There are several reasons for this design: keeping down the size of MSML, i.e. not making the definition too complex; keeping down the size of MSML instances, i

48、.e. not letting transfers take too long a time; encouraging vessel-to-vessel communication via shore base; letting shore base to shore base communication be handled outside MSML. An example of a possible message sequence using MSML is a vessel approaching a port with the intention of delivering its

49、cargo. 1. The vessel stores vessel data and sends the information to the port. 2. The port checks if there is a berth for the vessel, if it is allowed to enter the port, if there are no alarms, if a pilot is available, if repair and maintenance is accurate, etc. The port stores port data and sends data to vessel. 3. The vessel checks port data and requests an acknowledgement. 4. The port relates vessel and port data and sends acknowledgement. ISO/PAS 22853:2005(E) ISO 2005 All rights rese