System for establishing a hierarchical identification system for marine data assets based on MRN

Abstract

The present invention relates to a hierarchical identification system for marine data assets based on Marine Resource Names (MRN), wherein all marine data assets are clearly classified into three layers—raw data (Resource), analysis technology (Technology), and analysis output (Product)—according to their roles, and the generation relationships between layers are defined; thereby, anyone using the data can verify its source and composition process through layer-by-layer identification and relationship definition, which can enhance the reliability of data utilization across institutions. In the hierarchical identification system for marine data assets based on Marine Resource Names (MRN) according to the present invention, the areas for which the IALA G1143 standard delegates definition to each organization are classified into three layers: Resource (raw data), Technology (analytical technology), and Product (analytical output); wherein the said Resource (raw data) refers to all unprocessed basic data, the said Technology (analytical technology) refers to models or technologies for processing data, and the said Product (analytical output) refers to result data generated by receiving the said Resource (raw data) or other Products (analytical outputs) through the said Technology (analytical technology), and the relationships between the layers of the three layers It is defined through metadata.

Description

Technology Field

[0001] The present invention relates to a hierarchical identification system for marine data assets based on Marine Resource Names (MRN), and more specifically, to a hierarchical identification system for marine data assets based on Marine Resource Names (MRN) in which all marine data assets are clearly classified into three layers according to their roles—Resource, Technology, and Product—while the generation relationships between layers are defined, thereby enabling anyone using the data to verify its source and composition process through hierarchical identification and relationship definition, which can increase the reliability of the data utilization among institutions. Background Technology

[0003] The reliability of data stems from the clarity of its source, but as various institutions converge data or process it using various technologies, it is becoming difficult to determine which source materials and technologies were used to create the final generated data.

[0004] Furthermore, data with unclear sources like this leads to a fundamental problem where reliability in the decision-making process cannot be guaranteed.

[0005] Therefore, it is very important to ensure the reliability of data generated from various sources and jointly utilized by multiple institutions.

[0006] This applies equally to the field of marine data utilization; however, amidst the increasing trend of integrated use of various marine data, ensuring the reliability of such data is becoming challenging, which can be briefly summarized as follows.

[0008] - Current Status of Marine Data Utilization

[0009] 1. Increased Integrated Utilization of Diverse Marine Data

[0010] (1) Collection and utilization of various forms of data, such as accident information, location information, and weather information, beyond existing physical marine targets (reefs, shipwrecks, etc.)

[0011] (2) Trend of jointly utilizing data collected from various agencies such as civilian, military, and police forces

[0012] 2. Generation of new data through convergence and processing

[0013] (1) Producing information with new value by merging or analyzing collected raw data

[0014] (2) The generation of secondary and tertiary data, such as marine accident prevention technology and predictive information, is gradually increasing

[0015] - Problems

[0016] 1. Limitations on tracing data sources and generation processes

[0017] (1) As marine data is integrated and various processing technologies are applied, the process of generating the final product becomes complex, and the problem arises that it is difficult to clearly identify the source and conversion history.

[0018] (2) As a result, the source of the data becomes unclear and consistency is reduced, leading to a decline in the reliability of data-driven decision-making.

[0019] 2. Functional Limitations of Existing MRN Identification Systems

[0020] (1) Existing MRN-related patents focus on identifying physical and static objects such as reefs, sunken ships, and artificial reefs.

[0021] (2) Lack of ability to clearly distinguish and identify the roles and types of dynamically generated digital data assets (e.g., predictive information, analysis models)

[0022] (3) Lack of a function to define and express the creation relationships between data assets

[0024] Accordingly, the applicant proposes the present invention as a technology that ensures the reliability of all marine data generated from various sources and jointly utilized by multiple institutions through a hierarchical identification system based on MRN (Marine Resource Name).

[0025] To briefly explain the above MRN, MRN stands for Maritime Resource Name, and such MRNs are defined by IALA (International Association of Marine Aids to Navigation and Lighthouse Authorities) and can follow the format of Uniform Resource Name defined by the IETF (Internet Engineering Task Force) standardization organization.

[0026] To elaborate, MRN is an international standard ID system designed to uniquely identify all maritime entities, such as vessels, marine facilities, equipment, and engines, in an e-Navigation environment. Prior art literature

[0028] Korean Registered Patent No. 10-1984555 (Published June 3, 2019), “Database Design Method for Marine Safety Information Standard Data Processing” Korean Registered Patent No. 10-2424081 (Published July 25, 2022), “Object Image Classification Method Based on Machine Learning and Location / Environment Information” The problem to be solved

[0029] An embodiment of the present invention provides a hierarchical identification system for marine data assets based on Marine Resource Name (MRN), in which all marine data assets are clearly classified into three layers—raw data (Resource), analysis technology (Technology), and analysis product (Product)—according to their roles, and at the same time, the generation relationships between layers are defined. Through layer-by-layer identification and relationship definition, anyone using the data can verify its source and composition process, thereby increasing the reliability of the data utilization among institutions.

[0030] In addition, an embodiment of the present invention provides a hierarchical identification system for marine data assets based on Marine Resource Names (MRNs), which ensures the reliability of all marine data generated from various sources and jointly utilized by multiple institutions through the aforementioned hierarchical identification system based on MRNs.

[0031] In addition, the embodiment of the present invention provides a hierarchical identification system for marine data assets based on Marine Resource Names (MRN), which, compared to the existing IALA MRN which focuses on identifying physical or static resources such as navigational aids and VTS, can identify even dynamically generated digital data assets (Resource, Technology, Product) based on standard structure extensions and define their relationships. means of solving the problem

[0033] The hierarchical identification system for marine data assets based on Marine Resource Names (MRN) according to an embodiment of the present invention is defined by the IALA G1143 standard, which delegates the definition to each organization. <oss>The domain is classified into three layers: Resource (raw data), Technology (analysis technology), and Product (analysis output), wherein the Resource (raw data) is all unprocessed basic data, the Technology (analysis technology) is a model or technology for processing data, and the Product (analysis output) is result data generated by receiving the Resource (raw data) or another Product (analysis output) through the Technology (analysis technology); the relationships between the layers of the three layers are defined through metadata, wherein the metadata of the Technology (analysis technology) defines the type of raw data required by the technology, and the metadata of the Product (analysis output) records the raw data and analysis technology actually used to generate the output, and the marine data assets input for defining the metadata of the Technology (analysis technology) may be Resource (raw data) or Product (analysis output) generated in a previous stage, and the metadata of the Product (analysis output) may record whether the marine data assets used are Resource (raw data), Product (analysis output), or Technology (analysis technology).

[0034] In addition, the hierarchical identification system for marine data assets based on Marine Resource Name (MRN) according to an embodiment of the present invention utilizes the corresponding top-level organization identifier of an organization that has been officially issued an OID (Original Organization Identifier) ​​through IALA, and the subordinate to the OID <oss>The domain is composed of five hierarchical domains: <Service>:<Asset Type>:<Institution>:<Object Type>:<Unique Identifier>, wherein the <Service> is an identifier of a service platform that operates a hierarchical identification system for marine data assets based on Marine Resource Name (MRN), the <Asset Type> indicates which layer the marine data asset belongs to among Resource (raw data), Technology (analytical technology), and Product (analytical output), the <Institution> is an identifier of the institution that created the marine data asset and refers to the creator regardless of the type of marine data asset, the <Object Type> indicates a detailed type of data defined autonomously by the <Institution>, and the <Unique Identifier> may be a unique ID of an individual marine data asset assigned autonomously by the <Institution>.

[0035] In addition, if the above <Asset Type> is Resource (Raw Data), the above <Institution> may be the institution that first collected or generated the said Resource (Raw Data); if the above <Asset Type> is Technology (Analysis Technology), the above <Institution> may be the institution that developed the said Technology (Analysis Technology); and if the above <Asset Type> is Product (Analysis Output), the above <Institution> may be the institution that generated or produced the said Product (Analysis Output). Effects of the invention

[0037] According to an embodiment of the present invention, all marine data assets are clearly classified into three layers—raw data (Resource), analysis technology (Technology), and analysis results (Product)—according to their roles, and at the same time, the generation relationships between the layers are defined. Through layer-specific identification and relationship definition, anyone using the data can verify its source and composition process, thereby increasing the reliability of the data utilization among institutions.

[0038] In addition, through the aforementioned hierarchical identification system based on MRN (Marine Resource Name), the reliability of all marine data generated from various sources and jointly utilized by multiple institutions can be guaranteed.

[0039] In addition, compared to the existing IALA MRN which focused on identifying physical or static resources such as navigational aids and VTS, it is now possible to identify dynamically generated digital data assets (Resource, Technology, Product) based on the extension of the standard structure and define their relationships. Brief explanation of the drawing

[0041] FIG. 1 is a configuration diagram conceptually illustrating a hierarchical identification system for marine data assets based on Marine Resource Name (MRN) according to an embodiment of the present invention. FIG. 2 is a block diagram illustrating a system for establishing a hierarchical identification system for marine data assets based on Marine Resource Name (MRN) according to an embodiment of the present invention. Specific details for implementing the invention

[0042] The following detailed descriptions relating to the present invention refer to the accompanying drawings, which are embodiments in which the present invention may be practiced and are illustrated as examples of such embodiments. These embodiments are described in detail to sufficiently enable those skilled in the art to practice the present invention. It should be understood that various embodiments of the present invention are different but need not be mutually exclusive. For example, specific shapes, structures, and characteristics described herein may be implemented in other embodiments without departing from the spirit and scope of the present invention in relation to one embodiment. Furthermore, it should be understood that the location or arrangement of individual components within each described embodiment may be changed without departing from the spirit and scope of the present invention.

[0043] Accordingly, the following detailed description is not intended to be taken in a limiting sense, and the scope of the invention is limited only by the appended claims, including all equivalents to those claimed therein, provided they are properly described. Similar reference numerals in the drawings refer to the same or similar functions across various aspects.

[0044] The terms used in this invention have been selected based on currently widely used general terms, taking into account their functions within the invention; however, these terms may vary depending on the intent of those skilled in the art, case law, the emergence of new technologies, etc. Additionally, in specific cases, terms have been arbitrarily selected by the applicant, and in such cases, their meanings will be described in detail in the relevant description of the invention. Therefore, the terms used in this invention should be defined not merely by their names, but based on their meanings and the overall content of the invention.

[0045] When a part of an invention is described as "including" a certain component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components. Additionally, terms such as "…part" or "…module" described in the specification refer to a unit that processes at least one function or operation, which may be implemented in hardware or software, or as a combination of hardware and software.

[0046] Referring to FIG. 1, a hierarchical identification system for marine data assets based on Marine Resource Name (MRN) according to an embodiment of the present invention will be described.

[0047] Before proceeding with the explanation, since the hierarchical identification system for marine data assets based on Marine Resource Names (MRNs) according to an embodiment of the present invention is based on the standard MRN grammar defined in IALA (International Association of Lighthouse Authorities) G1143-Unique Identifiers for Maritime Resources, the IALA MRN standard grammar will be briefly explained first.

[0048] First, the standard MRN syntax defined in IALA (International Association of Lighthouse Authorities) G1143-Unique Identifiers for Maritime Resources is as follows.

[0049]

[0050] And the standard MRN syntax defined in IALA (International Association of Lighthouse Authorities) G1143-Unique Identifiers for Maritime Resources is explained in more detail as follows.

[0051] 1. Definition of IALA MRN

[0052] - It refers to a permanent and unique identifier for marine resources (navigational aids, VTS, etc.) and follows the Internet standard URN (Uniform Resource Name) syntax (RFC 2141).

[0053] 2. IALA MRN Standard Grammar

[0054] - Basic structure : urn:mrn: <oid> : <oss>(G1143, Section 5.1.1)

[0055] - IALA is an organizational sub-namespace <oss>It is recommended to subdivide it further and use it in a hierarchical structure.

[0056] 3. Detailed Explanation of MRN Standard Syntax

[0057] - urn:mrn: A fixed prefix indicating that it is a Marine Resource Name (MRN) adhering to the URN standard

[0058] - <oid>(Organization Identifier): A top-level organizational identifier (e.g., iala, iho, kor) managed by IALA that identifies each organization (country or agency).

[0059] - <oss>(Organization-Specific String) : <oid>Sub-namespaces managed by the organization identified as

[0060] Example: IALA is <oss>cast <type> : <type-specific-part>subdivided again into <type>: aton (navigational aid), vts (control services), wwy (navigation route), etc. <type-specific-part>Defined as : kr:A01010001(Korean Lighthouse Identifier)

[0061] 4. Standard MRN Example (G1143 Annex A)

[0062] - urn:mrn:iala:aton:us:1234.5 (U.S. navigational aid under IALA administration)

[0063] - urn:mrn:iala:aton:kr:A01010001 (Korean navigational aids under IALA administration)

