CN116737157A - JSON conversion method, system, equipment and medium - Google Patents
JSON conversion method, system, equipment and medium Download PDFInfo
- Publication number
- CN116737157A CN116737157A CN202310708631.8A CN202310708631A CN116737157A CN 116737157 A CN116737157 A CN 116737157A CN 202310708631 A CN202310708631 A CN 202310708631A CN 116737157 A CN116737157 A CN 116737157A
- Authority
- CN
- China
- Prior art keywords
- value
- conversion
- key
- json
- script
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000006243 chemical reaction Methods 0.000 title claims abstract description 112
- 238000000034 method Methods 0.000 title claims abstract description 31
- 238000012217 deletion Methods 0.000 claims description 33
- 230000037430 deletion Effects 0.000 claims description 33
- 238000012545 processing Methods 0.000 claims description 11
- 238000004590 computer program Methods 0.000 claims description 7
- 230000008569 process Effects 0.000 claims description 6
- 230000001788 irregular Effects 0.000 claims description 5
- 238000013507 mapping Methods 0.000 claims description 5
- 238000006467 substitution reaction Methods 0.000 claims description 5
- 238000013519 translation Methods 0.000 claims 1
- 238000007792 addition Methods 0.000 description 23
- 230000009471 action Effects 0.000 description 6
- 238000011161 development Methods 0.000 description 4
- 210000001072 colon Anatomy 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 239000002360 explosive Substances 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/151—Transformation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Document Processing Apparatus (AREA)
Abstract
The application provides a JSON conversion method, a system, equipment and a medium, which relate to the technical field of data conversion and comprise the following steps: step S1: establishing a set of conversion rules, wherein the rules are also described by a JSON format; step S2: implementing the conversion rule as a black box tool; step S3, writing rules into a black box tool, and storing conversion rules inside the black box tool; step S4: the instantiated JSON is externally input to the black box tool, which internally converts according to rules. Step S5: the black box tool returns the result of the conversion to the outside as a play-out. The application can realize data conversion.
Description
Technical Field
The application relates to the technical field of data conversion, in particular to a JSON conversion method, a system, equipment and a medium.
Background
With the growth of various open platforms on the internet, the externally provided OpenAPI also shows explosive growth, the version of the API is updated frequently, the external system needs to be in butt joint with the OpenAPI, the requirements on fields are inconsistent for different platforms, for example, merchants need to upload commodity information to a plurality of platforms, and the workload of processing JSON access is huge.
The existing mode requires a developer to make corresponding development aiming at the field requirement of each platform, each platform needs to have corresponding conversion codes, and the development cost and the development time are relatively large.
Disclosure of Invention
Aiming at the defects in the prior art, the application provides a JSON conversion method, a JSON conversion system, JSON conversion equipment and a JSON conversion medium.
According to the JSON conversion method, the system, the equipment and the medium provided by the application, the scheme is as follows:
in a first aspect, a JSON conversion method is provided, the method including:
step S1: establishing a set of conversion rules, wherein the rules are described by a JSON format;
step S2: implementing the conversion rule as a black box tool class;
step S3: writing rules into a black box tool, and storing conversion rules inside the black box tool;
step S4: the external of the black box tool inputs the instantiated JSON into the black box tool, and the internal of the black box tool is converted according to rules;
step S5: the black box tool returns the result of the conversion to the outside as a play-out.
Preferably, the Key in the JSON object is Key, and the Value in the JSON object is Value;
the conversion rule includes: operating Key and Value;
wherein operating the Key comprises: adding brother nodes, deleting nodes, renaming and JS script conversion;
operating on Value includes: fixed value, substitution, head addition, middle addition, tail addition, head deletion, middle deletion, tail deletion, enumeration, and JS script conversion.
Preferably, the Key is operated, and sibling nodes are added: adding a Key Value pair of Key and Value behind the designated Key;
deleting the node: deleting Key Value pairs of Key and Value;
renaming: renaming Key;
JS script conversion: and the method is responsible for processing complex business logic, and character strings for converting the script into base64 are put into conversion rules after the script is written.
Preferably, the operating on Value, fixed Value: uniformly setting a designated character string no matter any Value is encountered;
replacement: replacing a specific character in the Value with other characters;
head addition: adding characters in front of the Value;
intermediate addition: adding characters at any position in the Value character string;
tail addition: adding characters at the tail of the Value character string;
head deletion: deleting the character in front of the Value character string;
intermediate deletion: deleting the character in the middle of the Value character string;
tail deletion: deleting the character with the specified length at the tail part of the Value character string;
enumerating: a group of key value pairs with one-to-one mapping relation, searching keys to find corresponding values, wherein the relation between the keys and the values is irregular;
JS script conversion: a section of JS script code is edited to process complex business logic, and the script needs to be encoded by base 64.
In a second aspect, there is provided a JSON conversion system, the system comprising:
module M1: establishing a set of conversion rules, wherein the rules are described by a JSON format;
module M2: implementing the conversion rule as a black box tool class;
module M3: writing rules into a black box tool, and storing conversion rules inside the black box tool;
module M4: the external of the black box tool inputs the instantiated JSON into the black box tool, and the internal of the black box tool is converted according to rules;
module M5: the black box tool returns the result of the conversion to the outside as a play-out.
Preferably, the Key in the JSON object is Key, and the Value in the JSON object is Value;
the conversion rule includes: operating Key and Value;
wherein operating the Key comprises: adding brother nodes, deleting nodes, renaming and JS script conversion;
operating on Value includes: fixed value, substitution, head addition, middle addition, tail addition, head deletion, middle deletion, tail deletion, enumeration, and JS script conversion.
Preferably, the Key is operated, and sibling nodes are added: adding a Key Value pair of Key and Value behind the designated Key;
deleting the node: deleting Key Value pairs of Key and Value;
renaming: renaming Key;
JS script conversion: and the method is responsible for processing complex business logic, and character strings for converting the script into base64 are put into conversion rules after the script is written.
Preferably, the operating on Value, fixed Value: uniformly setting a designated character string no matter any Value is encountered;
replacement: replacing a specific character in the Value with other characters;
head addition: adding characters in front of the Value;
intermediate addition: adding characters at any position in the Value character string;
tail addition: adding characters at the tail of the Value character string;
head deletion: deleting the character in front of the Value character string;
intermediate deletion: deleting the character in the middle of the Value character string;
tail deletion: deleting the character with the specified length at the tail part of the Value character string;
enumerating: a group of key value pairs with one-to-one mapping relation, searching keys to find corresponding values, wherein the relation between the keys and the values is irregular;
JS script conversion: a section of JS script code is edited to process complex business logic, and the script needs to be encoded by base 64.
In a third aspect, there is provided a computer readable storage medium storing a computer program which, when executed by a processor, implements steps in the JSON conversion method.
In a fourth aspect, an electronic device is provided that includes a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program when executed by the processor implementing steps in the JSON conversion method.
Compared with the prior art, the application has the following beneficial effects:
1. the new platform is docked without intervention of programmers, only configuration of service personnel is needed, and development cost is saved;
2. the configuration mode can greatly save the time of accessing the new platform and can also enhance the flexibility of docking.
Other advantages of the present application will be set forth in the description of specific technical features and solutions, by which those skilled in the art should understand the advantages that the technical features and solutions bring.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, given with reference to the accompanying drawings in which:
FIG. 1 is a flow chart of the present application.
Detailed Description
The present application will be described in detail with reference to specific examples. The following examples will assist those skilled in the art in further understanding the present application, but are not intended to limit the application in any way. It should be noted that variations and modifications could be made by those skilled in the art without departing from the inventive concept. These are all within the scope of the present application.
The embodiment of the application provides a JSON conversion method, which abstracts various conversions to be used as a tool, and the tool provides an interface for external use. Business personnel input rules to a tool according to the platform JSON, the tool stores the input rules, loads the rules during conversion, converts the rules, and outputs the converted rules to the outside. Referring to fig. 1, the method specifically includes the following:
step S1: establishing a set of conversion rules, wherein the rules are also described by a JSON format;
step S2: implementing the conversion rule as a black box tool;
step S3: writing rules into a black box tool, and storing conversion rules inside the black box tool;
step S4: the instantiated JSON is externally input to the black box tool, which internally converts according to rules.
Step S5: the black box tool returns the result of the conversion to the outside as a play-out.
In the scheme, the concrete noun explanation firstly confirms the concepts of Key and Value:
the JSON object is a string composed of a group of Key-Value pairs with nested relation, key is in front of the colon, value is behind the colon (the following text is not only the JSON object):
JSON Key (Key in JSON object is Key, such as in example: company code);
JSON Value (Value in JSON object is Value, such as in example: "alibaba", "2019-01-01");
the conversion rule includes: operating Key and Value;
wherein operating the Key comprises: adding brother nodes, deleting nodes, renaming and JS script conversion;
operating on Value includes: fixed value conversion, character substitution, head addition, middle addition, tail addition, head deletion, middle deletion, tail deletion, enumeration, and JS script conversion.
If no operation is performed on the key or value, we can describe as "action" to "none" to indicate no operation.
The rules for Key operations are:
1. adding brothers:
adding a sibling node is adding a Key-Value pair of Key and Value after the specified Key, for example, adding a sibling node part to "company code" is adding a Key-Value pair after "company code", as shown in the following example:
conversion rules we need to use the Key in the original JSON as the Key in the rule, value in the rule is an object, in which "_key_" represents the rule that operates on the original Key, and "_value_" represents the rule that operates on the original Value. The following are example rules:
the corresponding conversion rules are as follows:
2. deleting the node:
the delete node is the Key Value pair that deletes the Key and Value. For example, if there is a rule to delete the company code, the converted JSON becomes
{
"updateTime":"2019-01-01"
}
The corresponding conversion rules are as follows:
3. renaming:
renaming is to change the Key to a name. For example, the command code is changed into myCode, and the converted JSON is changed into
The corresponding conversion rules are as follows:
4. JS script conversion
Script conversion is designed mainly for processing complex business logic processing, after script writing, character strings of script conversion into base64 are put into conversion rules, because a plurality of characters in the script codes collide with characters of the JSON rules, and avoidance is needed, and the avoidance method is to convert the script codes into character strings of base 64. For example, the company code character string is inverted to be edoCynapmoc, and then in the complex cases of replacing the capitalized C with T, the converted JSON is:
in this case, we first need to write JS script logic code to implement:
in the above-described case, the following is implemented with JS script code:
then the JS code is encoded by base64, and the base64 character string of the above code encoded by base64 is as follows:
ZnVuY3Rpb24gaW5pdCAoZGF0YSkgeyAKCSAgICBzdHIxID0gZGF0YS5zcGxpdCgiIikucmV2ZXJzZSgpLmpvaW4oIiIpOwoJICAgIHN0cjIgPSBzdHIxLnJlcGxhY2VBbGwoJ0MnLCdUJyk7Cgk gICAgcmV0dXJuIHN0cjI7Cn0＝
then, if the rule is changed, the action of the rule is written as jsConverter, and the corresponding conversion rule is as follows:
the operation rules for value are:
1. fixed value
The fixed Value refers to a character string that is uniformly set to a specified Value regardless of the Value of the instant encountered. For example, setting the Value corresponding to the company code as alimama, the converted JSON is:
the corresponding conversion rules are as follows:
2. replacement of
The replacement is to replace a specific character in Value with other characters, for example, "-" in date is replaced with "/", and then the converted JSON is:
the corresponding conversion rules are as follows:
3. head addition
Header addition refers to adding a fixed string in front of the Value. For example, adding name_ to the header of Value, then the converted JSON is:
the corresponding conversion rules are as follows:
4. intermediate addition:
intermediate additions refer to additions anywhere in the Value string. For example, add_name_ in the middle of Value, then the converted JSON is:
the corresponding conversion rules are as follows:
5. tail addition:
the tail addition means addition at the end of the Value string. For example, add_name at the tail of Value, then the converted JSON is:
the corresponding conversion rules are as follows:
6. head deletion:
header deletion refers to the character preceding the delete Value string. For example, deleting 2 characters of the Value header, the converted JSON is:
the corresponding conversion rules are as follows:
7. intermediate deletion:
the middle deletion refers to a character in the middle of deleting the Value string. For example, delete 3 rd to 5 th characters in the middle of Value, then the converted JSON is:
the corresponding conversion rules are as follows:
8. tail deletion:
the tail deletion refers to deleting characters of a specified length at the tail of the Value character string. For example, deleting 3 characters at the tail of Value, the converted JSON is:
the corresponding conversion rules are as follows:
9. enumerating:
enumeration is a set of one-to-one mapped key-value pairs, where the corresponding value is found by looking up keys, the relationship of keys to values being irregular.
Such as: a corresponds to 101
B corresponds to 328
C corresponds to 591
When the Value of JSON appears as the Value in a, B, C, the Value is converted into the corresponding Value according to the key Value pair. Enumeration needs to ensure that the Value belongs to one of the enumerations and cannot exceed the range of enumeration values.
Such as key-value pair conversion rules with the following mapping relationships:
alibaba＝>alimama,
alimama＝>aligege
aligege＝>alijj
if the parameter JSON is:
the key to be found is "alimama", the corresponding value found is "align", and the parameter JSON after conversion is:
the corresponding conversion rules are as follows:
10. JS script conversion
The JS script conversion is a section of script written to cope with complex processing logic, which needs to be encoded with base64, because the symbols in the script are prevented from colliding with the symbols in JSON. For example, if the date is added for 30 days and "-" in the date is replaced by "/", the date cannot be processed by configuration, and then script is needed for processing.
The corresponding conversion rules are as follows:
next, the present application will be described in more detail.
The implementation principle of the application is as follows:
the following teaches the principles of the application:
the above description is that the process of establishing the conversion rule, after the rule is established, a unique name needs to be given to the rule, the rule name and the rule content need to be input into a black box tool, the black box tool establishes the hidden relation between the name and the content and stores the hidden relation, and the storage form can be a file or a database. After the rule name and the JSON data to be converted are stored, the external is required to be input when the external requests the conversion, the black box tool finds the corresponding rule content according to the rule name, and then analyzes the rule file to perform conversion. The conversion process is essentially to read the object contents indicated by "_key_and" _value_in the rule, and the processing according to the rule needs is described below.
1. If "action" is "none" then this represents that no processing is done on the original Key.
2. If "addbrother node" is included in "_key_", it represents that a sibling node needs to be added, and the sibling node exists in the form of an array, and a group of sibling nodes can be added. Then there are also two Key bands in the sibling object, namely "nodeName" and "nodeValue".
3. If the Key is "action" in "_key_" is "delNode", the node for deleting the original Key is represented.
4. If the name is "action" in "_key_" is "renameNode", the renamed node is represented, and then the new name is identified by taking the value corresponding to "nodeName" in the object, and the new name is converted according to the new name.
5. If the value is "action" in "_key_" "jsConverter", it represents that a section of JS script is to be executed, then the value of "convertScript" in the object is analyzed, the value is decoded by base64 to obtain an executable JS script, a JS script engine is called to execute the section of code, and the return value after script execution is used as a conversion result.
6. If the representation is conversion of a fixed value, the value corresponding to the value in the object is assigned.
7. If the representation is replacement conversion, the source string indicated by the src and dst in the object is replaced by the target string indicated by the dst value in the character string.
8. In the case of "convertType" in "_value_", the representation is that the head adds the specified character string, and the value of the character string to be added is obtained from "value".
9. If "addMiddle" represents a string designated in the middle of adding, the values of "startPos" and "value" are read from the object, the value of "startPos" represents the character from which to start adding, and the value of "value" represents the added content.
10. If "addmail" is "convertType" in "_value_", the value representing the string to be added is obtained from "value" by adding the specified string at the tail.
11. If the character is "convertType" in "_value_" is "delHead", the character representing the specified length of the deleting head is deleted, and the number of characters to be deleted is obtained from "length" in the object.
12. In the case of "convertType" in "_value_" which represents deleting the middle part of characters, the values of "startPos" and "length" need to be obtained from the object, and "startPos" represents the character from which to start deleting.
13. If the character is ' convertType ' in ' value_ ' delTail ', and the character with the specified length is deleted on the basis of the tail, the value of ' length ' is acquired from the object, and the length specified by ' length ' is deleted from the tail.
14. If the value is ' convertType ' in ' value_ ' enum ', the enumeration value is represented, a ' relation ' key value pair in the object needs to be acquired, then the key in the enumeration value is matched by the original value, and when the matching is finished, the original value in the JSON is replaced by the value in the key value pair.
15. If the value is ' convertType ' in ' value_ ' jsConverter ', the value of ' convertScript ' in the object is analyzed if a section of JS script is to be executed, the value is decoded by base64 to obtain an executable JS script, a JS script engine is called to execute the section of code, and a return value after script execution is used as a conversion result.
Those skilled in the art will appreciate that the application provides a system and its individual devices, modules, units, etc. that can be implemented entirely by logic programming of method steps, in addition to being implemented as pure computer readable program code, in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Therefore, the system and various devices, modules and units thereof provided by the application can be regarded as a hardware component, and the devices, modules and units for realizing various functions included in the system can also be regarded as structures in the hardware component; means, modules, and units for implementing the various functions may also be considered as either software modules for implementing the methods or structures within hardware components.
The foregoing describes specific embodiments of the present application. It is to be understood that the application is not limited to the particular embodiments described above, and that various changes or modifications may be made by those skilled in the art within the scope of the appended claims without affecting the spirit of the application. The embodiments of the application and the features of the embodiments may be combined with each other arbitrarily without conflict.
Claims (10)
1. A JSON conversion method, comprising:
step S1: establishing a set of conversion rules, wherein the rules are described by a JSON format;
step S2: implementing the conversion rule as a black box tool class;
step S3: writing rules into a black box tool, and storing conversion rules inside the black box tool;
step S4: the external of the black box tool inputs the instantiated JSON into the black box tool, and the internal of the black box tool is converted according to rules;
step S5: the black box tool returns the result of the conversion to the outside as a play-out.
2. The JSON conversion method of claim 1, wherein a Key in the JSON object is Key and a Value in the JSON object is Value;
the conversion rule includes: operating Key and Value;
wherein operating the Key comprises: adding brother nodes, deleting nodes, renaming and JS script conversion;
operating on Value includes: fixed value, substitution, head addition, middle addition, tail addition, head deletion, middle deletion, tail deletion, enumeration, and JS script conversion.
3. The JSON conversion method of claim 2, in which the operating on keys adds sibling nodes: adding a Key Value pair of Key and Value behind the designated Key;
deleting the node: deleting Key Value pairs of Key and Value;
renaming: renaming Key;
JS script conversion: and the method is responsible for processing complex business logic, and character strings for converting the script into base64 are put into conversion rules after the script is written.
4. The JSON conversion method of claim 2, in which the operating on Value, fixed Value: uniformly setting a designated character string no matter any Value is encountered;
replacement: replacing a specific character in the Value with other characters;
head addition: adding characters in front of the Value;
intermediate addition: adding characters at any position in the Value character string;
tail addition: adding characters at the tail of the Value character string;
head deletion: deleting the character in front of the Value character string;
intermediate deletion: deleting the character in the middle of the Value character string;
tail deletion: deleting the character with the specified length at the tail part of the Value character string;
enumerating: a group of key value pairs with one-to-one mapping relation, searching keys to find corresponding values, wherein the relation between the keys and the values is irregular;
JS script conversion: a section of JS script code is edited to process complex business logic, and the script needs to be encoded by base 64.
5. A JSON conversion system, comprising:
module M1: establishing a set of conversion rules, wherein the rules are described by a JSON format;
module M2: implementing the conversion rule as a black box tool class;
module M3: writing rules into a black box tool, and storing conversion rules inside the black box tool;
module M4: the external of the black box tool inputs the instantiated JSON into the black box tool, and the internal of the black box tool is converted according to rules;
module M5: the black box tool returns the result of the conversion to the outside as a play-out.
6. The JSON conversion system of claim 5, wherein a Key in the JSON object is a Key and a Value in the JSON object is a Value;
the conversion rule includes: operating Key and Value;
wherein operating the Key comprises: adding brother nodes, deleting nodes, renaming and JS script conversion;
operating on Value includes: fixed value, substitution, head addition, middle addition, tail addition, head deletion, middle deletion, tail deletion, enumeration, and JS script conversion.
7. The JSON translation system of claim 6, in which the operating on keys adds siblings: adding a Key Value pair of Key and Value behind the designated Key;
deleting the node: deleting Key Value pairs of Key and Value;
renaming: renaming Key;
JS script conversion: and the method is responsible for processing complex business logic, and character strings for converting the script into base64 are put into conversion rules after the script is written.
8. The JSON conversion system of claim 6, wherein the operating on Value, fixed Value: uniformly setting a designated character string no matter any Value is encountered;
replacement: replacing a specific character in the Value with other characters;
head addition: adding characters in front of the Value;
intermediate addition: adding characters at any position in the Value character string;
tail addition: adding characters at the tail of the Value character string;
head deletion: deleting the character in front of the Value character string;
intermediate deletion: deleting the character in the middle of the Value character string;
tail deletion: deleting the character with the specified length at the tail part of the Value character string;
enumerating: a group of key value pairs with one-to-one mapping relation, searching keys to find corresponding values, wherein the relation between the keys and the values is irregular;
JS script conversion: a section of JS script code is edited to process complex business logic, and the script needs to be encoded by base 64.
9. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the steps of the JSON conversion method of any one of claims 1 to 4.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the computer program when executed by the processor implements the steps of the JSON conversion method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310708631.8A CN116737157A (en) | 2023-06-14 | 2023-06-14 | JSON conversion method, system, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310708631.8A CN116737157A (en) | 2023-06-14 | 2023-06-14 | JSON conversion method, system, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116737157A true CN116737157A (en) | 2023-09-12 |
Family
ID=87909286
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310708631.8A Pending CN116737157A (en) | 2023-06-14 | 2023-06-14 | JSON conversion method, system, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116737157A (en) |
-
2023
- 2023-06-14 CN CN202310708631.8A patent/CN116737157A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| RU2419846C2 (en) | Encoding markup language data | |
| US7958133B2 (en) | Application conversion of source data | |
| US8650207B2 (en) | Inductive synthesis of table-based string transformations | |
| JPWO2009017131A1 (en) | Nondeterministic finite automaton generation system, method and program without ε transition | |
| KR20080100348A (en) | Xml payload specification for modeling edi schemas | |
| CN111460815A (en) | Rule processing method, apparatus, medium, and electronic device | |
| US20080127136A1 (en) | Software build system, software build method, and recording medium storing software build program | |
| KR102531507B1 (en) | Method, device, equipment and storage medium for outputting information | |
| CN110737431A (en) | Software development method, development platform, terminal device and storage medium | |
| US3636520A (en) | Computer system for improved data transmission | |
| US20180032548A1 (en) | Data Structure, Model for Populating a Data Structure and Method of Programming a Processing Device Utilising a Data Structure | |
| CN116737157A (en) | JSON conversion method, system, equipment and medium | |
| CN111143461A (en) | Mapping relation processing system and method and electronic equipment | |
| US20170139970A1 (en) | Method for updating a record in a database by a data- processing device | |
| KR100788135B1 (en) | Migration apparatus which convert sam/vsam files of mainframe system into sam/vsam files of open system and method for thereof | |
| JP6491438B2 (en) | Migration support device | |
| JP7247593B2 (en) | Generation device, software robot system, generation method and generation program | |
| CN113411271A (en) | Data access method, device, equipment and storage medium | |
| CN113157257B (en) | Rapid development device for banking system | |
| US11537625B1 (en) | Using structured data templates and invocation statements to dynamically define values for efficient data encoding | |
| Cimini | A declarative validator for GSOS languages | |
| US7617089B2 (en) | Method and apparatus for compiling two-level morphology rules | |
| US11467752B2 (en) | Data migration system and data migration method | |
| CN114089976B (en) | Method, apparatus, and medium for generating database operation statements | |
| Sarkar et al. | Python for Natural Language Processing |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |