Value data digital representation method based on meta-model

Abstract

The invention provides a value data digital representation method based on a meta-model, and relates to the technical field of measurement digital transformation, and the method comprises the steps: constructing a unit-system digital representation meta-model; performing mode conversion on the original magnitude data based on the unit digital expression meta-model to obtain digitally expressed magnitude data; and based on the unit digital expression meta-model, verifying the digitally expressed magnitude data to obtain a magnitude data verification result, and completing the digital expression of the magnitude data. According to the invention, the digital representation of the magnitude data is readable by a machine, explainable by the machine and traceable.

Description

Technical Field

[0001] The present invention relates to the field of digital transformation technology for measurement, and in particular to a method for digitally representing measurement data based on a metamodel. Background Art

[0003] In order to solve the problem of digital representation of measurement units, many organizations and institutions have conducted research on the digital representation of units. There are two main solutions for the current digital representation of measurement units: one is a machine-readable unit identifier scheme based on international standards, such as ISO 80000 and IEC TS 62720; the other is a measurement unit ontology representation scheme based on semantic web technology, such as QUDT, QUDV, OM and vim:ontology. Solution 1 (unit identifier) ​​can only achieve the minimum machine-readable standard. With the increasing complexity of systems in various fields, simple machine-readable can no longer meet the requirements of data exchange and integration between different systems, and can neither be machine-interpretable nor machine-traceable. Solution 2 (unit ontology) has solved the problem of semantic expression of units to a certain extent, but it cannot correctly interpret the meaning of units, including the standardization of different expressions of units and the consistency of different expressions of the same unit.

[0004] Therefore, there are many difficulties in solving the problems of machine interpretability and traceability in unit digital representation methods using existing methods. Summary of the invention

[0005] In view of the above-mentioned deficiencies in the prior art, the present invention provides a digital representation method for measurement data based on a metamodel, which solves the problem that the digital representation of measurement data is machine-readable, machine-interpretable and traceable.

[0006] In order to achieve the above-mentioned invention object, the technical solution adopted by the present invention is: a digital representation method of value data based on a metamodel, comprising:

[0007] S1: Constructing the digital expression meta-model of the unit system;

[0008] S2: Based on the unit system digital expression metamodel, the original value data is converted into a mode to obtain digitally represented value data;

[0009] S3: Based on the unit system digital expression metamodel, the digitally represented quantity data is verified to obtain a quantity data verification result, thereby completing the digital representation of the quantity data.

[0010] (1) The digital representation scheme of units based on ontology has a variety of serialization forms, such as RDF, RDFS and OWL. The XML format adopted by the present invention has good versatility and can be read and processed by different systems; the digital representation scheme of units based on ontology has a variety of structures, and the unit systems defined by different organizations are different and inconsistent. The present invention is developed based on authoritative standards and specifications in the field of metrology and has versatility and consistency; although the digital representation scheme of units based on ontology provides relatively rich semantic information, it cannot be understood by computers and still requires hard coding to utilize the semantic information. The metadata model of the present invention realizes machine interpretability, and there is no need for different systems to hard code again to implement functions;

[0011] (2) The digital representation solution of units based on unit identifiers relies on traditional string matching technology and cannot detect the same SI unit expressions of different non-SI units, while the metadata model defined in the present invention can detect them; the digital representation solution of units based on unit identifiers cannot determine different expression formats of the same unit, while the metadata model defined in the present invention can identify, for example, the non-SI expression form and SI unit expression form of the derived unit; the digital representation solution of units based on unit identifiers only includes the basic name of the unit and the corresponding identifier string, and lacks metadata description. The metadata model proposed in the present invention provides a metadata description framework, which describes the unit information more comprehensively according to the requirements of the SI manual;

[0012] (3) A single unit identifier does not contain the original definition data of the measurement unit, which does not comply with the traceability principle of metrology. The present invention achieves the machine traceability feature by tracing the unit definition back to the SI reference point.

[0013] Furthermore, the unit-based digital expression metamodel includes:

[0014] A type definition module is used to compare and represent the basic concepts of the original value data to obtain comparison data; and to check the type definition and expression specification of the declaration verification data to obtain type check data;

[0015] A machine interpretable module is used to perform mode conversion and standard expression on the comparison data to obtain conversion data; perform strict mode conversion and regular expression verification on the type check data to obtain verification data;

[0016] The machine traceability module is used to perform unit inspection and traceability on the conversion data to obtain traceability data; perform unit definition comparison and traceability capability inspection on the verification data to obtain the value data verification result;

[0017] The header file declaration module is used to generate a file for the traceability data based on the declaration information to obtain digitally represented quantity data; based on the declaration information, perform version, syntax and format verification on the digitally represented quantity data to obtain declaration verification data.

[0018] Furthermore, the type definition module includes:

[0019] A real quantity submodule is used to describe a single real quantity value and its related attributes using related information including measurement value, unit, optional label, timestamp and measurement uncertainty, and obtain comparison data representing the real quantity value; check the declaration verification data of the real quantity value to obtain type check data of the real quantity value;

[0020] A constant submodule for obtaining comparative data representing the value and related characteristics of a constant value using the value, unit, optional tag, timestamp, uncertainty and distribution information of the specified constant; checking the declaration verification data of the constant value to obtain type checking data of the constant value;

[0021] A complex quantum module is used to represent the complex value in the form of Cartesian coordinates and polar coordinates using the real part, the imaginary part and the unit information to obtain comparison data of the complex value; and to check the declaration verification data of the complex value to obtain type check data of the complex value;

[0022] A real quantity list submodule for obtaining comparison data of a real quantity value list using multiple real quantity submodule elements, optional labels of the list, timestamps, units, and global measurement uncertainty declarations to represent independent measurements and multivariate vector quantities; checking declaration verification data of the real quantity value list to obtain type check data of the real quantity value list;

[0023] The real quantity XML list submodule is used to separate the list data by spaces to obtain the comparison data of the real quantity value list based on the XML type; check the declaration verification data of the real quantity value list based on the XML type to obtain the type check data of the real quantity value list based on the XML type;

[0024] A complex quantity list submodule is used to process a set of multiple complex quantity values ​​using multiple complex quantity submodule elements, list labels, timestamps, units and uncertainty statements to obtain comparison data of the complex quantity value list; check the statement verification data of the complex quantity value list to obtain type check data of the complex quantity value list;

[0025] A hybrid quantum module is used to add measurement values ​​in SI units and non-SI units to a machine-readable format using real numbers, complex numbers, various lists and constant types of measurement values ​​to obtain comparison data of the mixed value; and to check the declaration verification data of the mixed value to obtain type checking data of the mixed value;

[0026] The expanded uncertainty submodule is used to define various parameters of the expanded measurement uncertainty using uncertainty value, coverage factor, coverage probability and optional distribution information, and obtain comparative data representing the structure of the expanded measurement uncertainty; check the declaration verification data of the expanded uncertainty to obtain type check data of the expanded uncertainty;

[0027] The inclusion interval submodule is used to describe the range and probability characteristics of measurement uncertainty using standard uncertainty, interval minimum, interval maximum and inclusion probability information, and obtain comparative data representing the probability symmetric inclusion interval structure; check the declaration verification data of the inclusion interval to obtain the type check data of the inclusion interval;

[0028] The covariance matrix submodule is used to describe the covariance relationship between multi-dimensional measurement values ​​using multiple column elements containing covariance values ​​and their units, and obtain the comparison data of the covariance matrix; check the declaration verification data of the covariance matrix to obtain the type check data of the covariance matrix;

[0029] The elliptical region submodule is used to describe the uncertainty range of multivariate measurement quantities by defining a hyperellipsoidal inclusion region using covariance matrix, inclusion factor, inclusion probability and optional distribution information, declare the uncertainty of complex values, lists of real values ​​and lists of complex values, and obtain comparative data of the hyperellipsoidal inclusion region structure representing the uncertainty of multivariate quantities; check the declaration verification data of the elliptical region to obtain the type check data of the elliptical region;

[0030] The rectangular region submodule is used to describe the uncertainty of multivariate measurement quantities through a hyper-rectangular inclusion region using covariance matrices, inclusion factors, inclusion probabilities, and optional distribution information, declare the uncertainty of complex values, lists of real values, and lists of complex values, and obtain comparative data of the hyper-rectangular inclusion region structure representing the uncertainty of multivariate quantities; and check the declaration verification data of the rectangular region to obtain type check data of the rectangular region.

[0031] Furthermore, the machine interpretable module includes:

[0032] A strict mode definition unit, used for performing a strict mode conversion on the comparison data to obtain strict mode data; converting the type check data to a strict mode to obtain strict mode check data;

[0033] The regular mode definition unit is used to perform a regular expression on the strict mode conversion data based on a regular expression to obtain conversion data; and perform a regular expression verification on the strict mode check data to obtain verification data.

[0034] Furthermore, the machine traceability module includes:

[0035] An enumeration type definition unit is used to provide standardized identification information for measurement units and prefixes, and obtain traceability information of units in the conversion data to their authoritative definitions; perform unit definition comparison on the verification data to obtain unit definition comparison results;

[0036] The metadata description unit is used to define the relationship between elements and types based on the traceability information, build data processing flow and logic, and obtain traceability data; based on the unit definition comparison result, perform traceability capability check and obtain measurement data verification result.

[0037] Further, the S2 includes:

[0038] Comparing and expressing the basic concepts of the original quantity value data to obtain comparative data;

[0039] Performing mode conversion and standard expression on the comparison data to obtain conversion data;

[0040] Performing unit inspection and tracing on the conversion data to obtain traceability data;

[0041] Based on the declaration information, a file is generated for the traceability data to obtain digitally represented quantity value data.

[0042] Further, the S3 includes:

[0043] Based on the declaration information, checking the version, syntax and format of the digitally represented quantity value data to obtain declaration verification data;

[0044] Checking the type definition and expression specification of the declaration verification data to obtain type checking data;

[0045] Performing strict mode conversion and regular expression verification on the type check data to obtain verification data;

[0046] The verification data is subjected to unit definition comparison and traceability check to obtain the measurement data verification result.

[0047] The beneficial effects of the present invention are: a meta-model-based digital representation method for measurement data, which can realize unambiguous, automated, full-process and intelligent data exchange and integration of measurement data information between different systems, while meeting the requirements of measurement standards and information technology standards, and has the significant advantages of high accuracy, machine interpretability and traceability. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] This specification will be further described in the form of exemplary embodiments, which will be described in detail by the accompanying drawings. These embodiments are not restrictive, and in these embodiments, the same number represents the same structure, wherein:

[0049] Figure 1 It is an exemplary flow chart of a method for digitally representing quantity data based on a metamodel according to some embodiments of the present specification. DETAILED DESCRIPTION

[0050] The specific implementation modes of the present invention are described below so that those skilled in the art can understand the present invention. However, it should be clear that the present invention is not limited to the scope of the specific implementation modes. For those of ordinary skill in the art, as long as various changes are within the spirit and scope of the present invention as defined and determined by the attached claims, these changes are obvious, and all inventions and creations utilizing the concept of the present invention are protected.