[0064] However, since such existing IALA MRNs focus on identifying physical or static resources such as navigational aids and VTS, the hierarchical identification system of marine data assets based on marine resource names (MRN) according to an embodiment of the present invention, in order to solve these limitations, extends the standard structure described above to enable the identification of dynamically generated digital data assets (resource, technology, product) and the definition of their relationships.

[0066] Referring to FIG. 1, a hierarchical identification system for marine data assets based on Marine Resource Name (MRN) according to an embodiment of the present invention will be described.

[0067] FIG. 1 is a diagram conceptually illustrating a hierarchical identification system of marine data assets based on marine resource names (MRN) according to one embodiment of the present invention.

[0068] As described above, the hierarchical identification system for marine data assets based on marine resource names (MRN) according to one embodiment of the present invention defines a new MRN naming system, which aims to solve the problem of not being able to clearly identify data hierarchically and define their generation relationships, going beyond the limitations of the existing IALA MRN which focuses on static asset identification.

[0069] Hereinafter, a hierarchical identification system for marine data assets based on Marine Resource Name (MRN) according to an embodiment of the present invention will be described in detail.

[0070] 1. Definition and Purpose of the System

[0071] - This system is defined by the IALA G1143 standard, which delegates the definition to each organization <oss>It is an MRN naming scheme that newly defines the (organization-specific unique string) domain for two specific purposes: 'hierarchical identification of data' and 'definition of creation relationships'.

[0072] - It resolves the problem of unclear data sources and enables data consistency and clarity by clearly defining the relationship between the source (Resource) and technology (Technology) from which the final data (Product) was created.

[0073] 2. Core Components of the System

[0074] (1) Three-tiered classification of data assets (conceptual basis)

[0075] - Moving beyond existing fragmentary identification, we introduce a concept of classifying all assets into three logical layers according to their roles to reflect the data generation process.

[0076] ◎ Resource (Raw Data): All unprocessed basic data

[0077] ◎ Technology (Analysis Technology): Models or technologies for processing data

[0078] ◎ Product (Analysis Output): Result data generated by receiving Resource or Product (other analysis output) as input through Technology.

[0079] (2) Defining creation relationships through metadata (methodology)

[0080] - It does not stop at mere classification, but specifies a method for defining complex relationships between each layer.

[0081] ◎ Technology (Analysis Technology) Metadata: Defines the type of raw data required by the technology.

[0082] This input asset may be a Resource (raw data) or a Product (output) generated in the previous step.

[0083] ◎ Product (Analysis Output) Metadata: Records the raw data and analysis techniques actually used to generate the output.

[0084] At this time, clearly distinguish and record whether the asset used is a Resource, Product, or Technology.

[0085] 3. 'kor' <oid>using <oss>Definition of the hierarchical structure

[0086] - Utilizing kor (Ministry of Oceans and Fisheries of the Republic of Korea), which has been officially issued an OID through IALA, and the subordinate to this OID <oss>The area is newly organized into 5 hierarchical areas as follows.

[0087] (1) defined <oss>structure

[0088] IALA MRN Basic Structure : urn:mrn: <oid> : <oss>

[0089] <oss>= <서비스>:<자산유형>:<기관>:<객체유형>:<고유식별자>

[0090] <oss>Full MRN structure with applied : urn:mrn: <oid>:<Service>:<Asset Type>:<Institution>:<Object Type>:<Unique Identifier>

[0091] (2) Detailed description of OSS components

[0092] <Service>(Service Identifier): Identifier of the service (platform) operating this MRN system (e.g., bcsp blockchain-based marine data security platform)

[0093] <Asset Type>: A core element of the present invention, specifying which layer the asset belongs to among resource (raw data), technology (analytical technology), and product (outcome).

[0094] <Organization>: Identifier of the organization that created the data asset. This field refers to the creator regardless of the asset type.

[0095] ◎ In the case where the asset type is 'resource', the institution that first collected / generated the data

[0096] ◎ In the case of the asset type being technology, the institution that developed the relevant analysis technology

[0097] ◎ In the case where the asset type is 'product', the institution that generated (derived) the relevant analysis deliverable

[0098] <Object Type>: Detailed types of data defined autonomously by the <Organization> (e.g., wreck, ais-traffic)

[0099] Since there are no limits to the types of marine data, the present invention does not specify all types, and the institution can freely designate objects.

[0100] <Unique Identifier>: A unique ID for individual assets assigned autonomously by the <Institution>

