CN101165682A - Document file processing method and system - Google Patents
Document file processing method and system Download PDFInfo
- Publication number
- CN101165682A CN101165682A CNA2006101139426A CN200610113942A CN101165682A CN 101165682 A CN101165682 A CN 101165682A CN A2006101139426 A CNA2006101139426 A CN A2006101139426A CN 200610113942 A CN200610113942 A CN 200610113942A CN 101165682 A CN101165682 A CN 101165682A
- Authority
- CN
- China
- Prior art keywords
- document files
- version
- target
- document
- type
- 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
- 238000003672 processing method Methods 0.000 title 1
- 238000012545 processing Methods 0.000 claims abstract description 9
- 238000000034 method Methods 0.000 claims description 53
- 238000001514 detection method Methods 0.000 claims description 28
- 238000006243 chemical reaction Methods 0.000 claims description 21
- 230000008859 change Effects 0.000 claims description 20
- 238000012546 transfer Methods 0.000 claims description 6
- 230000008569 process Effects 0.000 description 11
- 238000010586 diagram Methods 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 10
- 230000008901 benefit Effects 0.000 description 7
- 238000013461 design Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000007812 deficiency Effects 0.000 description 4
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 239000000047 product Substances 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000002950 deficient Effects 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 239000012467 final product Substances 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000009466 transformation Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 238000000151 deposition Methods 0.000 description 1
- 238000009795 derivation Methods 0.000 description 1
- 230000005611 electricity Effects 0.000 description 1
- 238000005194 fractionation Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000008521 reorganization Effects 0.000 description 1
- 239000011800 void material Substances 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention is used in processing the document files in one same kind of software version series; said document files have similar file structure; after detecting the version type of the inputted document files, and according to the detected version type, reading the inputted document files, getting the object of the document file and the object type; according to the object, the object type, and version type, generating the memory object structure of the target version.
Description
Technical field
The present invention relates to the method and system of the multiple document files of a kind of compatibility, the method and system of compatible multiple document files in particularly a kind of software design and the document files process field.
Background technology
In the basic technology in software design and complicated document processing field, desk-top publishing software is because its page object is very abundant, and the syntagmatic between the object is very complicated, and therefore any desktop software all has the very file structure of check.And in the process of software development, will inevitably the structure of software be continued to optimize, expand, its result will inevitably cause can't opening between the new and old edition file of preserving under the other side's release format.
The file compatibility problem all is a very important thing for any software, neither an easy thing.In order thoroughly to solve the file compatibility problem, decision is adopted the document storage core texture of extend markup language (XML, eXtensible Markup Language) as Office in next version such as Microsoft.And the InDesign product of Adobe company, its up-to-date version will be charged separately to the client in order to open old version file, this shows that file compatibility also needs to drop into bigger paying for the developer.And the file compatibility function is also extremely important for the customer.The product of many companies because highest version can't compatible lowest version file cause redaction slowly can't upgrade, even have influence on the vitality of product and company.
For file compatibility, generally adopt at present based on other direct compatible technique of object level and XML intermediate form compatible technique.
In adopting object-oriented programming, file structure is made up of a lot of objects.Simple, efficient based on other direct compatible technique method of object level, but there is fatal defective.Because compatibility method is based on object, when bigger change takes place file structure, just be difficult to realize the compatibility of high lowest version in the time of such as the merging that object occurs, fractionation, deletion, reorganization.
XML intermediate form compatible technique be with XML as intermediate form, transfer the file of lowest version to the XML file, be the file layout of highest version again with the XML file conversion.This technology can solve the file compatibility problem of any complexity, because XML itself can infinitely expand, but its defective is: need the accurate XML Schema of definition; The threshold of XML intermediate form compatible technique itself is than higher, and the general work amount is all very big; On its flow process, owing to exist twice even the conversion of file layout repeatedly, its efficient obviously is very low.
Very popular quick software programming and reconfiguration technique in the software design field at present.Emphasize one-piece construction, code are continued to optimize improvement, thus maintainability, extensibility and the vitality of lifting software.Reconstruct work brings very big problem to file compatibility.Because software is reconstructed, will inevitably causes the change of file structure, thereby cause version after the reconstruct can't open the file of a version.
Again XML compatible technique and the deficiency that the direct compatible technique of object and they exist are described below.
One), XML compatible technique.
The XML compatible technique adopts XML as middle compatible format, need at first define the syntactic structure (Schema) of XML, and old formatted file is converted to the XML formatted file, is the format file with the XML file conversion again.If old formatted file and format file difference are very big, might define the XML file of old form and format respectively, and be new XML file old XML file conversion.Fig. 1 is for adopting the schematic flow sheet of single XML format compatible, and Fig. 2 is for adopting the schematic flow sheet of two XML format compatibles, and the file conversion flow process of XML compatible technique as shown in the figure.
The advantage of XML compatible technique has:
Extendability is strong, adaptability is strong, for the great file conversion of implementation structure difference, have very big advantage.
The deficiency of XML compatible technique is:
Owing to there is multiple conversions, efficient is low; The structure (Schema) that needs definition XML; Realize a plurality of transfer processes, the threshold height, workload is big.
Two), the direct compatible technique of object.
In the Object oriented programming method, document is made up of different objects, and object belongs to class.May there be an object instance in a class in document, also may have a plurality of object instances.File structure is a tree of being made up of object, and wherein Shu root node is exactly the root node of document.
Fig. 3 is a document object tree structure synoptic diagram, the tree of document as shown in the figure, wherein:
1, the square frame on the right is represented class, represents with capitalization; The circle code object on the left side is represented with lowercase;
2, the solid line representative has (Own) relation, dotted line code adduction relationship (Reference) in the tree derivation;
3, there is asterisk to represent to have a plurality of these objects;
4, an object can only be had by an object (Parent), can be by arbitrarily individual object reference.
The top of tree is unique root object, may comprise some general data (non-object data) in each object, also may comprise and have object (Own), also may comprise reference object (Reference).Object has this relation of (Own) subobject just, has formed the tree of document.In the tree of Fig. 3, the general data in the object that do not draw is because the change of these general data is than being easier to realize directly compatibility.
In order to preserve document, this tree need be write the document from internal memory, again this tree is read in the internal memory from disk file in the time of opening document.Here need to solve two problems, the one, the adduction relationship of reconstructed object, the 2nd, that determines object deposits (getting) in proper order.Adopted the mode of distributing unique ID for each object to come adduction relationship between reconstructed object in the prior art; That has adopted that the principle of depth-first determines object deposits (getting) in proper order, that is to say when depositing (getting) document, deposit (getting) object itself earlier, the subobject of this object is write in the chained list again, first object of getting again in the chained list is deposited (getting), go down so repeatedly, till all objects in chained list have been preserved.
As can be seen, this access mode is to be unit with the object fully, if change has taken place the general data of single object, realize that the document compatibility is very easy.Can be expressed as follows:
void?CMyObject::OnExchangeData(bool?bLoad，Iv_Stream*pStream)
//pStream is for preserving the stream of data, and bLoad is the true respresentation read data, otherwise is write data
{
Int iVersion=2; // object current version is 2
IVersion=ExchangeInt (iVersion, bLoad, pStream) // read (writing) object version number;
switch(iVersion)
{
case?1：
M_iData1=ExchangeInt (m_iData1, bLoad, pStream); // read the data in (writing) version 1;
break；
case?2：
M_iData1=ExchangeInt (m_iData1, bLoad, pStream); // read the data in (writing) version 1;
M_iData2=ExchangeInt (m_iData1, bLoad, pStream); // read the data in (writing) version 2;
break；
}
}
But in the process of exploitation, change to file structure is frequent, if in an object, added new subobject, perhaps deleted subobject, perhaps merging has taken place in subobject, perhaps change has taken place in adduction relationship, perhaps produces other more complicated structural adjustments, and this method based on the direct compatible technique of object is just powerless.Because in reading the process of file, in the object rank, can only be " only seeing trees; lose forest ", even the upper and lower relation for an object is understood very much, but owing to when reading an object, can not guarantee that the object of its upper and lower relation has read out from disk, so can not make too many change to this object, because this object itself or " incomplete ".
Come the deficiency of the direct compatible technique scheme existence of description object below with some the simplest examples.
Situation synoptic diagram when Fig. 4 takes place to merge for document object, as shown in the figure, subobject in object C merges, when the information of object g and h is merged into object i, adopt the direct object compatibility mode almost to be difficult to realize, because can not in process of reading, object g and h be merged into object i in implementing, and set up the have relation of c to i.
Situation synoptic diagram when Fig. 5 for document object division takes place, as shown in the figure, h divides when object, when object h is split into i and b, also exists this moment object e to the quoting of i, adopt object directly the method for compatibility also be difficult to realize.
The irrealizable example of directly compatible institute is very many, when almost the object structure of document changes, all can not realize compatibility, does not enumerate one by one at this.
The direct compatible technique advantage of object is to realize simply, efficient is high; But its deficiency is when file structure changes, and is difficult to realize compatible.
Summary of the invention
The invention provides a kind of disposal route and system of document files, in order to solve exist in the prior art when file structure changes, be difficult to the problem of realization document files compatibility.Further solved the problem how high efficiency processing document files is changed.
The technical scheme of document files disposal route of the present invention, the document files that is used for same kind software portfolio version is handled, and described document files has common file structure, comprises the steps:
A, detection input document files release type read the input document files according to described detected release type and form the memory object structure;
B, the object that obtains described input document files and object type;
C, according to described object and object type, according to target release type generates target version memory object structure.
Preferably, further comprise the steps:
Whether document files is read in detection is the document files that same kind software generates, and is then to change steps A over to.
Preferably, described step B is to travel through and obtain according to distributing in the input document files unique identification of each object.
Preferably, described step C comprises the steps:
Between described detection version and target version, press version height successively after the conversion, according to target release type generates target target version memory object structure.
Preferably, described steps A, B, C carry out in internal memory.
The present invention also provides a kind of disposal system of document files, and the document files that is used for same kind software portfolio version is handled, and described document files has common file structure, comprising:
First detection module is used for detecting input document files release type;
Read module links to each other with first detection module, is used for reading the input document files according to described detected release type and forms the memory object structure;
Acquisition module links to each other with described read module, converter, is used to obtain the object and the object type of described input document files;
Converter is used for according to described object and object type, and according to target release type generates target version memory object structure.
Preferably, further comprise:
Second detection module links to each other with described first detection module, is used to detect whether read document files be the document files that same kind software generates, and is then to transfer to described first detection module to handle.
Preferably, described acquisition module comprises:
Object Manager is used for according to the unique identification of distributing to each object of input document described input document files being traveled through;
Acquiring unit is used for obtaining object and object type according to described traversal unit traversing result.
Preferably, described converter comprises the converting unit of at least one corresponding continuous two version, is used between described detection version and target version, press the version height successively after the conversion, the target version of release type generation according to target memory object structure.
Preferably, described acquiring unit obtains in internal memory, and/or converter is changed in internal memory.
Beneficial effect of the present invention is as follows:
The present invention is based on " structurally having very big similarity between the height version file of a software " this prerequisite and designs.Therefore in invention, can realize compatibility between each version file of same software by using converter continuous more than simultaneously.
Because in the different editions of same software, be modified to as if seldom, therefore therefore conversion also seldom uses the present invention can obtain high efficient.Simultaneously, because for a converter, its possibility just only need a class object is done operation,, therefore implement also very succinct, easy such as the subobject of certain object of deletion.Because the required function of finishing of converter is simplified under same software greatly, when therefore implementing, the converter that has only needs 20 line codes just can finish the function of conversion.
Simultaneously since in same software based on the principle that has very big similarity, conversion from high to low and conversion from low to high are as broad as long in essence, the status of high lowest version is reciprocity.Therefore the present invention also can realize high to low compatibility.
In design studies of the present invention, adopted software for composing of new generation " wound of soaring skill " to test as beneficial effect as the upright exploitation of the leader of journalism software for composing, this software is a powerful software for composing towards journalism and commercial designs field.Because in the performance history of " wound of soaring skill ", need be from the user test stage, every two weeks is that typical customers is submitted a beta release to, has therefore produced because of the change to file structure too frequently on stream, and causes being difficult to realizing problem to the old and new's version file compatibility.After having adopted document files compatible technique of the present invention, not only thoroughly solved this problem, simultaneously the principle that is adopted because of the present invention's design makes and seems this transfer process efficient is very high, to such an extent as to can ignore the consumption of switching time.
Simultaneously because of the present invention is based on this principle of similarity that has height between the different editions of same software, therefore, the present invention is of universal significance for the document compatibling problem that solves between any software with similarity structure, has good versatility.
Description of drawings
Fig. 1 is the schematic flow sheet that adopts single XML format compatible described in the background technology;
Another adopts the schematic flow sheet of single XML format compatible to Fig. 2 in the background technology;
Fig. 3 is the synoptic diagram of document object tree structure described in the background technology;
Situation synoptic diagram when Fig. 4 is the generation of document object described in background technology merging;
Situation synoptic diagram when Fig. 5 is the generation of document object described in background technology division
Fig. 6 is the disposal route implementing procedure synoptic diagram of document files described in the embodiment;
Fig. 7 is the structural representation of document files disposal system described in the embodiment;
The schematic flow sheet that Fig. 8 shows for opening document file described in the embodiment;
Fig. 9 is for obtaining object described in the embodiment and object type is carried out the transformation flow synoptic diagram.
Embodiment
Below in conjunction with accompanying drawing concrete enforcement of the present invention is described.
Design of the present invention is based between the same type software different editions, on file structure, have a lot of common traits thereby have very big similarity, and then fully absorb the direct software engineering advantages of simplicity and high efficiency of object advantage, proposed file is carried out compatible technical scheme of repairing, thereby when having solved file structure and having changed, the problem that the direct compatible technique of object cann't be solved.Principle to the present invention's design is elaborated below.
The form of supposing old document is a version 1, and the form of new document is a version 2, open the file of legacy version in new edition software, and a feasible method is to do a converter (Convertr) so.Directly open old document with old read method, the data in the old document are read in the internal memory.With converter internal storage structure is operated then, because the information in the ancient deed is read in the internal memory fully at this moment, there is complete, a legal file structure in the internal memory, thereby this moment can carry out arbitrarily reasonably internal memory operation (in fact being exactly the method function that calls class), the file structure in the internal memory is operating as the compatibility of the file that version 2 promptly realized with converter from version 1.After the document internal storage structure was converted to version 2, document was just calculated really and is opened.Next step just can carry out various the operation to the document after the conversion, for example demonstrates the page object in the document.
Wherein, the notion of internal memory is meant an interim storage space in the present invention, and its memory capacity is limited, can change wherein canned data according to system call, also can lose because of transferring electricity, just reads an interim storage space in the document process.Obviously implementing the present invention is not limited only among internal memory.
Here, also be important the opportunity of calling for converter, and it should be after the legacy version File Open, and document carries out calling before next step operation.
Because converter does not produce any influence to the document compatibility method of front, and it can be operated arbitrarily to internal storage structure.Therefore it both can independently finish file compatibility work, one that also can be used as the direct compatible technique of object is replenished, if the direct compatibility of object can solve whole issue, then can not need converter, if the direct compatibility of object can solve subproblem, then can allow converter solve remaining problem, also can allow converter solve all compatibling problems.
Can see in the technical scheme of the present invention, break through the restriction of direct conversion to time and space, can bring into play arbitrarily by converter, Zhuan Huan mode has been utilized the method function that object itself has substantially simultaneously, and these methods are that enrich, reliable.
Based on above-mentioned technical conceive, the invention provides a kind of disposal route of document files, be used for the document files processing that same kind software generates, described document files has common file structure, below in conjunction with accompanying drawing concrete enforcement of the present invention is described.
Fig. 6 is the disposal route implementing procedure synoptic diagram of document files, as shown in the figure, comprises the steps:
Whether document is read in step 601, detection is the document files with same kind software generation of similar documents structure;
This step is to travel through and obtain according to distributing in the input document unique identification of each object.
Can then all objects in the document be put into unified management in the Object Manager (RuntimeEnv) by setting up the manager of document object during concrete enforcement, each object distributes a unique ID.Set up Object Manager, Object Manager can provide the ability that all objects are traveled through.
Then, object is enumerated, obviously Object Manager provides the ability that all document objects are enumerated;
Enumeration object is operated according to type; We need the type (affiliated class) according to object make amendment in the process of object enumeration, directly ignore for the object type that does not need to revise.
When detecting when having many versions between version and the target version, press the version height successively after the conversion, the target version of release type generation according to target memory object structure.
Conversion hereto, can use converter to finish, converter is relevant with the version of document, such as converter called after CConvertorV1toV2 from version 1 to version 2, converter called after CConvertorV2toV3 from the version 2 to the version 3, can use a plurality of continuous converters simultaneously, such as using converter CConvertorV1toV2 earlier, re-use CConvertorV2toV3......, so just realized compatibility to every other version file, and each released version is just need newly add a nearest version to get final product to the converter of current version, implements very simple.
In view of the characteristic of above-mentioned internal memory, the document files object all can be opened when in internal memory, carrying out in preferred the enforcement, thereby be changed more conveniently, simultaneously because what read is whole objects, thereby can access object relationship more completely in internal memory.
Based on same inventive concept, the present invention also provides a kind of disposal system of document files, be used for the document files processing that same kind software generates, document files has common file structure, describes below in conjunction with the concrete enforcement of accompanying drawing to native system.
Fig. 7 is the structural representation of document files disposal system, as shown in the figure, comprises second detection module 702, first detection module 701, read module 703, acquisition module 704, converter 705 in the system, and it is continuous successively that each module position is closed.Wherein:
Whether second detection module 702 detects and reads document files is the document files that same kind software generates, and is then to transfer to first detection module 701 to handle; First detection module 701 detects input document files release type then; The read module 703 that links to each other with first detection module 701 reads the input document files according to detected release type and forms the memory object structure; The acquisition module 704 that links to each other with read module 704, converter 705 obtains the object and the object type of input document files; Last converter 705 is according to object and object type, and according to target release type generates target version memory object structure.
Wherein acquisition module can comprise:
Object Manager is used for according to the unique identification of distributing to each object of input document described input document files being traveled through;
Acquiring unit is used for obtaining object and object type according to described traversal unit traversing result.
At least comprise at converter being used for the converting unit of continuous two versions of correspondence between described detection version and target version that press the version height successively after the conversion, according to target release type generates target version memory object structure.
Converter is relevant with the version of document, such as converter called after CConvertorV1toV2 from version 1 to version 2, converter called after CConvertorV2toV3 from the version 2 to the version 3, can use a plurality of continuous converters simultaneously, such as using converter CConvertorV1toV2 earlier, re-use CConvertorV2toV3......, so just realized compatibility, and each released version is just need newly add a nearest version to get final product to the converter of current version to every other version file.
In view of the characteristic of above-mentioned internal memory, thus the document files object all can be opened when in internal memory, carrying out, thereby change more conveniently, simultaneously because what read is whole objects, thereby can access object relationship more completely in internal memory.Converter is changed in internal memory during therefore preferred enforcement, and acquiring unit obtains in internal memory.
Be to utilize the present invention to overcome in the background technology below, for the direct compatible technique of object can not realize that the object document files can not merge, embodiment under the division situation.
Situation about describing for Fig. 4 can solve with following step:
1), open the legacy version file, has document internal storage structure this moment as left figure among Fig. 4 with the code of legacy version;
2), all objects in the traversal document;
3), be the object of C for type, do following processing:
(1) creates (new) object i;
(2) from object g, h, get data and make up object i;
(3) discharge object g, h.
Situation about describing for Fig. 5 can solve with following step:
1), open the legacy version file, has document internal storage structure this moment as left figure among Fig. 5 with the code of legacy version;
2), all objects in the traversal document;
3), be the object of F for type, do following processing:
(1) creates (new) object i and b;
(2) from object h, get data and make up object i and b;
(3) obtain the parent object e of f;
(4) set up the adduction relationship of object e to i;
(5) discharge object h.
For further describing the specific embodiment of the present invention, opening document file and transformer work flow among the present invention are described below in conjunction with accompanying drawing.
The schematic flow sheet that Fig. 8 shows for the opening document file, as shown in the figure, the step of opening is:
Fig. 9 carries out the transformation flow synoptic diagram for obtaining object and object type, and as shown in the figure, the workflow of converter is:
In sum, the present invention has fully absorbed the direct software engineering advantages of simplicity and high efficiency of object advantage, and has proposed a kind of file compatibility method for repairing and mending, solves when file structure changes the problem that the direct compatible technique of object cann't be solved.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (10)
1. the disposal route of a document files is used for the document files processing of same kind software portfolio version, and described document files has common file structure, it is characterized in that, comprises the steps:
A, detection input document files release type read the input document files according to described detected release type and form the memory object structure;
B, the object that obtains described input document files and object type;
C, according to described object and object type, according to target release type generates target version memory object structure.
2. the method for claim 1 is characterized in that, further comprises the steps:
Whether document files is read in detection is the document files that same kind software generates, and is then to change steps A over to.
3. the method for claim 1 is characterized in that, described step B is to travel through and obtain according to distributing in the input document files unique identification of each object.
4. the method for claim 1 is characterized in that, described step C comprises the steps:
Between described detection version and target version, press version height successively after the conversion, according to target release type generates target target version memory object structure.
5. the method for claim 1 is characterized in that, described steps A, B, C carry out in internal memory.
6. the disposal system of a document files is used for the document files processing of same kind software portfolio version, and described document files has common file structure, it is characterized in that, comprising:
First detection module is used for detecting input document files release type;
Read module links to each other with first detection module, is used for reading the input document files according to described detected release type and forms the memory object structure;
Acquisition module links to each other with described read module, converter, is used to obtain the object and the object type of described input document files;
Converter is used for according to described object and object type, and according to target release type generates target version memory object structure.
7. system as claimed in claim 6 is characterized in that, further comprises:
Second detection module links to each other with described first detection module, is used to detect whether read document files be the document files that same kind software generates, and is then to transfer to described first detection module to handle.
8. system as claimed in claim 6 is characterized in that, described acquisition module comprises:
Object Manager is used for according to the unique identification of distributing to each object of input document described input document files being traveled through;
Acquiring unit is used for obtaining object and object type according to described traversal unit traversing result.
9. system as claimed in claim 6, it is characterized in that, described converter comprises the converting unit of at least one corresponding continuous two version, be used between described detection version and target version, press version height successively after the conversion, according to target release type generates target target version memory object structure.
10. system as claimed in claim 6 is characterized in that described acquiring unit obtains, and/or converter is changed in internal memory in internal memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006101139426A CN101165682A (en) | 2006-10-20 | 2006-10-20 | Document file processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006101139426A CN101165682A (en) | 2006-10-20 | 2006-10-20 | Document file processing method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101165682A true CN101165682A (en) | 2008-04-23 |
Family
ID=39334381
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2006101139426A Pending CN101165682A (en) | 2006-10-20 | 2006-10-20 | Document file processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101165682A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104573127A (en) * | 2015-02-10 | 2015-04-29 | 北京嘀嘀无限科技发展有限公司 | Method and system for evaluating data difference |
| CN106227713A (en) * | 2016-08-31 | 2016-12-14 | 广州视睿电子科技有限公司 | The processing method and processing device of document |
| CN106874004A (en) * | 2017-02-21 | 2017-06-20 | 广州视源电子科技股份有限公司 | The method and client and server of lowest version software compatibility highest version file |
| CN107122341A (en) * | 2012-01-13 | 2017-09-01 | 微软技术许可有限责任公司 | Method and system for the calculating of the attribute of object/shape across application version |
| CN107122339A (en) * | 2017-04-18 | 2017-09-01 | 广州视源电子科技股份有限公司 | A kind of electronic document and its making, parsing method and system |
| CN107787487A (en) * | 2015-06-22 | 2018-03-09 | 微软技术许可有限责任公司 | By document deconstruction is component block for reusing in being applied in productivity |
| CN112308101A (en) * | 2019-07-30 | 2021-02-02 | 杭州海康威视数字技术股份有限公司 | Method and device for object recognition |
-
2006
- 2006-10-20 CN CNA2006101139426A patent/CN101165682A/en active Pending
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107122341A (en) * | 2012-01-13 | 2017-09-01 | 微软技术许可有限责任公司 | Method and system for the calculating of the attribute of object/shape across application version |
| CN104573127A (en) * | 2015-02-10 | 2015-04-29 | 北京嘀嘀无限科技发展有限公司 | Method and system for evaluating data difference |
| CN104573127B (en) * | 2015-02-10 | 2019-05-14 | 北京嘀嘀无限科技发展有限公司 | Assess the method and system of data variance |
| CN107787487A (en) * | 2015-06-22 | 2018-03-09 | 微软技术许可有限责任公司 | By document deconstruction is component block for reusing in being applied in productivity |
| CN106227713A (en) * | 2016-08-31 | 2016-12-14 | 广州视睿电子科技有限公司 | The processing method and processing device of document |
| WO2018040439A1 (en) * | 2016-08-31 | 2018-03-08 | 广州视睿电子科技有限公司 | Document processing method and apparatus |
| CN106874004A (en) * | 2017-02-21 | 2017-06-20 | 广州视源电子科技股份有限公司 | The method and client and server of lowest version software compatibility highest version file |
| CN106874004B (en) * | 2017-02-21 | 2020-08-21 | 广州视源电子科技股份有限公司 | Method for enabling low-version software to be compatible with high-version file, client and server |
| CN107122339A (en) * | 2017-04-18 | 2017-09-01 | 广州视源电子科技股份有限公司 | A kind of electronic document and its making, parsing method and system |
| CN107122339B (en) * | 2017-04-18 | 2020-12-22 | 广州视源电子科技股份有限公司 | Electronic document and making and analyzing method and system thereof |
| CN112308101A (en) * | 2019-07-30 | 2021-02-02 | 杭州海康威视数字技术股份有限公司 | Method and device for object recognition |
| CN112308101B (en) * | 2019-07-30 | 2023-08-22 | 杭州海康威视数字技术股份有限公司 | Method and device for identifying object |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Borkar et al. | Big data platforms: what's next? | |
| CN101165682A (en) | Document file processing method and system | |
| CN105205105B (en) | A kind of ETL process system and processing method based on storm | |
| Arlia et al. | Experiments in parallel clustering with DBSCAN | |
| CN103559323B (en) | Database implementation method | |
| CN101887365B (en) | Method and system for constructing executable code for component-based applications | |
| Luján-Mora et al. | A comprehensive method for data warehouse design | |
| CN104915450A (en) | HBase-based big data storage and retrieval method and system | |
| US20070179962A1 (en) | Schema mapping specification framework | |
| CN102043657A (en) | File serialization method of model library of physical modeling language Modelica | |
| CN101201816B (en) | Adapter and method for outputting data in data stream to XML document | |
| CN103365852A (en) | Concurrency control method and system for document library systems | |
| Del Fabro et al. | Applying Generic Model Management to Data Mapping. | |
| CN103309904A (en) | Method and device for generating data warehouse ETL (Extraction, Transformation and Loading) codes | |
| CN102819585A (en) | Method for controlling document of extensive makeup language (XML) database | |
| CN103425740A (en) | IOT (Internet Of Things) faced material information retrieval method based on semantic clustering | |
| CN103077192A (en) | Data processing method and system thereof | |
| CN116775605A (en) | Industrial data management and sharing platform based on artificial intelligence | |
| CN101350007B (en) | Method and apparatus for parallel XSL transformation with low contention and load balancing | |
| Shaw | Software architectures for shared information systems | |
| CN102722368A (en) | Plug-in software designing method based on document tree and message pump | |
| CN101894317B (en) | System and method for driving business logic through data changes | |
| KR20140076010A (en) | A system for simultaneous and parallel processing of many twig pattern queries for massive XML data and method thereof | |
| CN105550176A (en) | Basic mapping method for relational database and XML | |
| CN101582027B (en) | Computation module based on form field fusion |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20080423 |