[0051] Example

[0052] Figure 1 FIG. 1 is an exemplary flow chart of a method for digitally representing measurement data based on a metamodel according to some embodiments of this specification. Figure 1 As shown, the process includes the following steps. In some embodiments, the process can be executed by a processor.

[0053] S1: Construct a meta-model for digital expression of units.

[0054] The unit digital expression metamodel is a metamodel used to digitally represent and verify quantity data.

[0055] In some embodiments, the unit-based digital expression metamodel may include a type definition module, a machine interpretable module, a machine traceable module, and a header file declaration module.

[0056] The type definition module is used to compare and represent the basic concepts of the original value data to obtain comparison data; and to check the type definition and expression specifications of the declaration verification data to obtain type check data.

[0057] The original measurement data is the measurement data to be converted. For example, the original measurement data may include paper data, non-digital data, and data that does not meet the requirements of machine interpretability and traceability. The types of the original measurement data may include real quantities, constants, complex quantities, real quantity lists, real quantity XML lists, complex quantity lists, mixed measurement values, expanded uncertainties, inclusion intervals, covariance matrices, elliptical areas, and rectangular areas.

[0058] The comparison data is the original quantity data after the basic concepts are compared. For example, the comparison data may include comparison data of real quantity values, comparison data of the values ​​and related characteristics of constant quantity values, comparison data of complex quantity values, comparison data of real quantity value lists, comparison data of real quantity value lists based on XML type, comparison data of complex quantity value lists, comparison data of mixed quantity values, comparison data of structures representing extended measurement uncertainty, comparison data of probability symmetric inclusion interval structures, comparison data of covariance matrices, comparison data of super-ellipsoid inclusion region structures representing multivariate quantity uncertainty, and comparison data of super-rectangular inclusion region structures representing multivariate quantity uncertainty, etc.

[0059] The declaration verification data is data reflecting the syntax and format check results of the digitally represented quantity data. For example, the declaration verification data may include the declaration verification data of real quantity values, the declaration verification data of constant quantity values, the declaration verification data of complex quantity values, the declaration verification data of real quantity value lists, the declaration verification data of real quantity value lists based on XML type, the declaration verification data of complex quantity value lists, the declaration verification data of mixed quantity values, the declaration verification data of extended uncertainty, the declaration verification data of included intervals, the declaration verification data of covariance matrices, the declaration verification data of elliptical areas, and the declaration verification data of rectangular areas.

[0060] The type check data is data reflecting the type definition and expression specification check status of the declaration verification data. For example, the type check data may include type check data of real quantity values, type check data of constant quantity values, type check data of complex quantity values, type check data of real quantity value lists, type check data of real quantity value lists based on XML type, type check data of complex quantity value lists, type check data of mixed quantity values, type check data of extended uncertainty, type check data of included intervals, type check data of covariance matrices, type check data of elliptical areas, and type check data of rectangular areas.

[0061] In some embodiments, the type definition module may include a real number quantum module, a constant submodule, a complex number quantum module, a real number list submodule, a real number XML list submodule, a complex number list submodule, a hybrid quantum module, an extended uncertainty submodule, an inclusion interval submodule, a covariance matrix submodule, an elliptical region submodule, and a rectangular region submodule.

[0062] The real quantity submodule is used to describe a single real quantity value and its related attributes using related information including measurement value, unit, optional label, timestamp and measurement uncertainty to obtain comparison data representing the real quantity value; check the declaration verification data of the real quantity value to obtain type check data of the real quantity value.

[0063] In some embodiments, the metadata description model defined by the real quantity quantum module may include 5 fields, of which 2 required fields are value and unit; 3 optional fields are label, timestamp, and measurement uncertainty. Among them, the two required fields indicate the two parts that a complete quantity value information must contain: value and unit. In the optional fields, the label describes the name and meaning of the quantity value, such as "the temperature measured by the sensor", the timestamp indicates the specific time when the quantity value data is generated, and the measurement uncertainty indicates the uncertainty information of the quantity value determined after uncertainty evaluation.

[0064] In some embodiments, the real quantity quantum module can be used to represent the metadata of a real quantity value, including the measurement value, unit, optional label and timestamp, and related information of measurement uncertainty, which is used to accurately describe a single real quantity value and its related attributes. For the quantity data "T = 306.32K, U = 0.061K", it can be expressed as:

[0065] <si:real>

[0066] <si:value> 306.32< / si:value>

[0067] <si:unit> \kelvin< / si:unit>

[0068] <si:expandunc>

[0069] <si:value> 0.061< / si:value>

[0070] <si:unit> \kelvin< / si:unit>

[0071] < / si:expandunc>

[0072] < / si:real>

[0073] This quantity data contains two inseparable atomic parts: the measured quantity value and the measurement uncertainty. For the description of the measured quantity value, it contains the measured value and unit, its value is 306.32, it is represented by a floating point type, its unit is Kelvin, and the identifier used is "\kelvin"; for the description of the measurement uncertainty, it also contains the value and unit, its value is 0.061, it is represented by a floating point type, its unit should be consistent with the measured quantity value, Kelvin, and it is represented by the identifier "\kelvin". This allows the complete transmission of various information about the measured quantity when real quantity value data is exchanged.

[0074] The constant submodule is used to obtain comparative data representing the numerical value and related characteristics of the constant value by using the value, unit, optional tag, timestamp, uncertainty and distribution information of the specified constant; and to check the declaration verification data of the constant value to obtain the type check data of the constant value.

[0075] In some embodiments, the metadata description model defined in the constant submodule may include 6 fields, 2 required fields are value and unit, and 4 optional fields are label, timestamp, uncertainty value and probability distribution type.