[0101] It is recommended to define identifiers by considering the characteristics of the data (e.g., time series data, fixed identifiers, etc.).

[0102] With the above-described configuration, all marine data assets are clearly classified into three layers—raw data (Resource), analysis technology (Technology), and analysis results (Product)—according to their roles, and at the same time, the generation relationships between the layers are defined. Through this layered identification and relationship definition, anyone using the data can verify its source and composition process, and thus the reliability of the data can be enhanced across all institutions.

[0103] In other words, through the aforementioned hierarchical identification system based on MRN (Marine Resource Name), the reliability of all marine data generated from various sources and jointly utilized by multiple institutions can be guaranteed.

[0104] In addition, compared to the existing IALA MRN which focused on identifying physical or static resources such as navigational aids and VTS, it is now possible to identify dynamically generated digital data assets (Resource, Technology, Product) based on the extension of the standard structure and define their relationships.

[0105] The following illustrates an example in which a hierarchical identification system for marine data assets based on Marine Resource Name (MRN) according to an embodiment of the present invention is applied, illustrating the overall scenario.

[0106]

[0107] As confirmed through the above scenario, the hierarchical identification system of marine data assets based on Marine Resource Name (MRN) according to an embodiment of the present invention can logically define the entire complex sequential analysis process by clearly distinguishing and recording the hierarchy of the input data by the MRN issuer.

[0109] The following describes a system for establishing a hierarchical identification system for marine data assets based on Marine Resource Name (MRN) according to one embodiment of the present invention.

[0110] FIG. 2 is a block diagram illustrating a system for establishing a hierarchical identification system for marine data assets based on marine resource names (MRN) according to one embodiment of the present invention.

[0111] Before explaining, the system for establishing a hierarchical identification system for marine data assets based on marine resource names (MRN) according to the present embodiment is a device configuration for implementing the hierarchical identification system for marine data assets based on marine resource names (MRN) described with reference to FIG. 1.

[0112] As described above, a system for establishing a hierarchical identification system for marine data assets based on a marine resource name (MRN) according to one embodiment of the present invention comprises an input unit (100), a hierarchy classification module (200), a hierarchy relationship definition module (300), an organization unique string generation module (400), and a control unit (500).

[0113] The input section (100) receives marine data assets.

[0114] The layer classification module (200) classifies marine data assets transmitted through the input unit (100) into one of three layers: Resource (raw data), Technology (analysis technology), and Product (analysis result).

[0115] And the Resource (raw data) of the hierarchical classification module (200) is all unprocessed basic data, the Technology (analysis technology) is a model or technology for processing data, and the Product (analysis result) is result data generated by receiving the Resource (raw data) or other Product (analysis result) through the Technology (analysis technology).

[0116] The hierarchical relationship definition module (300) defines the relationships between the hierarchies classified through the hierarchical classification module (200) in the form of metadata.

[0117] And in the hierarchical relationship definition module (300), the metadata of the Technology (analysis technology) defines the type of raw data required by the technology, and the metadata of the Product (analysis output) records the raw data and analysis technology actually used to generate the output, and records which of the marine data assets used is the Resource (raw data), Product (analysis output), and Technology (analysis technology).

[0118] The organization unique string generation module (400) utilizes the corresponding top-level organization identifier of an organization that has been officially issued an OID (top-level organization identifier) ​​through IALA, and the underside of the official OID (top-level organization identifier) <oss>The domain is organized into five hierarchical domains: <Service>:<Asset Type>:<Institution>:<Object Type>:<Unique Identifier>.

[0119] And in the organization unique string generation module (400), the <Service> is an identifier of a service platform that operates a hierarchical identification system for marine data assets based on marine resource names (MRN), the <Asset Type> indicates which layer the marine data asset belongs to among Resource (raw data), Technology (analysis technology), and Product (analysis output), the <Institution> is an identifier of the institution that generated the marine data asset and signifies the generating entity regardless of the marine data asset type, the <Object Type> indicates a detailed type of data that is autonomously defined by the <Institution>, and the <Unique Identifier> is a unique ID of an individual marine data asset that is autonomously assigned by the <Institution>.

[0120] In addition, if the above <Asset Type> is Resource (Raw Data), the above <Institution> is the institution that first collected or generated the said Resource (Raw Data); if the above <Asset Type> is Technology (Analysis Technology), the above <Institution> is the institution that developed the said Technology (Analysis Technology); and if the above <Asset Type> is Product (Analysis Output), the above <Institution> is the institution that generated or produced the said Product (Analysis Output).