[0076] In some embodiments, the constant submodule can be used to represent constants, including structures of basic physical constants and mathematical constants. In addition to containing values, units, optional tags and timestamps, it can also specify the uncertainty and distribution information of the constants. It is suitable for defining constants with specific properties in the data model to ensure that when processing data related to physical or mathematical constants, its numerical value and related characteristics can be accurately represented. For example, for the "Euler constant e", its digital representation is:

[0077] <si:constant>

[0078] <si:label> Euler number e< / si:label>

[0079] <si:value> 2.71828182845904523536< / si:value>

[0080] <si:unit> \one< / si:unit>

[0081] <si:uncertainty> 0.000000000000000000005< / si:uncertainty>

[0082] <si:distribution> rectangular< / si:distribution>

[0083] < / si:constant>

[0084] For the representation of Euler constant, its data structure should be represented by the specification defined in the submodule "constant", including label, value, unit, uncertainty, and probability distribution type fields. Among them, the label specifies the name and meaning of the constant, the value represents the specific numerical part, the unit field indicates the identifier of the SI unit used by the constant, the uncertainty field indicates the numerical part of the uncertainty, and implies the unit consistent with the constant, and the probability distribution information indicates what probability distribution method is used to calculate the uncertainty of the constant.

[0085] The complex quantum module is used to use the real part, the imaginary part and the unit information to represent the complex value in the form of either Cartesian coordinates or polar coordinates to obtain comparison data of the complex value; and to check the declaration verification data of the complex value to obtain type check data of the complex value.

[0086] In some embodiments, for a complex quantity value, its representation may be:

[0087] <si:complex>

[0088] <si:valuereal> -10.310< / si:valuereal>

[0089] <si:valueimag> 5.010< / si:valueimag>

[0090] <si:unit> \metre< / si:unit>

[0091] < / si:complex>

[0092] Its representation includes three parts: real part, imaginary part and unit. The real part and imaginary part are both represented by numerical types, and the unit indicates the identifier of the SI unit used for the complex value.

[0093] In some embodiments, the complex quantum module can be used to define the structure of complex quantities in the metadata model, allowing complex values ​​to be represented in Cartesian coordinate form or polar coordinate form, containing corresponding real part, imaginary part (or amplitude, phase) and unit information, and can also represent measurement uncertainty. It is used to process complex values ​​and plays a role when complex data processing is involved (such as signal processing, circuit analysis and other fields).

[0094] The real quantity list submodule is used to use multiple real quantity submodule elements, optional labels of the list, timestamps, units and global measurement uncertainty declarations to represent independent measurements and multivariate vector quantities, and obtain comparison data of real quantity value lists; check the declaration verification data of real quantity value lists to obtain type check data of real quantity value lists.

[0095] In some embodiments, the metadata description model defined in the real quantity list submodule may include 4 fields, 1 required field is a data structure defined by one or more real quantity submodules, expressed in list form, and 3 optional fields include a label list or timestamp list, a single variable uncertainty list, and a multivariate uncertainty list.

[0096] In some embodiments, the real quantity list submodule is used to represent the metadata element of the real quantity value list, which can represent independent measurements or multivariate vector quantities. It can contain multiple real quantity submodule elements and provide optional labels, timestamps, units and global measurement uncertainty statements for the list. It can also represent multivariate uncertainty and is suitable for batch processing of multiple related real quantity values, such as in batch processing and analysis scenario applications of experimental data.

[0097] The real quantity XML list submodule is used to separate the list data by spaces to obtain the comparison data of the real quantity value list based on the XML type; check the declaration verification data of the real quantity value list based on the XML type to obtain the type check data of the real quantity value list based on the XML type.

[0098] In some embodiments, the metadata description model defined in the real quantity XML list submodule may include four fields: one required field is a numerical list represented by the XML built-in list, and three optional fields are a label or timestamp list, a single variable uncertainty list, and a multivariate uncertainty list.

[0099] In some embodiments, the real quantity XML list submodule can be used to represent metadata elements of real quantity value lists based on the XML type. Its function is similar to that of the real quantity list submodule, but the data storage method is different. The list data is separated by spaces, which can save memory and is suitable for the storage and processing of large data sets.

[0100] The complex quantity list submodule is used to process the collection of multiple complex quantity values ​​using multiple complex quantity submodule elements, list labels, timestamps, units and uncertainty declarations to obtain comparison data of the complex quantity value list; and to check the declaration verification data of the complex quantity value list to obtain type check data of the complex quantity value list.

[0101] In some embodiments, the metadata description model defined in the complex quantity list submodule may include 4 fields, 1 required field is a data structure defined by one or more complex quantity submodules, expressed in list form, and 3 optional fields include a label list or timestamp list, a single variable uncertainty list, and a multivariate uncertainty list.

[0102] In some embodiments, the complex quantity list submodule can be used to represent the metadata element of the complex quantity value list, which is used to represent a set of complex quantity values. It contains multiple complex quantity submodule elements and the relevant attributes of the list (such as labels, timestamps, units, uncertainty statements, etc.), which can be used to process a set of multiple complex quantity values ​​and is used in complex data batch processing scenarios.

[0103] The hybrid quantum module is used to add the measurement values ​​using SI units and non-SI units into a machine-readable format using real numbers, complex numbers, various lists and constant types of measurement values ​​to obtain comparison data of the mixed values; and to check the declaration verification data of the mixed values ​​to obtain type checking data of the mixed values.

[0104] In some embodiments, the hybrid quantum module can add measurement values ​​of different units to a machine-readable format, including real numbers, complex numbers, various lists, and constant types of measurement values, providing a flexible way to handle combinations of values ​​that may involve multiple units, adapting to the representation of measurement data in different unit systems or special needs, and playing a role in scenarios that need to process mixed unit measurement values.

[0105] The expanded uncertainty submodule is used to define various parameters of the expanded measurement uncertainty using uncertainty value, coverage factor, coverage probability and optional distribution information, and obtain comparative data representing the structure of the expanded measurement uncertainty; and to check the declaration verification data of the expanded uncertainty to obtain type check data of the expanded uncertainty.

[0106] In some embodiments, the extended uncertainty submodule can be used to represent the structure of extended measurement uncertainty, which is a way of expressing measurement uncertainty. It includes uncertainty value, coverage factor, coverage probability and optional distribution information, and clearly defines various parameters of extended measurement uncertainty. It is used when accurately representing measurement uncertainty, which helps to improve the credibility and interpretability of measurement results.

[0107] The inclusion interval submodule is used to describe the range and probability characteristics of measurement uncertainty using standard uncertainty, interval minimum value, interval maximum value and inclusion probability information, and obtain comparative data representing the probability symmetric inclusion interval structure; check the declaration verification data of the inclusion interval to obtain type check data of the inclusion interval.

[0108] In some embodiments, the inclusion interval submodule can be used to represent the structure of probability symmetric inclusion intervals, which is also a form of representation of measurement uncertainty. It contains information such as standard uncertainty, interval minimum, interval maximum, and coverage probability, and in this way describes in detail the range and probability characteristics of measurement uncertainty, which is used when processing measurement uncertainty with interval representation.

[0109] The covariance matrix submodule is used to describe the covariance relationship between multi-dimensional measurement values ​​using multiple column elements containing covariance values ​​and their units, and obtain the comparison data of the covariance matrix; check the declaration verification data of the covariance matrix to obtain the type check data of the covariance matrix.

[0110] In some embodiments, the covariance matrix submodule can be used to represent the covariance matrix elements of the multidimensional uncertainty statement in the metadata model. By including multiple column elements (each column element includes a covariance value and its unit) to describe the covariance relationship between the multidimensional measurement values, it is used when processing multiple related measurements and the covariance between them needs to be considered, which helps to more comprehensively evaluate the uncertainty of the measurement results.

[0111] The elliptical region submodule is used to describe the uncertainty range of multivariate measurement quantities by defining a hyperellipsoidal inclusion region using covariance matrix, inclusion factor, inclusion probability and optional distribution information, declare the uncertainty of complex values, real value lists and complex value lists, and obtain comparative data of the hyperellipsoidal inclusion region structure representing the uncertainty of multivariate quantities; check the declaration verification data of the elliptical region to obtain the type check data of the elliptical region.

[0112] In some embodiments, the elliptical region submodule can be used to represent the structure of a hyper-ellipsoid inclusion region of multivariate quantity uncertainty, for uncertainty declarations of complex quantities and lists of real or complex values, including a covariance matrix, inclusion factors, inclusion probabilities, and optional distribution information, and to describe the uncertainty range of multivariate measurement quantities by defining a hyper-ellipsoid inclusion region, which is used when processing uncertainty representations of multivariate measurement data.

[0113] The rectangular region submodule is used to describe the uncertainty of multivariate measurement quantities through a hyper-rectangular inclusion region using covariance matrices, inclusion factors, inclusion probabilities, and optional distribution information, declare the uncertainty of complex values, lists of real values, and lists of complex values, and obtain comparative data of the hyper-rectangular inclusion region structure representing the uncertainty of multivariate quantities; and check the declaration verification data of the rectangular region to obtain type check data of the rectangular region.

[0114] In some embodiments, the rectangular region submodule can be used to represent the structure of a hyperrectangular region containing the uncertainty of a multivariate quantity, and is also used for uncertainty declarations of complex values ​​and lists of real or complex values. Similar to the elliptical region submodule, it contains relevant information such as the covariance matrix, and describes the uncertainty of a multivariate measurement quantity through a hyperrectangular region, providing another way to represent the uncertainty of multivariate measurement data.

[0115] The machine interpretable module is used to perform mode conversion and standard expression on the comparison data to obtain conversion data; and perform strict mode conversion and regular expression verification on the type check data to obtain verification data.

[0116] Transformed data are comparative data in standardized expressions.

[0117] The verification data is data reflecting the strict mode conversion of the type check data and the regular expression verification status.

[0118] In some embodiments, the machine interpretable module may include a strict mode definition unit and a regular mode definition unit.

[0119] The strict mode definition unit is used to perform strict mode conversion on the comparison data to obtain strict mode data; and convert the type check data into strict mode to obtain strict mode check data.

[0120] In some embodiments, the original data is of string type and cannot be fully formatted. Therefore, the simple string type is converted to a strict type with regular expression restrictions, that is, the original "<xs:restrictionbase="xs:string"> ” is converted to “<xs:restriction base="xs:string"><xs:patternvalue=pattern> ”.

[0121] The regular mode definition unit is used to perform a regular expression on the strict mode conversion data based on a regular expression to obtain conversion data; and perform a regular expression verification on the strict mode check data to obtain verification data.

[0122] In some embodiments, the use of strict unit definition units and regular pattern definition units ensures that the units used in the XML document conform to the predefined SI unit rules, ensures the consistency and accuracy of unit representation, and facilitates correct parsing and operation in applications involving unit processing (such as metrological data exchange, scientific computing, etc.). It helps prevent misunderstandings or calculation errors caused by incorrect unit formats and improves the reliability and interoperability of data processing.