[0121] The control unit (500) is configured to interconnect the input unit (100), the hierarchy classification module (200), the hierarchy relationship definition module (300), and the organization unique string generation module (400).

[0122] And through the configuration described above, marine data is generated that follows the hierarchical identification system of marine data assets based on the Marine Resource Name (MRN) described with reference to Fig. 1.

[0123] To elaborate, since marine data following the hierarchical identification system of marine data assets based on marine resource names (MRN) described with reference to FIG. 1 is generated through the system for establishing a hierarchical identification system of marine data assets based on marine resource names (MRN) according to an embodiment of the present invention, the operation according to the hierarchical identification system of marine data assets based on marine resource names (MRN) described with reference to FIG. 1 can be implemented.

[0125] As described above, although the present description has been explained with specific details such as specific components, limited embodiments, and drawings, this is provided merely to aid in a more comprehensive understanding of the invention, and the invention is not limited to the above embodiments. A person skilled in the art can make various modifications and variations from this description.

[0126] Therefore, the scope of the present invention should not be limited to the described embodiments, and all variations equivalent to or equivalent to the claims set forth below, as well as the claims themselves, shall be considered to fall within the scope of the present invention. Explanation of the symbols

[0128] 100 : Input section 200 : Hierarchy classification module 300: Hierarchy Definition Module 400: Organization Unique String Generation Module 500 : Control unit< / oss> < / oid> < / oss> < / oss> < / oss> < / oid> < / oss> < / oss> < / oss> < / oid> < / oss> < / type> < / type> < / oss> < / oid> < / oss> < / oid> < / oss> < / oss> < / oid> < / oss> < / oss>

Claims

Claim 1 An input unit (100) into which marine data assets are input: a hierarchy classification module (200) that classifies marine data assets transmitted through the input unit (100) into one of three hierarchyes: Resource (raw data), Technology (analysis technology), and Product (analysis output); a hierarchy relationship definition module (300) that defines the relationships between the hierarchy classified through the hierarchy classification module (200) in the form of metadata; utilizing the corresponding top-level organization identifier of an organization that has been officially issued an OID (top-level organization identifier) ​​through IALA, and the one under the official OID (top-level organization identifier). <oss>The system includes an organization unique string generation module (400) that organizes the area into five hierarchical areas of <Service>:<Asset Type>:<Institution>:<Object Type>:<Unique Identifier>; and a control unit (500) that interconnects the input unit (100), the hierarchical classification module (200), the hierarchical relationship definition module (300), and the organization unique string generation module (400); wherein the Resource (raw data) of the hierarchical classification module (200) is all unprocessed basic data, the Technology (analysis technology) is a model or technology that processes data, and the Product (analysis result) is result data generated by receiving the Resource (raw data) or another Product (analysis result) through the Technology (analysis technology); and in the hierarchical relationship definition module (300), the metadata of the Technology (analysis technology) defines the type of raw data required by the technology, and the metadata of the Product (analysis result) records the raw data and analysis technology actually used to generate the result, wherein the marine data asset used It records which of Resource (raw data), Product (analysis output), and Technology (analysis technology) is used, and in the organization unique string generation module (400), the <Service> is an identifier of a service platform that operates a hierarchical identification system for marine data assets based on marine resource names (MRN), the <Asset Type> indicates which layer the marine data asset belongs to among Resource (raw data), Technology (analysis technology), and Product (analysis output), the <Institution> is an identifier of the institution that created the marine data asset and refers to the creator regardless of the marine data asset type, the <Object Type> indicates a detailed type of data that is autonomously defined by the <Institution>, and the <Unique Identifier> is a unique ID of an individual marine data asset that is autonomously assigned by the <Institution>.A system for establishing a hierarchical identification system for marine data assets based on Marine Resource Name (MRN), characterized by generating marine data that follows a hierarchical identification system for marine data assets based on Marine Resource Name (MRN), wherein if the above <Asset Type> is Resource (Raw Data), the above <Institution> is the institution that first collected or generated the said Resource (Raw Data); if the above <Asset Type> is Technology (Analysis Technology), the above <Institution> is the institution that developed the said Technology (Analysis Technology); and if the above <Asset Type> is Product (Analysis Output), the above <Institution> is the institution that generated or produced the said Product (Analysis Output).< / oss> Claim 2 delete

Images