[0123] The machine traceability module is used to perform unit inspection and traceability on the conversion data to obtain traceability data; perform unit definition comparison and traceability capability inspection on the verification data to obtain the measurement data verification result.

[0124] Traceable data is conversion data that is traceable to an SI Digital Reference Point (SIRP).

[0125] The measurement data verification result is a verification result that reflects whether the calibration data has the ability to be traced back to SIRP.

[0126] In some embodiments, the machine traceability module may include an enumeration type definition unit and a metadata description unit.

[0127] The enumeration type definition unit is used to provide standardized identification information for measurement units and prefixes, and obtain traceability information of units in the conversion data to their authoritative definitions; and perform unit definition comparison on the verification data to obtain unit definition comparison results.

[0128] In some embodiments, the enumeration type definition unit defines the complex types of all legal SI units and prefixes and their related metadata frameworks. For example, the unit "metre" has a type definition of "<xs:element name="metre"type="si:metreType" / > ". The element type and its corresponding attributes are defined for the unit, so that the reuse of the unit is realized under the framework of the present invention.

[0129] Traceability information is information that reflects the conversion of units in data to their authoritative definitions.

[0130] The unit definition comparison result is a result reflecting the comparison between the unit in the verification data and the unit definition in the enumeration type definition unit.

[0131] The metadata description unit is used to define the relationship between elements and types based on the traceability information, build data processing flow and logic, and obtain traceability data; based on the unit definition comparison result, perform traceability check and obtain the value data verification result. For example, for the unit "ampere", it should include unit name, symbol, identifier, unit type and other information, and its unit name is "unitName=ampere", symbol is "symbol=A", identifier is "dsiId=\ampere", unit type is "type=SI base unit", etc.

[0132] The header file declaration module is used to generate a file for the traceability data based on the declaration information to obtain digitally represented quantity data; based on the declaration information, perform version, syntax and format checks on the digitally represented quantity data to obtain declaration verification data.

[0133] The declaration information is information that declares the version and namespace conditions. For example, the declaration information may include a version declaration and a namespace declaration.

[0134] The version declaration specifies the XML version, character encoding format (UTF-8) and version number of the metamodel that the metamodel follows, which facilitates version management and identifies the evolution of the schema. For example, when the declaration information is "xs:schema version="2.1.0"" (using the metamodel version 2.1.0), files using other version numbers will not pass validation.

[0135] The namespace declaration defines the prefix of the namespace and declares the target namespace to which the elements and types defined by the metamodel belong. It is used to distinguish metamodel patterns from different sources, ensure that standard syntax and semantics are followed when defining the metamodel, avoid conflicts in element and type names, and ensure the uniqueness and consistency of elements in different namespaces. For example, when the namespace declaration is "targetNamespace="https: / / www.nim.ac.cn / si"" (the metamodel released by the National Institute of Metrology), frameworks released by other organizations or institutions will not pass verification.

[0136] The digitally represented quantity value data is a file of the digitally represented quantity value data in a complete common format and in compliance with the version specification.

[0137] In some embodiments, the enumeration type definition unit provides standardized identification information for units of measurement and prefixes, including their definitions, conversion relationships, etc., thereby achieving traceability from units in the data to their authoritative definitions. The metadata description unit defines the relationship between elements and types. This relationship information helps to build data processing flows and logic. When performing data exchange and integration, the system can determine how to correctly combine and process different types of data based on this relationship information to ensure data consistency throughout the system. In addition, for complex data structures, metadata descriptions provide guidance for understanding and processing these structures, avoiding errors during data operations and promoting data standardization and interoperability.

[0138] S2: Based on the unit system digital expression metamodel, the original quantity value data is converted into a mode to obtain digitally represented quantity value data.

[0139] In some embodiments, the processor can implement S2 based on the following steps: comparing and representing the basic concepts of the original measurement data to obtain comparison data; performing pattern conversion and standard expression on the comparison data to obtain conversion data; performing unit inspection and tracing on the conversion data to obtain traceability data; based on declaration information, generating a file for the traceability data to obtain digitally represented measurement data.

[0140] In some embodiments, the processor can input the initial quantity value data of "the measured value is 20m kg s-2" into the unit digital expression metamodel, use the type definition module to confirm the category of the concept contained in the input, and determine how to express it. "Measurement value" means that the information is a quantity value, and the "value + unit" representation mode should be used; "135m kg s-2" means that the value is 135, and the unit is m kg s-2, which is used as the comparison data of the initial quantity value data.

[0141] In some embodiments, the processor may construct a strict mode field from the strict mode definition unit based on the comparison data, such as that which may be represented in XML as " <strictunit> <value>135<\value><\unit>m kg s-2<\unit><\strictUnit>", as the strict mode check data; the strict mode check data is standardized by using the regular mode definition unit. For example, from the field "<\unit>m kg s-2<\unit>", it can be converted into the "<\unit>\metre\kilogram\second\tothe{-2}<\unit>" format that complies with the rules to obtain the converted data.

[0142] In some embodiments, the processor can use enumeration type definition units to provide standardized identification information for measurement units and prefixes. For example, after comparison, it can be obtained that "\metre\kilogram\second\tothe{-2}" is a derived unit, and its derived unit is "Newton". It can be represented by "\newton" to obtain traceability information of converting units in data to their authoritative definitions; using metadata description units, based on traceability information, define the relationship between elements and types, build data processing processes and logic, and trace the units to SIRP to achieve machine traceability of measurement units. For example, after tracing, "\newton" can obtain its persistent identifier "https: / / si-digital-framework.org / SI / units / newton" as traceability data.

[0143] In some embodiments, the processor may use a header file to declare a module and, based on the declaration information, write "mkg s -2 "Unit conversion to"<newton\> "Form, get" <value>135<\value><\unit>\newton<\unit>” information as numerically expressed quantity data.

[0144] S3: Based on the unit system digital expression metamodel, the digitally represented quantity data is verified to obtain a quantity data verification result, thereby completing the digital representation of the quantity data.

[0145] In some embodiments, the processor can implement S3 based on the following steps: based on the declaration information, performing version, syntax and format checks on the digitally represented value data to obtain declaration verification data; performing type definition and expression specification checks on the declaration verification data to obtain type check data; performing strict mode conversion and regular expression verification on the type check data to obtain verification data; performing unit definition comparison and traceability check on the verification data to obtain the value data verification result.

[0146] In some embodiments, the processor can use the header file declaration module to perform syntax and format checks on the digitally represented value data. For example, the input can be checked to see if it complies with the metamodel version and namespace based on the version declaration (P001) and namespace declaration (P002) in the metamodel. Taking XML as an example, if the input prefix is ​​"si:unit", it complies with the declaration; if it is "unit", it indicates that the namespace declaration is missing, and an error message should be returned as declaration verification data.

[0147] In some embodiments, the processor may utilize a type definition module to perform strict mode conversion and regular expression verification on the type check data, for example, " <real>"Should contain at least" <value>"and" <unit>" If any of the two fields is missing, the format is wrong and an error message is returned to obtain the verification data.

[0148] In some embodiments, the processor can use the machine traceability module to perform unit definition comparison and traceability check on the verification data, for example, <unit>The content in the " field is converted to " <strictunit>"Field Pair" <strictunit>The content "\newton" in " is checked, such as "\prefix? \unit\exponent?". If it does not meet the rules, an error message is output; the metadata of the check result is compared. For example, "\newton" will be determined as the derived unit "Newton". If the match fails in this step, an error message is output; if it succeeds, its traceability is further checked. Based on the "Newton" information, it can be checked whether it can be traced back according to the metadata of SIRP stored in the enumeration type definition unit. If not, an error message is output; if it can, the information that passed the verification and the metadata generated in the process are output to obtain the verification result of the measurement data.

[0149] In some embodiments, the digital expression meta-model of the unit system can be used for the generation function of the system. The paper or PDF version of the file containing the measurement data information is input into the system or the system function is called through the API. The system calls the metadata model. After identification and comparison, the metadata model returns a digital unit representation in a machine-interpretable and traceable XML format to the system. The system can present the digital representation of the measurement data information on the front end or return it to the user through the API; for the verification function of the system, the user needs to upload the measurement data information to be verified to the system. The system calls the metadata model for comparison and verification. After the verification is completed, the verification result is returned to the user through the user upload channel.

[0150] In some embodiments of the present specification, a meta-model-based digital representation method for measurement data can realize unambiguous, automated, full-process and intelligent data exchange and integration of measurement data information between different systems, while meeting the requirements of measurement standards and information technology standards, and has the significant advantages of high accuracy, machine interpretability and traceability.

[0151] (1) The digital representation scheme of units based on ontology has a variety of serialization forms, such as RDF, RDFS and OWL. The XML format adopted by the present invention has good versatility and can be read and processed by different systems; the digital representation scheme of units based on ontology has a variety of structures, and the unit systems defined by different organizations are different and inconsistent. The present invention is developed based on authoritative standards and specifications in the field of metrology and has versatility and consistency; although the digital representation scheme of units based on ontology provides relatively rich semantic information, it cannot be understood by computers and still requires hard coding to utilize the semantic information. The metadata model of the present invention realizes machine interpretability, and there is no need for different systems to hard code again to implement functions;

[0152] (2) The digital representation solution of units based on unit identifiers relies on traditional string matching technology and cannot detect the same SI unit expressions of different non-SI units, while the metadata model defined in the present invention can detect them; the digital representation solution of units based on unit identifiers cannot determine different expression formats of the same unit, while the metadata model defined in the present invention can identify, for example, the non-SI expression form and SI unit expression form of the derived unit; the digital representation solution of units based on unit identifiers only includes the basic name of the unit and the corresponding identifier string, and lacks metadata description. The metadata model proposed in the present invention provides a metadata description framework, which describes the unit information more comprehensively according to the requirements of the SI manual;

[0153] (3) A single unit identifier does not contain the original definition data of the measurement unit, which does not comply with the traceability principle of metrology. The present invention achieves the machine traceability feature by tracing the unit definition back to the SI reference point.< / strictunit> < / strictunit> < / unit> < / unit> < / value> < / real> < / value> < / value> < / strictunit>

Claims

1. A method for digitally representing quantity data based on a metamodel, characterized in that: include: Construct a digital expression meta-model of the unit system; Based on the unit system digital expression metamodel, the original value data is converted into a mode to obtain digitally represented value data; Based on the unit system digital expression metamodel, the digitally represented quantity data is verified to obtain a quantity data verification result, thereby completing the digital representation of the quantity data.

2. The method for digitally representing value data based on a metamodel according to claim 1, characterized in that: The unit system digital expression metamodel includes: A type definition module is used to compare and represent the basic concepts of the original value data to obtain comparison data; and to check the type definition and expression specification of the declaration verification data to obtain type check data; A machine interpretable module is used to perform mode conversion and standard expression on the comparison data to obtain conversion data; perform strict mode conversion and regular expression verification on the type check data to obtain verification data; The machine traceability module is used to perform unit inspection and traceability on the conversion data to obtain traceability data; perform unit definition comparison and traceability capability inspection on the verification data to obtain the value data verification result; The header file declaration module is used to generate a file for the traceability data based on the declaration information to obtain digitally represented quantity data; based on the declaration information, perform version, syntax and format verification on the digitally represented quantity data to obtain declaration verification data.

3. The method for digitally representing value data based on a metamodel according to claim 2, characterized in that: The type definition module includes: A real quantity submodule is used to describe a single real quantity value and its related attributes using related information including measurement value, unit, optional label, timestamp and measurement uncertainty, and obtain comparison data representing the real quantity value; check the declaration verification data of the real quantity value to obtain type check data of the real quantity value; A constant submodule for obtaining comparative data representing the value and related characteristics of a constant value using the value, unit, optional tag, timestamp, uncertainty and distribution information of the specified constant; checking the declaration verification data of the constant value to obtain type checking data of the constant value; A complex quantum module is used to represent the complex value in the form of Cartesian coordinates and polar coordinates using the real part, the imaginary part and the unit information to obtain comparison data of the complex value; and to check the declaration verification data of the complex value to obtain type check data of the complex value; A real quantity list submodule for obtaining comparison data of a real quantity value list using multiple real quantity submodule elements, optional labels of the list, timestamps, units, and global measurement uncertainty declarations to represent independent measurements and multivariate vector quantities; checking declaration verification data of the real quantity value list to obtain type check data of the real quantity value list; The real quantity XML list submodule is used to separate the list data by spaces to obtain the comparison data of the real quantity value list based on the XML type; check the declaration verification data of the real quantity value list based on the XML type to obtain the type check data of the real quantity value list based on the XML type; A complex quantity list submodule is used to process a set of multiple complex quantity values ​​using multiple complex quantity submodule elements, list labels, timestamps, units and uncertainty statements to obtain comparison data of the complex quantity value list; check the statement verification data of the complex quantity value list to obtain type check data of the complex quantity value list; A hybrid quantum module is used to add measurement values ​​in SI units and non-SI units to a machine-readable format using real numbers, complex numbers, various lists and constant types of measurement values ​​to obtain comparison data of the mixed value; and to check the declaration verification data of the mixed value to obtain type checking data of the mixed value; The expanded uncertainty submodule is used to define various parameters of the expanded measurement uncertainty using uncertainty value, coverage factor, coverage probability and optional distribution information, and obtain comparative data representing the structure of the expanded measurement uncertainty; check the declaration verification data of the expanded uncertainty to obtain type check data of the expanded uncertainty; The inclusion interval submodule is used to describe the range and probability characteristics of measurement uncertainty using standard uncertainty, interval minimum, interval maximum and inclusion probability information, and obtain comparative data representing the probability symmetric inclusion interval structure; check the declaration verification data of the inclusion interval to obtain the type check data of the inclusion interval; The covariance matrix submodule is used to describe the covariance relationship between multi-dimensional measurement values ​​using multiple column elements containing covariance values ​​and their units, and obtain the comparison data of the covariance matrix; check the declaration verification data of the covariance matrix to obtain the type check data of the covariance matrix; The elliptical region submodule is used to describe the uncertainty range of multivariate measurement quantities by defining a hyperellipsoidal inclusion region using covariance matrix, inclusion factor, inclusion probability and optional distribution information, declare the uncertainty of complex values, lists of real values ​​and lists of complex values, and obtain comparative data of the hyperellipsoidal inclusion region structure representing the uncertainty of multivariate quantities; check the declaration verification data of the elliptical region to obtain the type check data of the elliptical region; The rectangular region submodule is used to describe the uncertainty of multivariate measurement quantities through a hyper-rectangular inclusion region using covariance matrices, inclusion factors, inclusion probabilities, and optional distribution information, declare the uncertainty of complex values, lists of real values, and lists of complex values, and obtain comparative data of the hyper-rectangular inclusion region structure representing the uncertainty of multivariate quantities; and check the declaration verification data of the rectangular region to obtain type check data of the rectangular region.

4. The method for digitally representing quantity data based on a metamodel according to claim 2, characterized in that: The machine interpretable module includes: A strict mode definition unit, used for performing a strict mode conversion on the comparison data to obtain strict mode data; converting the type check data to a strict mode to obtain strict mode check data; The regular mode definition unit is used to perform a regular expression on the strict mode conversion data based on a regular expression to obtain conversion data; and perform a regular expression verification on the strict mode check data to obtain verification data.

5. The method for digitally representing value data based on a metamodel according to claim 2, characterized in that: The machine traceability module includes: An enumeration type definition unit is used to provide standardized identification information for measurement units and prefixes, and obtain traceability information of units in the conversion data to their authoritative definitions; perform unit definition comparison on the verification data to obtain unit definition comparison results; The metadata description unit is used to define the relationship between elements and types based on the traceability information, build data processing flow and logic, and obtain traceability data; based on the unit definition comparison result, perform traceability capability check and obtain measurement data verification result.

6. The method for digitally representing value data based on a metamodel according to claim 1, characterized in that: The S2 includes: Comparing and expressing the basic concepts of the original quantity value data to obtain comparative data; Performing mode conversion and standard expression on the comparison data to obtain conversion data; Performing unit inspection and tracing on the conversion data to obtain traceability data; Based on the declaration information, a file is generated for the traceability data to obtain digitally represented quantity value data.

7. The method for digitally representing value data based on a metamodel according to claim 1, characterized in that: The S3 includes: Based on the declaration information, checking the version, syntax and format of the digitally represented value data to obtain declaration verification data; Checking the type definition and expression specification of the declaration verification data to obtain type checking data; Performing strict mode conversion and regular expression verification on the type check data to obtain verification data; The verification data is subjected to unit definition comparison and traceability check to obtain the measurement data verification result.

Images