CN1871598A - Systems and methods for extensions and inheritance for units of information manageable by a hardware/software interface system - Google Patents

Abstract

By modeling real-world application objects with complex structures, behaviors, and operations described by a schema which is enforced by the hardware/software interface system, various embodiments of the present invention provide rich sub-typing functionality by extending Items (and Item types) using 'Extensions' which provide additional data structures (Properties, Relationships, etc.) to already existing Items type structures. Extensions are strongly typed instances that cannot exist independently and must be attached to an Item or a Nested Element. Extensions are also intended to address 'multi-typing' issues by enabling the overlap of type instances (e.g., a Document may be a 'legal document' as well a 'secure document').

Description

Being used for can be by the expansion of the information unit of hardware/software interface system management and the system and method for succession

The cross reference of relevant application

The present invention requires the priority of following patent application: the U.S. Patent application of submitting on October 24th, 2003 number 10/693,574 (application attorney docket MSFT-2847), title are " SYSTEMS AND METHODS FOR EXTENSIONS AND INHEITANCE FOR UNITS OF INFORMATION MANAGEABLE BY A HARDWARE/SOFTWARE INTERFACE SYSTEM (be used for can by the expansion of the information unit of hardware/software interface system management and the system and method for succession) "; The U.S. Patent application of submitting on August 21st, 2003 number 10/646,580 (application attorney docket MSFT-2735), title are " SYSTEMS AND METHODS FOR DATA MODELING IN AN ITEM-BASED STORAGE PLATFORM (system and method that is used for data modeling in project-based storage platform) "; And the international application no PCT/US 03/26144 (application attorney docket MSFT-2779) of submission on August 21st, 2003, title is " SYSTEM AND METHODS FOR DATA MODELING IN AN ITEM-BASED STORAGE PLATFORM (system and method that is used for data modeling in project-based storage platform) "; Content with them is included in this by reference.

The application is relevant with the invention that discloses in the application of below general appointment on theme, content integral body with them comprises in the present invention (and for convenient partly be summarized in this) by reference: the U.S. Patent application of submitting on August 21st, 2003 number 10/647,058 (application attorney docket MSFT-1748), title is " SYSTEMS AND METHODS FOR REPRESENTING UNITS OF INFORMATION MANAGEABLE BY A HARDWARE/SOFTWARE INTERFACE SYSTEM BUT INDEPENDENT OF PHYSICAL REPRESENTATION (be used for expression can be by the information unit of hardware/software interface system management but be independent of the system and method that physics represents) "; The U.S. Patent application of submitting on August 21st, 2003 number 10/646,941 (application attorney docket MSFT-1749), title are " SYSTEMS AND METHODS FOR SEPARATING UNITS OF INFORMATION MANAGEABLE BY A HARDWARE/SOFTWARE INTERFACE SYSTEM FROM THEIR PHYSICAL ORGANIZATION (being used for separating according to their physical organization can be by the system and method for the information unit of hardware/software interface system management) "; The U.S. Patent application of submitting on August 21st, 2003 number 10/646,940 (application attorney docket MSFT-1750), title are " SYSTEMS AND METHODS FOR THE IMPLEMENTATION OF A BASE SCHEMA FOR ORGANIZING FOR UNITS OF INFORMATION MANAGEABLE BY A HARDWARE/SOFTWARE INTERFACE SYSTEM (be used for to realize tissue can by the system and method for the basic mode formula of the information unit of hardware/software interface system management) "; The U.S. Patent application of submitting on August 21st, 2003 number 10/646,632 (application attorney docket MSFT-1751), title is " SYSTEMS AND METHODS FOR THE IMPLEMATION OF A CORE SCHEMA FOR PROVIDING A TOP-LEVEL STRUCTURE FOR ORGANIZING UNITS OF INFORMATION MANAGEABLE BY A HARDWARE/SOFTWARE INTERFACE SYSTEM (be used for being embodied as tissue and can provide the system and method for the core schema of top level structure by the hardware/information unit of software interface system management) "; The U.S. Patent application of submitting on August 21st, 2003 number 10/646,645 (application attorney docket MSFT-1752), title are " SYSTEMS AND METHODS FOR REPRESENTING RELATIONSHIPS BETWEEN UNITS OF INFORMATION MANAGEABLE BY A HARDWARE/SOFTWARE INTERFACE SYSTEM (be used for expression can by the system and method for the information unit Relations Among of hardware/software interface system management) "; The U.S. Patent application of submitting on August 21st, 2003 number 10/646,575 (application attorney docket MSFT-2733), title is " SYSTEMS AND METHODS FOR INTERFACING APPLICATION PROGRAMS WITH AN ITEM-BASED STORAGE PLATFORM (being used for making the system and method for the project-based storage platform of application programming interfaces) "; The U.S. Patent application of submitting on August 21st, 2003 number 10/646,646 (application attorney docket MSFT-2734), title is " STORAGE PLATFORM FOR ORGANIZING; SEARCHING, AND SHARING DATA (storage platform that is used for tissue, search and shared data) "; The U.S. Patent application of submitting on August 21st, 2003 number 10/692,779 (application attorney docket MSFT-2829), title are " SYSTEMS AND METHODS FOR THE IMPLEMENTATION OF A DIGITAL IMAGES SCHEMA FOR ORGANIZING UNITS OF INFORMATION MANAGEABLE BY A HARDWARE/SOFTWARE INTERFACE SYSTEM (be used for to realize tissue can by the system and method for the digital picture pattern of the information unit of hardware/software interface system management) "; The U.S. Patent application of submitting on August 21st, 2003 number 10/692,515 (application attorney docket MSFT-2844), title is " SYSTEMS AND METHODS FOR PROVIDING SYNCHRONIZATION SERVICES FOR UNITS OF INFORMATION MANAGEABLE BY A HARDWARE/SOFTWARE INTERFACE SYSTEM (being used to provide the system and method for synchronous service by the information unit of hardware/software interface system management) "; The U.S. Patent application of submitting on the same day with the application number 10/692,508 (application attorney docket MSFT-2845), title is " SYSTEMS AND METHODS FOR PROVIDING RELATIONAL AND HIERARCHICAL SYNCHRONIZATION SERVICES FOR UNITS OF INFORMATION MANAGEABLE BY A HARDWARE/SOFTWARE INTERFACE SYSTEM (being used to the system and method for the synchronous service that related and layering can be provided by the information unit of hardware/software interface system management) "; And on October 24th, 2003 U.S. Patent application submitted to number 10/693,362 (application attorney docket MSFT-2846), title are " SYSTEMS AND METHODS FOR THE IMPLEMENTATION OF A SYNCHRONIZATION SCHEMAS FOR UNITS OF INFORMATION MANAGEABLE BY A HARDWARE/SOFTWARE INTERFACE SYSTEM (be used for to realize can by the system and method for the synchronous mode of the information unit of hardware/software interface system management) ".

Technical field

The present invention relates generally to the field of information storage and retrieval, and more particularly, relates to the storage platform of the activity of tissue, search and shared different types of data in computerized system. Various embodiment of the present invention is for using expansion and the inheritance method that is used for management data by hardware/software interface system.

Background

In last decade, the capacity of single disc is annual to increase about percent 70 (70%). The calculated to a nicety surprising growth of CPU (CPU) ability in several years in the past of mole (Moore) rule. Wired be connected with wireless technology quantitatively huge connection and bandwidth is provided. Suppose that current trend continues, general laptop computer will have the storage of about terabyte (TB) and comprise millions of files within the several years, and the driver of 500,000,000,000 bytes (500GB) becomes common.

The consumer uses their computer to be mainly used in communication and organizes personal information, no matter they are data or the media as digital music or photo of traditional personal information manager (PIM) style. The amount of digital content and the ability of storing original byte increase in large quantities; Yet the consumer can be used for organizing and the method for unifying these data does not but catch up with paces. The knowledge worker spends that the plenty of time manages and shared information, and some studies estimation, and the knowledge worker spends the time of 15-25% in the activity relevant with invalid information. Research is estimated in addition, and typical knowledge worker spends 2.5 hours search information every day approximately.

The time that the investment of developer and information technology (IT) department is a large amount of and money make up themselves the abstract data of common memory that are used for and store, to present such as item orders such as people, place, Time And Events. This not only causes the work of repetition, also forms the isolated island of public data, does not have the mechanism of common search or shared those data. How many address books only consider has at the computer that moves Microsoft Windows operating system now. Many application programs as email client and Personal Finance program keep address book separately, and only have seldom shared between the address book application that each such program is safeguarded respectively. Thereby, financial procedure (such as Microsoft Money) not with the address that is maintained in address in the e-mail contacts file (such as the contacts folder among the Microsoft Outlook) and shares the payer. Really, many users have a plurality of equipment, should be logically between these equipment and between being included in such as the various additive sources of the mobile portable phone number of the commercial service such as MSN and AOL synchronous their personal data; Yet the cooperation major part of shared document reaches by document is attached to email message-and this is manual and poor efficiency.

A reason that lacks cooperation is to organize the conventional method of the information in the computer system to concentrate on the system's (" file system ") that uses based on file-file-catalogue, comes abstract in the catalogue hierarchy of a plurality of file organizations to file based on the physical organization of the storage medium that is used for storage file. But be considered to be in operating system grade is managed storage data units with file, file and catalogue pioneer in nineteen sixty for the Multics operating system of developing. Particularly, Multics uses symbolic address (thereby concept of introducing file path) in the hierarchy of file, and the physical address of its File is opaque to user (application program and end user). This file system gives no thought to the file format of any Single document, and the pass that reaches hereof between the file ties up to (that is, different from the position of hierarchy File) that are considered on the operating system grade have nothing to do. Because the appearance of Multics, storable data are organized into file, file and catalogue on operating system grade. These files generally comprise the document layered structure itself (" catalogue ") that is placed in the specific file of being safeguarded by file system. This catalogue and then maintenance are corresponding to the tabulation of the project of all other files in this catalogue and the node location of those files in hierarchy (referring to file here). This is state nearly 40 years in this area.

Yet, although the reasonable representation of the information in the physics storage system that resides in computer is provided, but file system is the abstract of physics storage system, thereby what (having context, feature and and the unit of the relation of other unit) utilization of file need to process and operating system provides indirect (explanation) between what (file, file and catalogue) layer the user. As a result, user (application program and/or end user) have to force information unit is put into file system structure, though do like this be poor efficiency, inconsistent or undesirable. In addition, existing file system is known little about it about the structure of the data of storing in each file, and therefore, most of information keep sealing hereof, can only be write the application access (with understanding) of those data. Therefore, lack the pattern description of information and the mechanism of management information, cause forming the vertical shaft (silo) of data, only have less data between each vertical shaft, to share. For example, many personal computers (PC) user has storage different more than 5, and they comprise about they submit mutual people's information-such as Outlook contact person, online account address, Windows address book, Quicken payee and instant message (IM) partner list-because constituent act proposes important challenge to these pc users at certain one deck. Because most of existing file system utilize nested file metaphor to come constituent act and file, therefore when quantity of documents increases, become very surprising for keeping the necessary effort of flexible and effective enterprise schema. In these cases, the multiple classification that has a Single document is very useful; Yet use the hard and soft link in the existing file system to be trouble and to be difficult to safeguard.

Past has been made the shortcoming that some unsuccessful trials overcome file system. But some have related to certain in attempting before these memory with the content addressing and provide and can rather than visit the mechanism of data by physical address by content. Yet, these effort are proved to be unsuccessful, but although thereby the memory of content addressing to being proved to be useful by using such as the small-scale of the equipment such as high-speed cache and MMU, but still impossible owing to a variety of causes to the extensive use such as equipment such as physical storage mediums, therefore such solution exists seldom or never. Made other trial of using OODB Object Oriented Data Base (OODB) system, although but these trials are with the feature of strong database, and good non-representation of file, but processing aspect the representation of file ineffectively, can not reappear on hardware/software interface is system-level speed, efficient and simplicity based on file and the file of hierarchy. Use other trial of SmallTalk (with other derivation method) being proved to be quite effective aspect processing file and the non-representation of file such as attempting, effectively organize and utilize the necessary database feature of the relation that exists but lack between various data files, therefore the whole validity of the sort of system is unacceptable. Use BeOS (with other such operating system research) although another trial can be competent at some necessary database feature is provided again when suitably representing file, be proved to be inadequate in the expression of processing non-file, this is the same core shortcoming of traditional file systems.

Database technology is another professional domain that has similar challenge. For example, although the relevant database model has been obtained very large coml success, in fact stand alone software retail trader (ISV) has generally used available function sub-fraction in the relevant database software product (such as Microsoft SQL Server). On the contrary, the great majority of application program and such product are the form with simple " gets " and " puts " alternately. Although this is had some reasons of understanding easily (as platform or database unknowable), the reason of a commonly overlooked key is that database there is no need to provide accurately abstract that main commercial application program retail trader needs really. For example, although really the world has concept such as " client " or " projects " such as " orders " (and " line item " of the embedding of order is as wherein project and project itself), and relevant database only table and capable aspect talking about. As a result, although application program may wish to have uniformity, locking, safety and/or trigger on the project level aspect (only listing), database only provides these features in table/row level usually. If also can work finely although each project is mapped to the single row of certain table of database, but in the situation with the order of a plurality of line items, exist a project in fact will be mapped to the reason of a plurality of tables, and in the case, single system R can not provide correct abstract definitely. Therefore, application program must be at the top layer construction logic of database to provide these substantially abstract. In other words, the fundamental relation model does not provide enough platforms of the storage data of developing easily advanced application thereon, because the fundamental relation model need to be between application program and storage system indirect layer, wherein only in the application program of some situation, can see the semantic structure of data. Although some database retail trader just is being building up to Premium Features in their product and (as is providing the object relationship ability, new organize models etc.), so far which still not having, the total solution that needs is provided, and wherein real total solution is the solution of the data model abstract (such as " project ", " expansion ", " relation " etc.) that provides usefulness for useful territory abstract (such as " individual ", " position ", " event " etc.).

Consider the above-mentioned shortcoming in available data storage and the database technology, need a kind of new storage platform, a kind of improved ability is provided for it so that all types of data in tissue, search and the Sharing computer system-a kind of storage platform, it is expanded outside existing file system and Database Systems and has enlarged data platform, and is designed to store all types of data. This demand has been satisfied in the present invention and previous relevant invention incorporated herein by reference. Especially, the invention provides the expansion of the object of being processed by hardware/software interface system and the method for succession.

General introduction

Below general introduction provide take the front by with reference to the relevant invention (" relevant invention ") of the institute's combination summary as the various aspects of the present invention of background note. This general introduction does not aim to provide the exhaustively explanation of all importances of the present invention, neither be to the restriction of scope of the present invention. But this general introduction is intended to as following detailed description and the introduction of accompanying drawing.

Relevant invention jointly relates to the storage platform for tissue, search and shared data, and the concept of data storages is expanded and enlarged to described storage platform outside existing file system and Database Systems. This storage platform is designed to store all types of data, comprises structurized, non-structured or partly-structured data.

This storage platform is included in the data storage that realizes on the database engine. Described database engine comprises the relevant database engine with the relevant expansion of object. Described data storage has realized a kind of data model, and it supports tissue, search, shared, the synchronous and safety of data. Stated the particular type of data with various modes (schema), and this platform provides a kind of mechanism, the setting of its mode of extension is in order to define new data type (mainly being the subtype of the fundamental type that is provided by described pattern). A kind of synchronizing function helps at user or system's data sharing. The function of filesystem class is provided, and it allows the interoperability of described data storage and existing file system, and does not have the restriction of this traditional file systems. A kind ofly change the ability that follow-up mechanism provides the change of tracking data storage. This storage platform also comprises one group of application programming interfaces, and they be so that application program can be accessed the above-mentioned all functions of described storage platform, and can access the data with the pattern statement.

The data model of being realized by the storage of described data with project, element and contextual definition the unit of data storages. Project is the unit of storable data in the data storage, and can comprise one or more elements and relation. Element is the example of type, comprises one or more fields (being also referred to as attribute herein). Relation is two connections between the project. (as used herein, these and other specific term can be capitalized, in order to they are separated near employed other term, yet, be not to be intended to treat with a certain discrimination the term capitalized for example " Item " and the same term during by capitalization, for example " item ", and should not suppose or hint this difference. )

This computer system also comprises a plurality of projects, and wherein each project comprises that one can be by the discrete storable information unit of hardware/software interface system operation; A plurality of project folders, they have consisted of the institutional framework of described project; And for the hardware that operates a plurality of projects/software interface system, and wherein each project belongs at least one project folder, and can belong to the project folder more than.

Opposite with derivation from lasting storage, project or some item attribute value can dynamically be calculated. In other words, described hardware/software interface system does not need project to be stored, and support some operation, function such as the Set For Current of enumerating project, or the project that provides at the identifier on the storage platform (describing in the part of API or API and more completely illustrated) and the ability of search terms-for example, project can be cellular current location, or the temperature of reading from temperature sensor. Described hardware/software interface system can process a plurality of projects, and can comprise the project that can be interconnected by a plurality of relations of described hardware/software interface system management.

Be used for the hardware of this computer system/software interface system and also comprise core schema, understand in order to define described hardware/software interface system, and one group of core project can a kind of predetermined and predictable mode directly processing. In order to process a plurality of projects, described computer system interconnects project and a plurality of relation, and in hardware/described relation of software interface system layer management.

The API of this storage platform provides data class for each project, project expansion and the relation that defines in storage platform pattern group. In addition, API provides a framing class, and they have defined one group of public action for described data class, and provides basic programming model with data class for storage platform API. Described storage platform API provides the interrogation model of simplifying, its mode so that the application programmer is kept apart from the details of the query language of underlying database engine is so that the application programmer can form the inquiry of the various attributes of the project in the based on data storage. Storage platform API also collects the change of project being made by application program, and then they is organized in the required correct renewal of the database engine (or storage engines of any kind) of realizing described data storage. This and leaves the ins and outs of data storage update for API so that the application programmer can change project in memory.

By its common storage basis with by the data of medelling, storage platform of the present invention can be made more effective application program exploitation for consumer, Knowledge Worker and enterprise. It provides abundant and extendible API, this interface not only so that in its data model intrinsic function can use, but also comprise and expanded the access method of existing file system and database.

In view of prolonging and whole structures (describing in detail among the chapters and sections II that is describing in detail) in relevant invention, the present invention is particularly for the function of the use of expanding with expansion project and attribute type, and the use of inheriting is to promote at the effective search between the relevant item and tissue (describing in detail among the chapters and sections III that is describing in detail). Other further feature of the present invention and advantage can become apparent by following the detailed description and the accompanying drawings of the present invention.

Brief description of drawings

When reading in conjunction with appended accompanying drawing, can understand better top summary and following detailed description of the invention. For the purpose of illustrating the invention, the exemplary embodiment of various aspects of the present invention shown in the drawings; Yet, the invention is not restricted to disclosed concrete grammar and means. In the accompanying drawings:

Fig. 1 is the block diagram that expression aspect of the present invention can combined computer system within it;

Fig. 2 is a block diagram, shows the computer system that is divided into 3 assembly groups: nextport hardware component NextPort, hardware/software systems interface module and application component;

Fig. 2 A shows for the traditional hierarchy based on tree that is grouped into based on the file in the file in the catalogue of the operating system of file;

Fig. 3 shows the block diagram of a storage platform;

Fig. 4 shows the structurized relation between project, project folder and the kind;

Fig. 5 A shows the block diagram of the structure of project;

Fig. 5 B shows the block diagram of complex properties type of the project of Fig. 5 A;

Fig. 5 C shows the block diagram of " Location (position) " project, and wherein the complicated type of " position " project is further specified (being listed clearly);

Fig. 6 A shows one as the project of the subtype of the project in the basic schema;

Fig. 6 B shows the block diagram of the subtype project of Fig. 6 A, has wherein listed clearly the type (except its direct attribute) of its succession;

Fig. 7 shows the block diagram of basic model, and this basic model comprises its two top layer class types, project and attribute basis, and from its additional basis mode type that draws;

Fig. 8 A shows the block diagram of the project in the core schema;

Fig. 8 B shows the block diagram of the attribute type in the core schema;

Fig. 9 is a block diagram, shows project folder, its member's project and the interconnected relationship between project folder and its member's project;

Figure 10 is a block diagram, shows kind (itself also is a project), its member's project and the interconnected relationship between kind and its member's project;

Figure 11 shows the figure of reference type level of the data model of storage platform;

It is the figure how to be classified that Figure 12 shows relation;

Figure 13 shows the figure of notice mechanism;

Figure 14 shows the figure of an example, and wherein two affairs are all inserted new record in same B tree;

Figure 15 shows data and changes Check processing;

Figure 16 shows exemplary directory tree;

Figure 17 shows an example, and wherein the file of existing file system based on catalogue is moved in the described storage platform data storage;

Figure 18 shows the concept of holding file;

Figure 19 shows the basic architecture of storage platform API;

Figure 20 has schematically shown each assembly of storage platform API stack;

Figure 21 A is the diagrammatic representation of contact item's pattern of example;

Figure 21 B is the diagrammatic representation of element of contact item's pattern of the example of Figure 21 A;

Framework when Figure 22 shows the operation of storage platform API;

Figure 23 shows the execution of " FindAll " operation;

Figure 24 shows such processing, processes from the storage platform pattern generating storage platform API class by this;

Figure 25 shows such pattern, and file (File) API is based on this pattern;

Figure 26 shows the schematic diagram for the access mask form of data security purpose;

Figure 27 (part a, b, c) has provided a new safety zone of being protected in the same manner of being divided out in existing safety zone;

Figure 28 shows the schematic diagram of the concept of project search view;

Figure 29 shows the schematic diagram of the project layering of example;

Figure 30 A shows the interface " interface 1 " as pipeline, and the first and second coding sections are by this interface communication;

Figure 30 B shows an interface, and this interface comprises interface object I1 and I2, and it is so that the first and second coding sections of system can be by medium M communication;

Figure 31 A the function that is provided by interface " interface 1 " is provided can how be divided, in order to the communication of interface is transformed into a plurality of interfaces " interface 1A ", " interface 1B ", " interface 1C ";

How the function that is provided by I1 Figure 31 B can be divided into a plurality of interface I1A, I1B, I1C if being provided;

Figure 32 A shows a kind of situation, and wherein insignificant parameter p recision can be left in the basket or by with parameter replacement arbitrarily;

Figure 32 B shows a kind of situation, and wherein the replaced interface of interface is replaced, and described alternative interface is designated be used to ignoring or adding parameter to interface;

Figure 33 A shows a kind of situation, and wherein the first and second coding sections are integrated in both modules that comprises them;

Figure 33 B shows a kind of situation, and wherein part or all of interface can write in another interface with being embedded into, in order to form merged interface;

Figure 34 A show intermediate equipment one or more how can change the communication on the first interface in order to make them meet one or more different interfaces;

Figure 34 B shows coding section and how can introduce in order to receive from the communication of an interface and with described function with interface and be transferred to the second and the 3rd interface;

How Figure 35 A can be transformed into the communication from a coding section another coding section if showing instant compiler (JIT);

Figure 35 B shows for the JIT method that dynamically rewrites one or more interfaces, it can be applied to dynamic factor or otherwise change described interface;

Figure 36 illustrates the subset of a series of relevant items and relation thereof;

Figure 37 A illustrates the shortcoming for the standard SubClassing of the project of using special-purpose purpose;

Figure 37 B illustrates the part solution of standard SubClassing problem; And

Figure 37 C illustrates one embodiment of the present of invention, uses expansions different from contact person itself and that be independent of it to come the expansion project, thereby allows the polymorphic type function.

Describe in detail

Catalogue

I. foreword ... 14

A. exemplary computing environment ... 14

B. traditional storage based on file ... 17

II. the WINFS storage platform that is used for tissue, search and shared data ... 18

C. vocabulary ... 18

D. storage platform is summarized ... 18

E. data model ... 20

1. project ... 21

2. project label ... 23

3. project folder and classification ... 24

4. pattern ... 26

A) basic schema ... 26

B) core schema ... 26

5. concern ... 28

A) relation statement ... 28

B) hold relation ... 29

C) embed relation ... 30

D) quote relation ... 31

E) Rule and constraint ... 32

F) ordering of relation ... 32

6. extensibility ... 36

A) project expansion ... 37

B) expansion NestedElement type ... 40

F. database engine ... 41

1. use the data storage of UDT to realize ... 42

2. project mapping ... 42

3. expansion mapping ... 43

4. nested element mapping ... 44

5. object identity ... 44

6.SQL object naming ... 44

7. row name ... 45

8. search view ... 45

A) project ... 46

(1) major event order search view ... 46

(2) the project search view of classifying type ... 46

B) project expansion ... 47

(1) main expanded search view ... 47

(2) the expanded search view of classifying type ... 47

C) nested element ... 48

D) relation ... 48

(1) primary relation search view ... 48

(2) relationship example search view ... 48

      e) …………………………………………………………………49

9. upgrade ... 49

10. change and follow the tracks of and gravestone ... 50

A) change tracking ... 50

(1) change in " master " search view is followed the tracks of ... 50

(2) change in " classifying type " search view is followed the tracks of ... 51

B) gravestone ... 52

(1) project gravestone ... 52

(2) expansion gravestone ... 52

(3) concern gravestone ... 53

(4) gravestone is removed ... 53

11. assistant API and letter ... 54

A) function [System.Storage] .GetItem ... 54

B) function [System.Storage] .GetExtension ... 54

C) function [System.Storage] .GetRelationship ... 54

12. metadata ... 54

A) pattern metadata ... 54

B) example metadata ... 54

G. security ... 54

H. notify and change tracking ... 55

I. synchronous ... 55

Storage platform to storage platform synchronously ... 56

A) synchronous (Sync) controlling application program ... 56

B) pattern note ... 57

C) synchronously configuration ... 58

(1) community's file-mapping ... 58

(2) overview ... 59

(3) timetable ... 60

D) conflict is processed ... 60

(1) collision detection ... 60

(a) based on the conflict of knowledge ... 60

(b) conflict of Constraint-based ... 61

(2) conflict is processed ... 61

(a) automatic collision decomposition ... 61

(b) conflict log recording ... 62

(c) conflict examination and decomposition ... 62

(d) propagation of the convergence of duplicate and collision decomposition ... 62

To the storage of non-storage platform data synchronously ... 63

A) synchronously service ... 63

(1) change is enumerated ... 63

(2) change application ... 64

(3) collision decomposition ... 65

B) adapter is realized ... 65

3. security ... 65

4. manageability ... 66

J. traditional file interoperability ... 66

K. storage platform API ... 66

III. expand and inherit ... 71

A. type system ... 72

B. type family ... 77

1. nested element type ... 77

2. item types ... 77

3. relationship type ... 78

A) relation is semantic ... 79

B) relation rule and constraint ... 80

4. expansion type ... 81

C. the function that strengthens ... 82

1. inherit ... 82

2. expansion ... 83

IV. conclusion ... 84

I. foreword

Theme of the present invention is described with details, to satisfy legal requirement. Yet itself does not attempt to limit the scope of this patent this description. On the contrary, present inventor imagination, claimed theme also can otherwise be implemented, and comprises the different step that is similar to this declarative description or the combination of step with the technology in and future current in conjunction with other. In addition, although term " step " can be used for meaning the different elements of the method that adopts here, however implicit specific order between each step that this term can not be interpreted as here disclosing, unless described clearly the order of each step.

A. exemplary computing environment

Many embodiment of the present invention can carry out on computers. Fig. 1 and following discussion aim to provide the concise and to the point description that wherein realizes suitable computing environment of the present invention. Although be not essential, aspects of the present invention can be with such as by describing in the context as the computer executable instructions of the program module carried out on the computer of client workstation or server. Generally speaking, program module comprises routine, program, object, assembly, data structure etc., and they are carried out particular task or realize particular abstract data type. In addition, the present invention can realize with other computer system configurations, comprises handheld device, multicomputer system, based on the system of microprocessor or programmable consumer electronics, network PC, minicomputer, large scale computer etc. The present invention can also realize in DCE that wherein task is by finishing by the teleprocessing equipment of communication network link. In DCE, program module can be arranged in the Local or Remote memory storage device.

As shown in Figure 1, exemplary general-purpose computing system comprises traditional personal computer 20 etc., and it comprises processing unit 21, system storage 22 and will comprise that the various system components of system storage are coupled to the system bus 23 of processing unit 21. System bus 23 can be several bus-structured any, any the local bus that comprises memory bus or memory controller, peripheral bus and use various bus architectures. System storage comprises read-only storage (ROM) 24 and random access storage device (RAM) 25. Basic input/output 26 (BIOS) comprises as help the basic routine of transmission information between all elements at personal computer 20 when starting, and is stored among the ROM 24. Personal computer 20 can comprise that also the disc driver 28, read-write of hard disk drive 27, the read-write moveable magnetic disc 29 of reading writing harddisk (not shown) are such as the CD drive 30 of the removable CD 29 of CDROM or other light medium. Hard disk drive 27, disc driver 28 and CD drive 30 are respectively by hard disk drive interface 32, disk drive interface 33 and CD drive interface 34 connected system buses 23. Driver and relevant computer-readable medium thereof provide the non-volatile memory of computer-readable instruction, data structure, program module and other data for personal computer 20. Although exemplary environment described herein adopts hard disk, moveable magnetic disc 29 and removable CD 31, those skilled in the art understand, but in the exemplary operation environment, also can use stored energy by other type computer computer-readable recording medium of the data of computer access, such as cassette tape, flash card, digital video disc, Bernoulli cassette tape, random access memory (RAM), read-only storage (ROM) etc. Similarly, the example environment also can comprise is permitted eurypalynous surveillance equipment, such as temperature-sensitive and safety or fire alarm system, and other information source.

Some program modules can be stored among hard disk, disk 29, CD 31, ROM 24 or the RAM 25, comprise operating system 35, one or more application program 36, other program module 37 and routine data 38. The user can be input to personal computer 20 by ordering such as input equipments such as keyboard 40 and positioning equipments 42 with information. Other input equipment (not shown) can comprise microphone, control stick, game mat, disc type satellite antenna, scanner etc. Here be connected to processing unit 21 with other input equipment normal open overcoupling to the serial line interface 46 of system bus, but also can connect by other interface, such as LPT, game port or USB (USB). The display device of monitor 47 or other type also is connected to system bus 23 by the interface such as video adapter 48. Except monitor 47, personal computer generally includes such as other peripheral output equipment (not shown) such as microphone and printers. The example system of Fig. 1 also comprises primary adapter 55, small computer system interface (SCSI) bus 56 and is connected to the External memory equipment 62 of SCSI bus.

Personal computer 20 can use logic such as one or more remote computers of remote computer 49 and be connected in the network environment and operate. Remote computer 49 can be another personal computer, server, router, network PC, peer device or other common network node, and generally include above many or all elements that personal computer 20 is described, although memory storage device 50 only is shown in Fig. 1. The logic that draws among Fig. 1 connects and comprises LAN (LAN) 51 and wide area network (WAN) 52. Such network environment is common in office, enterprise-wide computer network, Intranet and internet.

When using in the lan network environment, personal computer 20 is connected to LAN51 by network interface or adapter 53. When using in the WAN network environment, personal computer 20 generally includes modem 54 or is used for by setting up other device of communication such as the wide area networks such as internet 52. Built-in or external modem 54 is by serial port interface 46 connected system buses 23. In network environment, program module or its part that relative personal computer 20 draws can be stored in the remote memory memory device. Be appreciated that the network connection that illustrates is exemplary, can use other device of between computer, setting up communication link.

Shown in the block diagram of Fig. 2, computer system 200 can be divided into three assembly groups roughly: nextport hardware component NextPort 202, hardware/software interface system component 204 and application component 206 (being also referred to as " nest " or " component software " here in some context).

Get back to Fig. 1, in the various embodiment of computer system, nextport hardware component NextPort 202 can comprise CPU (CPU) 21, memory (ROM 24 and RAM 25), basic input/output (BIOS) 26 and various I/O (I/O) equipment, such as keyboard 40, mouse 42, monitor 47 and/or printer (not shown) etc. Nextport hardware component NextPort 202 comprises the basic physical basis structure of computer system 200.

Application component 206 comprises various software programs, includes but not limited to compiler, Database Systems, documentor, commercial program, video-game etc. Application program provides computer resource to be used to various users (machine, other computer system and/or end user) to deal with problems, provide the means of solution and deal with data.

Hardware/software interface system component 204 comprises (can only comprise in certain embodiments) operating system, itself comprises shell and kernel the most applications latter. " operating system " is the separate procedure of taking on the intermediary between application program and computer hardware (OS). Hardware/software interface system component 204 also can comprise virtual machine manager (VMM), common statement Runtime Library (CLR) or its functional equivalent, Java Virtual Machine (JVM) or its functional equivalent or the operating system place in computer system or other component software outside the operating system. The purpose of hardware/software interface system provides the therein environment of executive utility of user. The target of any hardware/software interface system is to make computer system easy to use, and utilizes computer hardware in effective mode.

Hardware/software interface system generally is loaded into computer system when starting, and manages subsequently all application programs in computer system. Application program is by coming and hardware/software interface system interaction via application programming interfaces (API) request service. Some application program can be passed through such as command lanuage or graphic user interface (GUI) and hardware/software interface system interaction the end user.

Hardware/software interface system is the various services of executive utility traditionally. In multitask hardware that a plurality of programs are moved simultaneously/software interface system, what time sort run is which application program hardware/software interface system determine with, and how long allows in turn each being used journey before switching to the Another Application program. Hardware/software interface system also manages sharing of between a plurality of application programs internal storage, and processes the input and output that commute such as the additional hardware device such as hard disk, printer and dialing port. Hardware/software interface system also sends to the message about mode of operation and contingent any mistake each application program (arriving in some cases the end user). Hardware/software interface system also can pass down (offload) batch processing operation management of (as printing), so that the application program that starts can be broken away from this work and restart other processing and/or operation. On the computer that parallel processing can be provided, hardware/software interface system also manages partition program, so that it moves at a plurality of processors simultaneously.

Hardware/software interface system shell (being called for short " shell " here) is the interactive end-user interface to hardware/software interface system. (shell is also referred to as " command interpreter ", or is called " operating system shell " in an operating system). Shell be can be directly by the skin of the hardware of application program and/or visit to end user/software interface system. Opposite with shell, the innermost layer of the hardware that kernel is direct and nextport hardware component NextPort is mutual/software interface system.

Be particularly useful for computerized system although can conceive many embodiment of the present invention, yet do not mean that in the present note and limit the invention to those embodiment. On the contrary, term used herein " computer system " is intended to comprise can Storage and Processing information and/or can use any and all devices of behavior or the execution of canned data control appliance itself, and no matter whether those equipment are electronics, mechanical, logic or virtual in essence.

B. traditional storage based on file

In current most computers system, " file " is the unit that can store information, and it can comprise hardware/software interface system and application program, data set etc. In all modern hardware/software interface systems (Windows, Unix, Linux, MacOS, virtual machine system etc.), file is can be by basic discrete (can store and can retrieve) information unit of hardware/software interface system processing. The file group is organized into " file " usually. In Microsoft Windows, Macintosh OS and other hardware/software interface system, file be can be retrieved as single information unit, the set of the mobile and file processed. These files and then be organized into are called arranging based on tree-like hierarchy of " catalogue " (discussing in detail in the back). As Dos, z/OS and great majority based on other hardware of the operating system of Unix/software interface system in, term " catalogue " and/or " file " are interchangeable, and early stage apple computer system (such as Apple IIe) uses term " classification " to replace catalogue; Yet all these terms are regarded as synonym and can being used alternatingly when here using, and are intended to also to comprise quoting all other equivalent terms of hierarchical information storage organization and file and file components.

Traditionally, catalogue (catalogue that has another name called file) is based on tree-like hierarchy, and its File is combined into file, file and then the relative node location arrangement of pressing the formation directory tree. For example, shown in Fig. 2 B, constituent instruments folder (or " root ") 212 based on the file system of DOS can comprise a plurality of files 214, its each can also comprise other file (such as " sub-folder " of specific file) 216, and these each comprises other file 218, to infinity. Each of these files can have one or more files 220, although on hardware/software interface is system-level, what common ground each file in the file does not have except their positions in tree-like hierarchy. Physical organization not strange, file organization has been reflected indirectly the typical storage medium (such as hard disk, floppy disk, CD-ROM etc.) that is used for these files of storage to the method for document layered structure.

Except above-mentioned, each file be to its sub-folder and its catalogue container-namely, each file has its sub-folder and file. For example, when file was deleted by hardware/software interface system, the sub-folder of this document folder and file be deleted (sub-folder and the file that also recursively comprise it in the situation of each sub-folder) also. Equally, each file is general only to be had by a file, although and file can be copied and copy is positioned at different files, the copy of file itself is difference and separate unit, it with original document without directly being connected (on hardware/software interface is system-level, not being reflected to wave file such as the change to original document). Therefore in this respect, file and file are " physics " in itself, and container is processed because file is similar to physics, and file as different in these containers and independently physics unit usually process.

II. the WINFS storage platform that is used for tissue, search and shared data

The present invention in conjunction with invention incorporated herein by reference for the storage platform that is used for tissue, search and shared data. Storage platform of the present invention is expanded and has been widened data platform, surmounts file system discussed above and Database Systems, and is designed to store all types of data, comprises the data of the new form that is called project.

C. vocabulary

Reach the term that in claims, uses here following meaning arranged:

" project " is the unit of energy storage hardware/addressable information of software interface system, do not resemble simple files, and it is to have the object that is represented the basic attribute set of jointly supporting to all objects of end user by hardware/software interface system shell. Project also tool comprises the feature (discussing in detail below) that allows to introduce new attribute and relation to common attribute and the relation of supporting of all items type.

" operating system " is the separate procedure of disguising as the intermediary between application program and the computer hardware (OS). In most of the cases, operating system comprises shell and kernel.

" hardware/software interface system " is the combination of software or hardware and software, and it plays a part at the bottom hardware assembly of computer system and the interface between the application program that computer system is carried out. Hardware/software interface system generally includes (including only in certain embodiments) operating system. Hardware/software interface system can also comprise virtual machine manager (VMM), common statement Runtime Library (CLR) or its functional equivalent, Java Virtual Machine (JVM) or its functional equivalent or at the operating system place of computer system or other component software except operating system. The purpose of hardware/software interface system provides the environment of user's energy executive utility. The target of any hardware/software interface system is to make computer system easy to use, and utilizes computer hardware with effective means.

D. storage platform is summarized

With reference to figure 3, storage platform 300 is included in the data storage 302 that realizes on the database engine 314. In one embodiment, database engine comprises the relevant database engine with the object relationship expansion. In one embodiment, relevant database engine 3 14 comprises Microsoft SQL Server relevant database engine. Data storage 302 realizes supporting the tissue, search of data, shared, synchronous and safe data model 304. In such as pattern 340 isotypes, describe specific data type, and storage platform 300 is provided for adopting these patterns and for the instrument 346 of expanding these patterns, this describes in detail in the back.

The change follow-up mechanism 306 that realizes in data storage 302 provides the ability of the change of tracking data storage. Data storage 302 also provides security capabilities 308 and upgrading/degradation ability 310, all describes in detail later. Data storage 302 also provides one group of application programming interfaces 312, to represent the ability of data storage 302 to other storage platform assembly that utilizes this storage platform and application program (such as application program 350a, 350b and 350c). Storage platform of the present invention also comprises application programming interfaces (API) 322, makes such as application program 350a, and 350b, and the application program such as 350c can be accessed all above-mentioned functions of storage platform and can access the data of describing in pattern. Application program can be in conjunction with using storage platform API 322 such as other API such as OLE OB API 324 and Microsoft Windows Win 32 API 326.

Storage platform 300 of the present invention can provide various services to application program, comprises the synchronous service 330 of being convenient at the data sharing of user or system. For example, serve synchronously 330 permissions and have the interoperability of storing other data storage 340 of 302 identical forms with data, and access has the data storage 342 of other form. Storage platform 300 also provides data storage 302 and the file system ability such as the interoperability of Windows new technology file system 318 systems such as existing file such as grade of allowing. In some embodiment at least, storage platform 320 can also provide other ability to application program, data is worked and allows mutual with other system allowing. These abilities may be embodied in such as Info Agent service 334 and notice and serve in the form of 332 Additional Services such as grade 328, and are embodied in the form of other utility program 336.

In some embodiment at least, storage platform is implemented, or is formed its complete part with the hardware of computer system/software interface system. For example and unrestricted, storage platform of the present invention can be implemented with operating system, virtual machine manager (VMM), common statement Runtime Library (CLR) or its functional equivalent or Java Virtual Machine (JVM) or its functional equivalent, or forms its complete part. By its public storage basis and the data of medelling, storage platform of the present invention makes consumer, knowledge worker and enterprise can more effectively carry out the exploitation of application program. It provides abundant and extendible programming surf zone, is contained in the ability in its data model in not only can obtaining, and can also comprise and expand existing file system and database access method.

Reach in the foregoing description in various accompanying drawings, storage platform 300 of the present invention can be called " WinFs ". Yet use this name to refer to that storage platform only is for convenience, does not attempt to make restriction like this.

E. data model

The data of storage platform 300 of the present invention are stored 302 and are realized a kind of data model, and its is supported the tissue that resides in the data in the data storage, search, shared, synchronous and safety. In data model of the present invention, " project " is the elementary cell of storage information. This data model provides a kind of mechanism, be used for statement project and project expansion, be used for being based upon the relation between the project and be used for the project organization to project folder and classification, the below is with more abundant description.

This data model depends on two primitive mechanism: type and relation. Type provides the structure of form of form of the example of domination type. Form is expressed as orderly group of attribute. Attribute is the name of the value or set of values of given type. For example, USPostalAddress (United States Post Office address) type has attribute Street (street), City (city), Zip (postcode), State (state), wherein Street, City and State are the String types, and Zip is the Int32 type. Street can be many-valued (i.e. a class value), allows the address that the Street attribute is had value more than. Some primitive type that system definition can be used in other type structure comprises String, Binary, Boolean, Int16, Int32, Int64, Single, Double, Byte, DateTime, Decimal and GUID. Can use any primitive type (with some restriction of following note) or the type of any structure to come the attribute of define styles. For example, Location (position) type definable has attribute Coordinate (coordinate) and Address (address), and wherein the Address attribute is above-mentioned type USPostalAddress. Attribute also can be essential or optional.

Relation can be declared and represent the mapping between the example collection of two types. For example, the relation of stating can be arranged between Person (individual) type and Location type, be called LivesAt (living in), it determines where who lives in. Relation has name and two end points, i.e. source endpoint and target end points. Relation also can have the ordered set of attribute. Source endpoint and target end points all have name and type. For example, the LivesAt relation has the source of the Occupant (resident) that is called type Person and is called the target of the Dwelling (house) of type Location, and have in addition attribute StartDate (from date) and EndDate (date of expiry), represent that this resident living is in the time period of this house. Notice that pass in time, the individual can live in a plurality of houses, and house can have a plurality of residents, be originally to be in relation so place the most probable place of StartDate and EndDate information.

Contextual definition by the mapping between the example of the type constraint that provides as endpoint type. For example the LivesAt relation can not be that wherein Automobile (automobile) is Occupant (resident's) relation, because Automobile is not Person.

Subtype between data model permission define styles-superclass type relation. Subtype-the superclass that is also referred to as the fundamental type relation is the as follows definition of type relation, if type A is the fundamental type of type B, each example that then must be B also is the situation of the example of A. The another kind of method of expressing is that each example that meets B must meet A. For example, if A has the attribute Name (name) of String type, and B has the attribute Age (age) of Int16 type, then draws, and any example of B must have Name and Age concurrently. The hierarchy of type can be envisaged as the tree with the single superclass type on root. The branch of root provides first order subtype, and this grade branch provides second level subtype, and so on, until itself no longer have end of blade (leaf-most) subtype of any subtype. Tree is not limited to the unified degree of depth, but can not comprise any loop. Given type can have zero perhaps many subtypes and zero or a superclass type. Given example can meet at most the superclass type an of type and the type. In other words, to the tree in arbitrary grade locate given example, this example can meet at most a subtype on this grade. If the example of a type must also be the example of the subtype of the type, then to be said to be abstract to the type.

1. project

Project is the unit of storable information, does not resemble simple file, and it is the object with the common basic attribute set supported of all objects that is represented to end user or application program by storage platform. Project also has common attribute and the relation of supporting of all items type, comprises that permission as described below introduces new attribute and the feature of relation.

Project is the object of common operation, as copying, delete, move, open, print, back up, recover, copy etc. Project is the unit that can be stored and retrieve, and the form of ownership of the stored information of being processed by storage platform exists as attribute or the relation between the project of project, project, its each more discuss in detail below.

That project is intended to represent reality and hold intelligible data cell, such as contact person (Contacts), people (People), service (Services), position (Locations), (various types of) document (Documents) etc. Fig. 5 A is the block diagram that the structure of project is shown. The underproof name of this project is " Location ". The qualified name of this project is " Core.Location ", and it shows that this project structure is defined by the project (the Core pattern discusses in detail below) of the particular type in Core (core) pattern.

The Location project has a plurality of attributes, comprises EAddress (e-mail address), MetropolitanRegion (urban place), Neighborhood (neighbour) and PostalAddress (postal address). The particular type attribute of each project represents immediately following attribute name ground, and separates with colon (": ") and attribute name. The right in type name, the quantity of the value that this attribute type is allowed represent that between square brackets (" [] ") wherein the asterisk (" * ") on colon (": ") the right represents unspecified and/or unconfined quantity (" many "). " 1 " on colon the right shows maximum values. Zero (" 0 ") on the colon left side shows that this attribute is optional (fully void value). " 1 " on the colon left side shows to have a value (this attribute is necessary) at least. Neighborhood and MetropolitanRegin all are " nvarchar " types (or connection of equivalent type), and it is predefined data type or " simple types " (representing with lacking capitalization here). Yet EAddress and PostalAddress are respectively the defined type of type EAddress and PostalAddress or the attribute of " complicated type " (here with capitalization mark). Complicated type is from one or more simple data types and/or the type that derives from other complicated type. The complicated type of the attribute of a project also consists of " nested element ", because the details of complicated type is nested in the direct project to define its attribute, and the information that belongs to these complicated types is kept (in the border of this project, discussing such as the back) with the project with these attributes. These concepts of type are that the crowd knows, and are understood by those skilled in the art easily.

Fig. 5 B is the block diagram that complex properties type PostalAddress and EAddress are shown. The definition of PostalAddress attribute type, the project of attribute type PostalAddress can expect to have zero or a City (city) value, zero or a Country Code (country code) value, zero or MailStop (country code) value and any quantity (zero to many) PostalAddress type etc. In this way, defined the shape of the data of the particular community in the project. The EAddress attribute type is similarly definition as shown. Although optionally use in this application here, the other method that is illustrated in complicated type in the Location project is to use each attribute of each complicated type of wherein listing to draw this project. Fig. 5 C is the block diagram that the Location project is shown, and further describes therein its complicated type. Yet should be appreciated that the another kind of Location project represents it just is same project to shown in Fig. 5 A in this Fig. 5 C. Storage platform of the present invention also allows subclassification (subtyping), thereby an Attribute class can be another subtype (one of them Attribute class is inherited the attribute of another father's attribute type).

Be similar to but be different from attribute and their attribute type, Item (project) type of project inheritance ground expression its oneself, it also is the theme of subclassification. In other words, the subtype that to allow a project be another project of the storage platform among some embodiment of the present invention (thereby project is inherited the attribute of another father's project). In addition, to various embodiment of the present invention, each project is the subtype of " Item " item types, and the latter is first and the basic item types (basic schema also discusses in detail in the back) that finds in basic schema. Fig. 6 A illustrates a project (in this example for Location project) and be the subtype of the Item item types that finds in basic schema. In this figure, arrow represents that Location project (such as all other projects) is the subtype of Item item types. Item item types as the elementary item of therefrom deriving all other projects has some important attributes such as ItemId and various time mark, thereby has defined the standard attribute of all items in the operating system. In this figure, these attributes of Item item types are inherited by Location, thereby and become the attribute of Location.

The another kind of method of expression attribute from the Location project that the Item item types is inherited is to use each attribute from each attribute type of father's project of wherein listing to draw Location. Fig. 6 B is the block diagram that the Location project is shown, and wherein describes the type of its succession except its direct attribute. Should note and understand, this project is the same project shown in Fig. 5 A, although in this figure, Location illustrates with all its attributes, comprise direct attribute (shown in Ben Tu and Fig. 5 A) and inherited attribute (shown in this figure but not shown in Fig. 5 A) (and in Fig. 5 A, being that the subtype of Item item types is quoted these attributes by the Location project is shown with arrow).

Project is object independently, if thereby delete a project, also the deleted entry purpose all directly and attributes of inheriting. Similarly, when retrieval during one project, retrieval be this project and all directly and the attribute (comprising the information that belongs to its complex properties type) of inheriting. Some embodiment of the present invention can make people can ask the subset of attribute when the retrieval specific project; Yet to many such embodiment acquiescences be provide when the retrieval have all its directly and the project of the attributes of inheriting. In addition, the attribute of project also can be expanded to the existing attribute of the type of this project by adding new attribute. These " expansions " are thereafter the real properties of this project, and the subtype of this item types can automatically comprise extended attribute.

" border " of project represented by its attribute (comprising complex properties type, expansion etc.). The border of project is also illustrated in the restriction of the operation of carrying out on the project, comprises copy, deletion, movement, establishment etc. For example in some embodiment of the present invention, when copy one project, all the elements within this project border also are copied. To each project, the border comprises following:

The item types of project, if and this project is another purpose subtype (in the situation such as some embodiment of the present invention of deriving from the single project of basic schema and item types at all items), is any applicable sub-type information (information that namely belongs to father's item types). If the original project that copies is another purpose subtype, this copy also can be this identical entry purpose subtype.

The complicated type attribute of project and expansion (if any). If original project has the attribute of complicated type (originally or expansion), copy also can have identical complicated type.

The record of the project on " ownership ", that is, the project that this project (" having project ") has what other project (" catalogue project ") has tabulation. This in particular concerns the rule that the project folder that discusses fully below and all items that mentions below must belong to a project folder at least. In addition, about embedding project (following more discuss fully), embedding project is considered to wherein embed the part such as the project of the operations such as copy, deletion.

2. project label

In overall project space, identify uniquely project with ItemID. The Base.Item type definition store the field ItemID of the type GUID of this project identity. One project must accurately only have an identity in the data storage.

It is the data structure that comprises location and identification item purpose information that project is quoted. In this data model, the abstract type of definition ItemReference by name therefrom derives all items reference type. ItemReference (project is quoted) type definition the virtual method of Resolve by name (parsing). The Resolve method is resolved ItemReference and is returned a project. The method is covered by the concrete subtype of ItemReference, and the latter realizes the function of given one search terms when quoting. Call the Resolve method as the part of storage platform API 322.

ItemIDReference (item id is quoted) is the subtype of ItemReference. It has defined Locator (locator) and ItemID field. The territory of Locator field name (i.e. sign) project. It is processed by the locator resolution method that the value of Locator can be resolved to the project territory. The ItemID field is the ItemID type.

ItemPathReference (item Path is quoted) is the particularization that defines the ItemReference of Locator and Path (path) field. Locator field identification one project territory. It is processed by the locator resolution method that the value of Locator can be resolved to the project territory. (relatively) path during the Path field comprises take the project territory that provided by Locator as the storage platform name space of root.

Can not in set operation, use this class reference. Quote generally and must resolve by path resolving. The Resolve method of storage platform API 322 provides this function.

Reform discussed above represents by the reference type hierarchy shown in Figure 11. The other reference type of inheriting from these types can define pattern. They can be used as the type of aiming field in the relation statement.

3. project folder and classification

As below will more discussing fully, project team can be organized into the special item that is called project folder (not obscuring with the file of file). Yet do not resemble most of file system, a project can belong to a plurality of project folders, so that when a project accessed and when revision in a project folder, the project of this revision subsequently can be directly from another project folder access. In fact, although can occur from different project folders the access of a project, in fact real access is same project. Yet a project folder needn't have its all member's projects, or owns project together in conjunction with other file simply, so that the unnecessary deletion that causes project of the deletion of a project folder. Yet in some embodiment of the present invention, a project must belong to a project folder at least, so that if unique file of specific project is deleted, then to some embodiment, this project is automatically deleted, or in other embodiment, this project automatically becomes the member of default item file, and (" Trash Can (dustbin) " file is at the conceptive similar name file that uses in various systems based on file and file that is similar to. )

More discuss fully as following, project also can belong to the classification based on the feature of common description, feature is such as (a) item types (or type), (b) specific directly or the attribute (or attribute) of inheriting, or (c) corresponding to the particular value (or value) of item attribute. For example, comprise that the project of the particular community of individual associated person information can belong to contact person (Contact) classification automatically, any project with associated person information attribute equally also belongs to this classification automatically. Equally, any project that has the position attribution of " New York City (New York) " value can belong to New York (NewYorkCity) classification automatically.

Classification is in the conceptive project folder part that is different from, project folder can comprise the mutually irrelevant project feature of common description (namely without), and each project in classification has common type, attribute or the value (" common point ") that this classification is described, just this concomitant basis that forms the relation between other project in it and this classification or those projects. In addition, although the membership qualification of the project in specific file is not compulsory aspect this project any specific, yet to some embodiment, all items with common point relevant with a classification in classification can automatically become such other member on hardware/software interface is system-level. Conceptive, classification also can be regarded the phantom item file as, its membership qualification is based on the ad hoc inquiry result of (as in the context of database), and the project that satisfies the condition (common point by classification is determined) of this inquiry should consist of such other membership qualification.

Fig. 4 is illustrated in the structural relation between project, project folder and the classification. A plurality of projects 402,404,406,408,410,412,414,418 and 420 are each project folder 422,424,426,428 and 430 member. Some project belongs to an above project folder, belongs to project folder 422 and 424 such as project 402. Some project, also be one or more classifications 432,434 and 436 member such as project 402,404,406,408,410 and 412, and other project, such as project 44,416,418 and 420 can not belong to any classification (although this major part does not resemble in certain embodiments, wherein has any attribute and automatically hints membership qualification in the classification, therefore in such embodiment in order not to be the member of any classification, project should be fully without feature). Opposite with the hierarchy of file, classification and project folder all have more the structure as directed digraph. Under any circumstance, project, project folder and classification all are project (although being different item types).

Opposite with file, file and catalogue, the feature of project of the present invention, project folder and classification is not " physics " in itself, because they do not have notional equivalence of physics container, thereby project can be present in position such more than. The ability that project is present in an above item file position and is organized into classification provides in hardware/software interface level and has strengthened and the data of enriching degree are processed and the storage organization ability, has surmounted in the art current available ability.

4. pattern

A) basic schema

For the general basis of establishment and the project of use is provided, each embodiment of storage platform of the present invention comprises basis (Base) pattern that is used for creating and organizing the conceptual frame of project and attribute of setting up. Basic schema has defined project and the attribute of some particular type, and the feature that therefrom further derives these specific fundamental types of subtype. Use this basic schema that the programmer can be distinguished project (and type separately) and attribute (and type separately) conceptive. In addition, basic schema is listed the basic attribute set that all items can have, because all items (and corresponding item types) is this elementary item (and the corresponding item types) derivation from basic schema.

As shown in Figure 7, for some embodiment of the present invention, basic schema definition three top layer type: Item (project), Extension (expansion) and PropertyBase (attribute basis). As shown in the figure, the attribute definition by this basic " Item " item types item types. On the contrary, top layer attribute type " PropertyBase " does not have predefined attribute, only be an anchor position (anchor), therefrom derive all other attributes, and interknit (jointly deriving from single attribute type) by the attribute type of its all derivation. The Extension type attribute defines this expansion and has expanded which project, and definition sign that an expansion and another project are distinguished, because a project can have a plurality of expansions.

ItemFolder (project folder) is the subtype of Item item types, except the attribute of inheriting from Item, it characterizes the relation that is used for being established to its member (if any), although Identitykey (identity keyword) and Property (attribute) all are the subtype of PropertyBase. CategoryRef (catalogue is quoted) and then be the subtype of IdentityKey.

B) core schema

The various embodiment of storage platform of the present invention also are included as core (Core) pattern that top layer item types structure provides conceptual framework. Fig. 8 A is the block diagram that the project in the core schema is shown, and Fig. 8 B is the block diagram that attribute type in the core schema is shown. The function that is similar to core schema with the file of different extension name (* .com, * .exe, * .bat, * .sys etc.) and the differentiation of in based on file and file system folder, making between other criterion. In project-based hardware/software interface system, core schema has defined one group of core project type, their directly (by item types) or indirectly (by project subtype) all items feature is changed into project-based hardware/software interface system understanding and can be with one or more core schema item types predetermined or the direct processing of predictable mode. Predetermined item types has reflected the most frequently used project in project-based hardware/software interface system, and the therefore project-based hardware by understanding these predetermined item types that comprise core schema/software interface system acquisition validity rank.

In certain embodiments, core schema can not be expanded, and, does not have the directly item types subclassification from basic schema of other type that is, unless as the specific predetermined item types of deriving of the part of core schema. By forbidding the expansion (that is, by forbidding adding new project to core schema) to core schema, the use of storage platform trustship core schema item types is because each follow-up item types must be the subtype of core schema item types. This structure allows to have the flexibility of resonable degree when the other item types of definition when maintenance has the benefit of one group of predetermined core project type.

With reference to figure 8A, to various embodiment of the present invention, can be comprised following one or more by the specific project type of core schema support:

Category (classification): the effective classification of sports representative in project-based hardware/software interface system of this project type (and the subtype that therefrom derives).

Commodity (article): as the project of the identified things of value.

Device (equipment): the project with logical construction of support information disposal ability.

Document (document): have and to be explained and the project of opposite content by explaining corresponding to the application program of Doctype by project-based hardware/software interface system.

Event (event): the project of event occurs in some in the record environment.

Location (position): the project in represents physical position (such as the geographical position).

Message (message): the project of communication between two or more main bodys (below definition).

Principal (main body): have except ItemId at least one and certainly can verify the identity project of (such as, the sign of individual, tissue, group, family, author, service etc.).

Statement (statement): have the project about the customizing messages of environment, include but not limited to: policy, reservation, voucher etc.

Similarly with reference to figure 8B, can be comprised following one or more by the particular community type of core schema support:

Certificate (certificate) (the basic PropertyBase type from basic schema derives)

PrincipalIdentityKey (subject identity keyword) (the IdentityKey type from basic schema derives)

PostalAddress (postal address) (the Property type derives from basic schema)

RichText (rich text) (the Property type derives from basic schema)

EAddress (Email geology) (the Property type derives from basic schema)

IdentitySecnrityPackage (identity rescue bag) (the Relationship type derives from basic schema)

RoleOccupancy (resident role) (the Relationship type derives from basic schema)

BasicPresence (basis exists) (the Relationship type derives from basic schema) these projects and attribute further describe by the separately attribute of listing in Fig. 8 A and Fig. 8 B.

5. concern

Relation is binary crelation, and one of them project is designated as the source, and another is designated as target. Source item order and destination item interrelate by relation. The source item order is generally controlled the life cycle of relation. That is, deleted when the source item order, the relation between the project is also deleted.

Relation is classified into: comprise (Containment) and quote (Reference) relation. The life cycle of inclusion relation control destination item, and the relation of quoting does not provide any life cycle management semantic. Figure 12 illustrates the mode of relation classification.

Inclusion relation is classified into again to be held (Holding) and embeds (Embedding) relation. When relation that all of a project are held is removed, this project is deleted. Hold and concern by reference counter mechanism control target. The relation that embeds can be to compound project modeling, and can be counted as the exclusive relation of holding. A project can be one or more related targets of holding; But a project can only be a target that embeds relation. Project as the target that embeds relation can not be that the target of relation is held or embedded to arbitrary other.

The relation of quoting is not controlled the life cycle of destination item. They can be that pendulous-destination item can not exist. Any place (that is, comprising the teledata storage) modeling that the relation of quoting can be used at overall entry name word space is quoted project.

The project that obtains does not obtain certain relation automatically, and application program must be asked the relation of project clearly. In addition, revise relation and do not revise source or destination item; Similarly, add relation and do not affect source/destination item.

A) relation statement

The following element definition of explicit relationship type;

In Name (name) attribute, specify the relation name

One of following relationship type: hold, embed, quote. This appointment in Type (type) attribute.

The source and target end points. Each end points is specified name and the type of institute's REFER object.

The source endpoint field generally is ItemID (item id) type (without proper notice), and must quote the project in storing with the same data of relationship example.

To holding and embedding relation, the target end-points field must be ItemIDReference (item id is quoted) type, and it must quote the project in identical storage with relationship example. To quoting relation, the target end points can be any ItemReference (project is quoted) type, and can quote the project in other storage platform data storage.

Can optionally state one or more fields of scalar or PropertyBase (attribute basis) type. These fields can comprise the data that are associated with this relation.

Relationship example is stored in the holotopy table.

Each relationship example is uniquely by combination (source ItemID, relations I D) sign. All are derived from the relation of given project, and relations I D is unique in given source ItemID, and no matter their type.

The source item order is the owner of relation. And the life cycle that the project control that is designated as the owner concerns, relation itself is separated with the project relevant with them. Storage platform API 322 is provided for representing the mechanism of the relation that is associated with project.

Here be the example of a relation statement.

<Relationship Name＝″Employment″BaseType＝″Reference″>

       <Source Name＝″Employee″ItemType＝″Contact.Person″/>

       <Target Name＝″Employer″ItemType＝″Contact.Organization″

           ReferenceType＝″ItemIDReference″/>

       <Property Name＝″StartDate″Type＝″the storage

       platformTypes.DateTime″/>

       <Property Name＝″EndDate″Type＝″the storage

       platformTypes.DateTime″/>

       <Property Name＝″Office″Type＝″the storage

       platformTypes.DateTime″/>

</Relationship>

This is the example of quoting relation. If the individual event of being quoted by the source does not exist, then can not create this relation. If this individual event is deleted, the relationship example between individuals and organizations is also deleted. If yet organize project deleted, concern not deletedly, and it is pendulous.

B) hold relation

The life cycle management that the relation of holding is used for the based target project comes the reference count modeling.

Project can be for the source endpoint to zero or a plurality of relations of project. The project that is not the embedding project can be the destination item of holding in the relation one or more.

Target endpoint reference type must be ItemIDReference, and it must quote the project in the storage identical with relationship example.

The relation of holding is implemented the life cycle management of target end points. Hold relationship example and be atomic operation as the establishment of the project of target. Can create the hold relationship example of other of same project as target. Hold relationship example when deleted when having last as the target end points of given project, this destination item is also deleted.

The type of the end points project of appointment is generally forced when the example of this relation of establishment in the relation statement. The type of end points project can not change after relation is set up.

Hold to close in the name space that ties up to the formation project and play key effect. They comprise " Name (name) " attribute, and its objective definition project is with respect to the source item destination name. To all relations of holding that is derived from given project, relative name is unique. Begin to form the full name of this project to the orderly class table of the relative name of given project from root Element.

The relation of holding forms a directed acyclic graph (DAG). Hold when concerning in establishment, system guarantees not produce the loop, thereby the name space of guaranteeing project forms DAG.

Although hold the life cycle of relation control destination item, it does not control the uniformity of the operation of target end points project. Destination item is independent of by holding in operation and concerns the project that has it. As hold copy, movement, backup and other operation on the project in related source do not affect as homonymous target project-for example, backup file folder project does not automatically back up all items in this document folder (target in FolderMember (file member) relation).

The below holds related example:

       <Relationship Name＝″FolderMembers″BaseType＝″Holding”>

              <Source Name＝″Folder″ItemType＝″Base.Folder″/>

              <Target Name＝″Item″ItemType＝″Base.Item″

                  ReferenceType＝″ItemIDReference″/>

       </Relationship>

The FolderMember relation makes the concept of file become the generic set of project.

C) embed relation

The relation that embeds is with the conceptual modelling of the exclusive control of the life cycle of destination item. They allow the concept of complex item.

Embed relationship example and be atomic operation as the establishment of the project of target. A project can be the source of zero or a plurality of embedding relation. Yet a project can be one and only be a target that embeds relation. Project as the target that embeds relation can not be to hold related target.

Target endpoint reference type must be ItemIDReference, and it must quote the project in identical data storage with relationship example.

The type of the end points project of appointment is generally forced when the example of this relation of establishment in the relation statement. The type of end points can not change after relation is set up.

Embed the operational consistency of this target end points of relation control. For example, the operation of serialization project can comprise all the embedding relations that all are derived from this project and all its targets that serialize; The project that copies also copies all its embedding projects.

The below is the example statement:

<Relationship Name＝″ArchiveMembers″BaseType＝″Embedding”>

             <Source Name＝″Archive″ItemType＝″Zip.Archive″/>

             <Target Name＝″Member″ItemType＝″Base.Item″

                 ReferenceType＝″ItemIDReference″/>

             <Property Name＝″ZipSize″Type＝″the storage

             platformTypes.bigint″/>

             <Property Name＝″SizeReduction″Type＝″the storage

             platformTypes.float″/>

</Relationship>

D) quote relation

The relation of quoting is not controlled the life cycle of the project that it quotes. Especially, quote the existence that relation does not guarantee target, do not guarantee that also the type of target is as appointment in the relation statement. This means that the relation of quoting can be pendulous. And the relation of quoting can be quoted the project in other data storage. The relation of quoting can be regarded the concept that is similar to the link on the webpage as.

The below is the example of quoting the relation explanation:

      <Relationship Name＝″DocumentAuthor″BaseType＝″Reference″>

             <Sourc ItemType＝″Document″

             ItemType＝″Base.Document″/>

             <Target ItemType＝″Author″ItemType＝″Base.Author″

                 ReferenceType＝″ItemIDReference″/>

             <Property Type＝″Role″Type＝″Core.CategoryRef/>

             <Property Type＝″DisplayName″Type＝″the storage

             platformTypes.nvarchar(256)″/>

      </Relationship>

End points in target allows any reference type. The project that relation is quoted in participation can be any item types.

The relation of quoting is used for the most of non-life cycle management relationship modeling between the project. Because do not force the existence of target, the relation quoted is convenient to loosely-coupled relationship modeling. The relation of quoting can be used for being included in the destination item in the storage on other computer in other storage.

E) Rule and constraint

Following ancillary rules and constraint are applied to relation:

A project must be the target of (only embeds relation) or (one or more relation of holding). An exception is root Element. A project can be zero or a plurality of target of quoting relation.

Concern that as embedding the project of target can not be to hold related source. It can be the source of quoting relation.

If a project then can not be to hold related source from the file upgrading. It can be the source that embeds relation and quote relation.

Project from the file upgrading can not be the target that embeds relation.

F) ordering of relation

In at least one embodiment, the ordering of storage platform support relation of the present invention. Finish ordering by the attribute of " Order (ordering) " by name in the fundamental relation definition. In the Order field without unique constraints. Do not guarantee the order with the relation of same " Order " property value, yet guarantee that they can sort after the relation of band lower " Order " value and before the relation of being with higher " Order " field value.

Application program is by obtaining giving tacit consent to the relation of order upper ordering of combination (SourceItem ID, RelationshipID, Order). All relationship example that are derived from given project are ranked into single set, and no matter the type that in set, concerns. Yet this assurance, all relations of given type (such as, FolderMembers (file member)) are ordering subsets of the set of relationship of given project.

Realize the operation of the ordering of one group of support relation for the treatment of the data storage API 312 of relation. Introduce following term and help to explain those operations:

RelFirst is with first relation of order value OrdFirst in the ordered set;

RelLast is last relation of ordered set crossed belt order value OrdLast;

RelX is with the given relation of order value OrdX in the set;

RelPrev is close to the band of the RelX relation less than the order value OrdPrev of OrdX in the set; And

RelNext is close to the band of the RelX relation greater than the order value OrdNext of OrdX in the set.

Operation includes but not limited to:

InsertBeforeFirst (SourceItemID, Relationship) inserts relation as first relation in the set. The value of " Order " attribute of new relation can be less than OrdFirst.

InsertAfterLast (SourceItemID, Relationship) inserts relation as last relation in the set. The value of " Order " attribute of new relation can be greater than OrdLast.

InsertAt (SourceItemID, ord, Relationship) inserts with the relation to the value of " Order " attribute appointment.

InsertBefore (SourceItemID, ord, Relationship) inserted this relation before with the relation of given order value. New relation can be assigned with " Order " value, and it but does not comprise this two values between OrdPrev and ord.

InsertAfter (SourceItemID, ord, Relationship) inserts this relation after the relation with given order value. New relation can be assigned with " Order " value, and it but does not comprise this two values between ord and OrdNext.

MoveBefore (SourceItemID, ord, Relationship) will move to the relation of given relations I D band and specify before the relation of " Order " value. Relation can be assigned with new " Order " value, and it but does not comprise this two values between OrdPrev and ord.

MoveAfter (SourceItemID, ord, Relationship) will move to the relation of given relations I D band and specify after the relation of " Order " value. This relation can be assigned with new order value, and it but does not comprise this two values between ord and OrdNext.

Arrive such as prerequisite, each project must be the member of project folder. According to relation, each project must accompany a relation with an item file. In some embodiment of the present invention, some relation is represented by the relation that exists between all projects.

Such as the realization to various embodiments of the present invention, relation provides an oriented binary crelation, and it extends to another project (target) by a project (source). Therefore relation is had by source item order (extending its project), if the source is removed then that relation is removed (deleted such as relation when the source item order is deleted). In addition in some cases, relation can be shared the ownership of (owning together) destination item, and such ownership only can be reflected in IsOwned (by the having) attribute (or its equivalent attribute) of relation (such as Fig. 7 to shown in the attribute of a relation type). In these embodiments, create new IsOwned relation and automatically increase progressively reference count on this target, and delete can successively decrease the reference count on this destination item of such relation. To these specific embodiments, if project has the reference count greater than 0, then exist, if item count reaches 0 automatically deletion. Again, project folder is the project with one group of relation of (maybe can have) and other project, and these other projects comprise the membership qualification of project folder. Other actual realization of relation is possible, and conceives to realize function described herein by the present invention.

No matter actual realization how, relation is the selectable connection from an object to another object. A project belongs to an above project folder and one or more classification, no matter and these projects, file and classification that to be publicly-owned or privately owned ability be is determined by the meaning that gives existing in the project-based structure (or shortage). These logical relations are to distribute to the meaning of one group of relation, no matter and the physics realization that it is used for realizing function described here specially how. Logical relation is set up (or opposite) between project and file or classification, because each of project folder and classification is the project of particular type in essence. Therefore, can be as other project project folder and classification are worked (copy, add in the email message, embed document etc., and unrestricted), and project folder can use identical mechanism serialization and de-serialization (import and derive) with classification as other project. (for example in XML, all items can have serialized form, and these lattice are applied to project folder, classification and project comparably).

The above-mentioned relation of the relation between representative project and the project folder thereof logically can extend to project folder, extend to project or both from project folder from project. The relation that extends to project folder from a project in logic shows that this project folder is publicly-owned for this project, and shares its membership qualification information with this project; On the contrary, the logical relation that lacks from the project to the project folder shows that this project folder is privately owned to this project, and does not share its membership qualification information with this project. Similarly, the relation that extends to project from project folder in logic shows that this project is publicly-owned, and can share with this project folder, shows that this project is privately owned and can not shares and lack the logical relation that extends to project from project folder. Therefore, when deriving project folder to other system, it is the project of " publicly-owned ", it is shared in new environment, and when its project folder of project search is sought other sharable project, it is the project folder of " publicly-owned ", and it provides information about shared with the project that belongs to it to this project.

Fig. 9 is the block diagram that interconnecting relation between project folder (itself also is project), its member's project and project folder and the member's project thereof is shown. Project folder 900 has a plurality of projects 902,904 and 906 as its member. Project folder 900 have from the itself to the project 902 concern 912, it shows that project 902 is publicly-owned, and can with project folder 900, its member 904 and 906 and any other project folder, classification or the project (not shown) of any accessible items file 900 share. Yet it doesn't matter from project 902 to project folder project 900, and this shows that 900 pairs of projects 902 of project folder are privately owned, and do not share its membership qualification information with project 902. On the other hand, project 904 really have from the itself to the project folder 900 concern 924, this shows that project folder 900 is publicly-owned, and shares its membership qualification information with project 904. Yet 904 the relation from project folder 900 to project not, this shows that project 904 is privately owned, and not with project folder 900, its other member 902,906, and any other project folder, classification or the project (not shown) of accessible items file 900 share. Opposite with its relation to project 902 and 904 (or not having these relations), project folder 900 have from itself to project 906 concern 916, and project 906 have get back to project folder 900 concern 926, show that together project 906 is publicly-owned, and can to file 900, its member 902 and 904 and any other project folder, classification or the project (not shown) of accessible items file 900 share, and project folder 900 is publicly-owned, and shares its membership qualification information with project 906.

Such as front discussion, the project in project folder does not need to share concomitant, because project folder is not by " description ". On the other hand, classification is by the common common point of all its member's projects is described. Therefore, the membership qualification of classification is limited to the project with described common point inherently, and in certain embodiments, all items that satisfies the description of classification automatically becomes such other member. Therefore, although project folder allows to represent unessential type structure by its membership qualification that classification allows membership qualification based on the common point of definition.

Certainly, it is logic in essence that classification is described, thereby classification can be described by any logical expressions of type, attribute and/or value. For example, can be its membership qualification to the logical expressions of a classification, have one of two attributes or both projects to comprise. If these attributes that classification is described are " A " and " B ", then such other membership qualification can comprise have attribute A and do not have B project, have attribute B and the project that do not have the project of A and have attribute A and B concurrently. Describe the logical expressions of attribute by logical operator " OR (or) ", wherein describing member's group by classification is the project with attribute A OR B. As understood by those skilled in the art, also can use similar logical operator (including but not limited to independent " AND (with) " " XOR (XOR) " and " NOT (non-) " or its combination) to describe classification.

Although between project folder (not describing) and classification (describing), have any different, but in many embodiment of the present invention, the classification relation that arrives in principle project reaches the above same method in the face of project folder and project of the project relationship that arrives classification and discloses.

Figure 10 is the block diagram that the interconnecting relation between a classification (itself also being project), its member's project, classification and the member's project thereof is shown. Classification 1000 has a plurality of projects 1002,1004 and 1006 as the member, and all these shares certain combination of common attribute, value and the Class1 008 (concomitant description 1008 ') described by classification 1000. Classification 1000 has from itself to project 1002 relation, it shows that project 1002 is publicly-owned, and can with classification 1000, its member 1004 and 1006 and any other classification, project folder or the project (not shown) of addressable classification 1000 share. Yet, 1000 the relation from project 1002 to classification not, this shows that 1000 pairs of projects 1002 of classification are privately owned, and does not share the membership qualification information with project 1002. On the other hand, project 1004 really have from itself to classification 1000 concern 1024, this shows that classification 1000 is publicly-owned, and shares its membership qualification information with project 1004. Yet, there is not the relation that extends to project 1004 from classification 1000, this shows that project 1004 is privately owned, and can not with classification 1000, its other member 1002 and 1006 and any other classification, project folder or the project (not shown) of addressable classification 1000 share. Opposite with the relation (or not having this relation) of it and project 1002 and 1004, classification 1000 have from itself to project 1006 concern 1016, and what project 1006 had classification of getting back to 1000 concerns 1026, this shows that together project 1006 is publicly-owned, and can with classification 1000, its program member 1002 and 1004 and any other classification, project folder or the project (not shown) of addressable classification 1000 share, and classification 1000 is publicly-owned, and shares its membership qualification information with project 1006.

At last, because classification and project folder itself are projects, and project can cross correlation, classification can be related to project folder, vice versa, and in some other embodiment, classification, project folder and project can be related to respectively other classification, project folder and project. Yet in various embodiments, item file clamping structure and/or classification structure forbid comprising the loop in that hardware/software interface is system-level. When project folder and classification structure are similar to digraph, forbid that the embodiment in loop is similar to directed acyclic graph (DAG), according to the mathematical definition in graph theory field, DAG is the digraph that does not wherein have the path to begin on same summit and stop.

6. extensibility

As mentioned above, this storage platform aims to provide originate mode group 340. Yet at least in certain embodiments, this storage platform allows also to comprise that the clients such as stand alone software retail trader (ISV) create new pattern 344 (being new project and nested element type). The item types that this section is passed expansion definition in originate mode group 340 through discussion and nested element type (or being called for short " element " type) are conceived to create the mechanism of this pattern.

Preferably, the following constraint of expansion of the initial set of project and nested element type:

Allow ISV to introduce new item types, i.e. subtype Base.Item;

Allow ISV to introduce new nested element type, i.e. subtype Base.NestedElement;

Allow ISV to introduce new expansion, i.e. subtype Base.NestedElement; But

ISV can not subclassification by any type of originate mode group 340 definition of storage platform (project, embed element or expansion type).

The item types or the embedding element type that define owing to the originate mode group by storage platform may inaccurately mate the needs of ISV application program, must allow ISV to customize the type. This has just considered the concept of expansion. Expansion is strongly-typed example, still (a) they can not independently exist, and (b) they must be attached to project or nested element.

Except solving the needs to the pattern extensibility, expansion also is intended to solve " many classification " problem. In certain embodiments because storage platform may not supported many inheritances or overlapping subtype, application program can use the expansion as the overlapping type instance of modelling (as document be legal documents be again security document) method.

A) project expansion

For the extensibility of project is provided, data model also defines the abstract type of Base.Extension by name. This is the root type of the hierarchy of expansion type. Application program can subclassification Base.Extension, to create specific expansion type.

In basic schema as the Base.Extension type of giving a definition:

    <Type Name＝″Base.Extension″IsAbstract＝″True″>

       <Propety Name＝″ItemID″

               Type＝″the storage platformTypes.uniqueidentified″

               Nullable＝″false″

               MultiValued＝″false″/>

       <Property Name＝″ExtensionID″

               Type＝″the storage platformTypes.uniqueidentified″

                  Nullable＝″false″

                  MultiValued＝″false″/>

    </Type>

The ItemID field comprises the ItemID of the project related with this expansion. Project with this ItemID must exist. If the project with given ItemID does not exist, then can not create expansion. When project deleted, deleted with all expansions of same ItemID. Two tuples (ItemID, ExtensionID) have identified the expansion example uniquely.

The structure of expansion type is similar to the structure of item types:

Expansion type has field;

Field can be primitive or nested element type; And

Expansion type can be by subclassification.

Following restriction is applied to expansion type

Expansion can not be the source and target of relation;

The expansion type example can not be independent of project and exist; And

Expansion type can not be as the field type in the storage platform type definition

Not constraint of type to expansion that can be related with given item types. Any expansion type allows any item types of expansion. When a plurality of expansion examples are affixed to a project, they are independent of one another in structure and behavior.

The expansion example is stored and accesses from project. All expansion type examples can be from overall extended view access. Can form an effectively inquiry, it will return all examples of the expansion of given type, and no matter the project of their related what types. The programming model that storage platform API provides and can store, retrieves and the modification project is expanded.

Expansion type comes the type of subclassification with the single succession model of storage platform. Derive the new expansion type of establishment from an expansion type. The structure of an expansion or behavior can not cover or structure or the behavior of alternative item types hierarchy. Be similar to item types, the expansion type example can directly be accessed by the view related with this expansion type. The ItemID of expansion shows which project they belong to, and can be used for from overall situation project object corresponding to eye diagram retrieval. Be the purpose of operational consistency, expansion is considered to be the part of project. Other operation commonly used of copy/mobile, backup/restoration and storage platform definition can operate in the expansion as the part of project.

Consider following example. In the Windows type group, define Contact (contact person) type.

    <Type Name＝″Contact″BaseType＝″Base.Item″>

       <Property Name＝″Name″

                  Type＝″String″

                  Nullable＝″false″

                  MultiValued＝″false″/>

       <Property Name＝″Address″

                  Type＝″Address″

                  Nullable＝″true″

                  MultiValued＝″false″/>

    </Type>

CRM (customer relation management) application developer is liked the expansion of CRM application program is appended to the contact person who is stored in the storage platform. The application developer definition comprises the CRM/ expansion of the treatable additional data structure of application program.

  <Type Name＝″CRMExtension″BaseType＝″Base.Extension″>

     <Property Name＝″CustomerID″

                   Type＝″String″

                Nullable＝″false″

                MultiValued＝″false″/>

    …

  </Type>

The HR application developer wishes also additional data to be appended to the contact person. These data are independent of the CRM application data. Application developer also can create-expand

    <Type Name＝″HRExtension″EBaseType＝″Base.Extension″>

       <Property Name＝″EmployeeID″

                  Type＝″String″

                  Nullable＝″false″

                  MultiValued＝″false″/>

      …

    </Type>

CRMExtension and HRExtension can append to two independent expansions of contacts purpose. They can create and access independently of one another.

In above-mentioned example, the field of CRMExtension type and method can not cover field and the method for contact person's hierarchy. The example that it should be noted that the CRMExtension type can be affixed to the item types that is different from the contact person.

When the searching linkman project, automatically do not retrieve its project expansion. Given contact item can visit its relevant project expansion with the expansion of the same ItemID of searching belt by inquiring about overall extended view.

Can visit CRMExtension expansions all in the system by CRMExtension type view, no matter and what project they belong to. Same project id is shared in all items expansion of a project. In above-mentioned example, contact item's example and additional CRMExtension and HRExtension example are shared same ItemID.

Following table has been summed up similitude and the difference between Item (project), Extension (expansion) and NestedElement (nested element) type:

Item, ItemExtension and NestedElement

	Item	ItemExtension	NestedElement
				Item id storing queries/search inquiry/hunting zone relation semanteme is related with project	Hierarchy with the project id project of oneself be stored in its oneself table all examples that can the queried for items table can search for an item types can have with the relation of project can by hold embed relevant with other project with soft relation	The project id project expansion hierarchy of sharing project be stored in its own table all examples that can the queried for items expansion table can search for a project expansion type and project expand irrelevant usually can only be next relevant by expanding. It is semantic that the expansion semantic category is similar to the embedding project	Do not have its oneself project id. Nested element be the part of project be stored in usually can only in comprising the context of project, inquire about in the project usually can only in the nested element type example of single (comprising) project, search for nested element irrelevant come by field relevant with project. Nested element is the part of project

B) expansion NestedElement type

Nested element type need not be identical with item types mechanism expansion. The expansion of nested element mechanism storage and the access identical with nested element type field.

Data model has defined the root of the nested element type of Element by name (element).

          <Type Name＝″Element″

                IsAbstract＝″True″>

                <Property Name＝″ElementID″

                       Type＝″the storage platformTypes.uniqueidentifier″

                       Nullable＝″false″

                       MultiValued＝″false″/>

          </Type>

The NestedElement type is inherited from this type. The NestedElement element type defines-field in addition, and it is the multicomponent element.

          <Type Name＝″NestedElement″BaseType＝″Base.Element″

             IsAbstract＝″True″>

                 <Property Name＝″Extensions″

                        Type＝″Base.Element″

                        Nullable＝″false″

                        MultiValued＝″true″/>

          </Type>

NestedElement expands below, and the aspect is different from the project expansion:

Nested element expansion is not expansion type. They do not belong to the expansion type hierarchy take the Base.Extension type as root.

The expansion of nested element is stored with other field of this project, and be not the overall situation addressable-can not form the inquiry of all examples of retrieving given expansion type.

Other nested element (or project) is stored these expansions as Cun Chu. Resemble other nested group, the NestedElement expansion is stored among the UDT. They can visit by Extension (expansion) field of nested element type.

Be used for the set interface of access multi-valued attribute also for access and iteration on the Extended-type group.

Following table is summed up and relatively Item expansion and NestedElement expansion.

Item expansion and NestedElement expansion

	The project expansion	The NestedElement expansion
			Storage	Project expansion hierarchy deposits its table in	Resemble and store the nested element

Inquiry/search inquiry/hunting zone programmability behavior relation semantic item ID

Can queried for items expansion table all examples that can inquire about a project expansion type need special inquiry on special expansion API and the expansion table can correlation behavior and project expand the project id of irrelevant shared project

Usually can only in comprising the context of project, inquire about and usually can only in the nested element type example of single (comprising) project, search for the NestedElement extension class like any other many-valued field of nested element; Use normal nested element type API do not allow behavior (?) expand the irrelevant project id that does not have it with NestedElement. The NestedElement expansion is the part of project

F. database engine

As mentioned above, data are stored on the database engine and realize. In the present embodiment, database engine comprise such as Microsoft SQL Server engine etc. realize the SQL query language, with the relational database engine of object relationship expansion. This section is described the data model of data storage realization to the mapping of relational storage according to present embodiment, and the information of being used by the client computer of storage platform is provided at logic API. Yet be appreciated that when adopting different database engines and can adopt different mappings. Really, also can realize in other types of database, such as object-oriented and XML database the storage platform conceptual data model except realizing at the relevant database engine.

Object-oriented (OO) Database Systems are that programming language object (such as C++, Java) provides continuation and affairs. The storage platform concept of " project " can be mapped to the object in the Object-Oriented Systems well, although the set that embeds must be added to object. Similar inheritance and other storage platform type concepts such as nested element type also are mapped to the system of object-oriented type. Object-Oriented Systems is support target identity usually; Therefore, the project identity can be mapped to object identity. The behavior of project (operation) is mapped to object method well. Yet the common inorganizable ability of OO system is also very poor aspect search. And OO system does not provide the support to destructuring and semi-structured data. For supporting complete storage platform data model described herein, resemble the concepts such as relation, file and expansion and need to add object data model to. In addition, need to realize as upgrading, synchronously, the mechanism such as notice and security.

Be similar to OO system, support the system of inheriting type based on single based on the XML database of XSD (XML mode-definition). Item types of the present invention system can be mapped to the XSD Type model. XSD does not provide the support to behavior yet. The behavior of the necessary addition item of the XSD of project. The XML database is processed single XSD document and inorganizable and widen search capability. As object-oriented database, for supporting data model described herein, need to be incorporated into this XML database such as other concepts such as relation and files; And need to realize as synchronously, the mechanism such as notice and security.

About following trifle, provide a small amount of diagram so that general information illustration: Figure 13 is the diagram that notice mechanism is shown. Figure 14 illustrates the diagram that two affairs are all inserted new record the example of same B tree. Figure 15 illustrates data and changes testing process. Figure 16 illustrates exemplary directory tree. The existing file double-layered quilt that Figure 17 illustrates wherein based on the file system of catalogue moves in the storage of storage platform data.

1. use the data storage of UDT to realize

In the present embodiment, the relevant database engine 3 14 that comprises in one embodiment Microsoft SQL Server engine is supported built-in scalar type. Built-in scalar type is " primary (native) " and " simply ". They are that primary meaning is, the user can not define themselves type; They are that simple meaning is, the user can not encapsulate complicated structure. User-defined type (hereinafter referred to as UDT) provides a kind of mechanism for surpassing or surmount the type extensibility of primary scalar type system by making the user come the expansion type system by defining complicated structured type. In case defined by the user, UDT can be for the type system that can use built-in scalar type Anywhere.

Press one aspect of the present invention, the storage platform pattern is mapped to the UDT class in the database engine storage. The data stored items is mapped to the UDT class that derives from the Base.Item type. Be similar to project, expansion also can be mapped to the UDT class and use and inherit. The root expansion type is Base.Extension, derives all expansion types from it.

UDT is the CLR class, and it has state (being data field) and behavior (being routine). Use any managed language (c#, VB.NET etc.) definition UDT. UDT method and operator can be called by the example for the type in T-SQL. UDT can be: in the row in the type, T-SQL of row the type of the parameter of routine or in T-SQL type of variables.

The storage platform pattern to being mapped in of UDT class high-level upper be direct fully. Generally speaking, the storage platform pattern is mapped to the CLR name space. The storage platform type is mapped to the CLR class. The succession mirror image of CLR class the succession of storage platform type, and the storage platform attribute is mapped to the CLR generic attribute.

2. project mapping

Can be searched for globally in order to wish project, and in the relational data of present embodiment, support to inherit and the type substitutability, be in the single table with the row of type B ase.Item, to store all items to a kind of possible realization of the project storage in the database storage. The type of service substitutability can be stored all types of projects, and can come filtered search by the subtype of the item types of the operator of " is of (type) " of using Yukon.

Yet, owing to involve the overhead that is associated with this method in the present embodiment, by top type projects are divided, so that the project of each type " family " stores in the independent table. In this partition mode, each is directly created a table from the item types that Base.Item inherits. As mentioned above, the substitutability of these type type of service is stored in the suitable type family table below the succession. Only have from the first order succession of Base.Item and ad hoc processed.

Use one " shade " but the copy of the overall situation search attribute of table storage all items. This table can be safeguarded by the Update () method of storage platform API, make the change of all data by the method. Do not resemble type family table, this overall repertory only comprises the top scalar attribute of this project, rather than full UDT project object. Overall situation repertory allows to navigate to the project object that is stored in the type family table by representing ItemID and TypeID (type I D). Project in the common uniquely identification data storage of ItemID. Can use the metadata of not giving description here that TypeID is mapped to type name and the view that comprises this project. Because seeking project by its ItemID all is operation commonly used in the context of overall repertory and other situation, the therefore given ItemId of project provides GetItem () function to come the search terms object.

For ease of access and the details of hiding as much as possible realization, all inquiries of project can be carried out the view that makes up on the table that impinges upon above-mentioned project. Particularly, to the family table establishment view of each item types for adequate types. These type views can be selected the type that is associated, comprise all items of subtype. For simplicity, except the UDT object, view can represent row to all TLDs that comprise the type of inheriting field.

3. expansion mapping

Expansion is very similar to project, and has some identical requirement. As support adoptive another root type, many same considerations and relatively compromise during expansion is stored. For this reason, to the mapping of the similar type of expanded application family, rather than single table method. Certainly, in other embodiments, can use single table method. In the present embodiment, expansion by ItemID only with an item association, and be included in ExtensionID unique in the context of project. As project, given ItemID and the right identity of ExtensionID of comprising can provide a function to be used for the retrieval expansion. Be similar to the item types view, can create view to each expansion type.

4. nested element mapping

Nested element is can be embedded into project, expansion, relation or other nested element to form the type of dark nested structure. Be similar to project and expansion, nested element is realized as UDT, but they are stored in project and the expansion. Therefore, nested element does not surmount their project and the Storage Mapping of the mapping of extension container. In other words, in system, do not have directly to store the table of the example of NestedElement type, and be not specifically designed to the view of nested element.

5. object identity

Each entity in data model, namely each project, expansion and relation have unique key value. A project is identified uniquely by its ItemId. Expansion is identified uniquely by composite key (ItemId, ExtensionId). Relation is identified by composite key (ItemId, RelationId). ItemId, ExtensionId and RelationshipId all are GUID values.

6.SQL object naming

All objects that create in the data storage can be stored in from the SQL pattern name that storage platform pattern name derives. For example, storage platform basic schema (normal claim " basis ") can be created in the type in " [System.Storage] " SQL pattern, such as " [System.Storage] .Item ". The name that produces can be with the determiner prefixing to eliminate the conflict of name. Can use at suitable place exclamation mark (! ) as the decollator of each logical gate of name. The below's table has been summarized the name custom that is used for object in the data storage. Name custom with the modification of the example that is used for the visit data storage is listed each pattern element (project, expansion, relation and view).

Object	The name character modification	Describe	Example
				Major event order search view	Master！Item	The summary of project is provided in current project territory	[System.Storage].   [Master！Item]
The project search view of classifying type	ItemType	All properties data from project and any parent type are provided	[AcmeCorp.Doc].   [OfficeDoc]
				Main expanded search view	Master！Extension	Be provided at the summary of all expansions in the current project territory	[System.Storage].   [Master！Extension]

The expanded search view of classifying type	Extension！extensionType	Provide all properties data to expansion	[AcmeCorp.Doc].  [Extension！SlickyNote]
				The primary relation view	Master！Relationship	Be provided at related summary in the current project territory	[System.Storage].  [Master！Relationship]
Relational view	Relationship！relationship Name	The data that provide all to be associated with given relation	[AcmeCorp.Doc].  [Relationship！Authors  FromDocument]
				View	View！viewName	The Schema-based view definition provides row/type	[AcmeCorp.Doc].  [View！DocumentTitles]

7. row name

When shining upon arbitrary object model to storage, naming conflict might occur in the additional information owing to storing with application object. For avoiding naming conflict, the specific row of all non-types (not mapping directly to the row of the attribute of the name in the type declarations) underscore character (_) prefixing. In the present embodiment, underscore character (_) does not allow the beginning character as any identifier attribute. In addition, for being unified in the name between the storage of CLR and data, all properties of storage platform type or pattern element (relation etc.) should have the first character of capitalization.

8. search view

Provide view by storage platform, be used for the content of search storage. Provide the SQL view to each project and expansion type. In addition, provide view to support relation and view (by the data model definition). All SQL views and the bottom table in storage platform are read-only. The below uses the Update () method of storage platform API can store or change data more abundant description.

＜view-name 〉] access. BookSales] visit. Because the output format of view is self-defining (being determined by any inquiry that side who defines view provides) on the basis of each view, row Schema-based view definition is directly shone upon.

All SQL search views in the storage of storage platform data use the following ordering custom of row:

Logic " keyword " row such as the view result of ItemId, ElementId, RelationshipId etc.

Such as the metadata information about result type such as TypeId.

Change such as CreateVersion (establishment version), UpdateVersion (renewal version) etc. and follow the tracks of row

The row of type special use (attribute of the type of statement)

The view of type special use (family's view) also comprises the object row of returning an object value

The member of each type family can search for a series of eye diagrams, and each item types has a view in the data storage. Figure 28 is the diagram that the concept of project search view is shown.

A) project

Each project search view comprises delegation to each example of the project of particular type or its subtype. For example, the view of document can return the example of Document (document), LegalDocument (legal documents) and ReviewDocument (checking document). Given this example, as shown in Figure 29 generalities item eye diagram.

(1) major event order search view

Each example definition of storage platform data storage is called the special item view of major event eye diagram (Master Item View). This view provides the survey information about each project in the data storage. View provides row to each item types attribute, a row description entry purpose type wherein, and some row are used for providing changing to be followed the tracks of and synchronizing information. Item] " identify the major event eye diagram.

Row	Type	Describe
			ItemId	ItemId	The storage platform identity of this project
_TypeId	TypeId	The TypeId-of this project identify this project definite type and can be for retrieve information about type with the metadata classification
			_RootItemId	ItemId	Control first non-embedded elder generation's of this purpose life cycle ItemId
＜the overall situation changes follows the tracks of 〉	…	The overall situation changes trace information
			＜item attribute 〉	n/a	Each item types attribute there are row

(2) the project search view of classifying type

Each item types also has the search view. Be similar to the root Element view, this view also provides by the access of " _ Item " row to the project object. In data storages, use name [schemaName] .[itemTypeName] identify the project search view of each classifying type. [AcmeCorp.Dod] .[OfficeDoc for example].

Row	Type	Describe
			ItemId	ItemId	The storage platform identity of this project
＜type change is followed the tracks of 〉	…	The type change trace information
			＜father attribute 〉	＜attribute is special-purpose 〉	Each father's attribute there are row
＜item attribute 〉	＜attribute is special-purpose 〉	Each exclusive attribute to this type has row
			_Item	The CLR type of project	The type of the project of CLR object one statement

B) project expansion

All items expansion in the WinFs storage also can use the search view to visit.

(1) main expanded search view

Each example definition one of data storage is called the special extended view of main extended view (Master Extension View). This view provides the survey information about each expansion in the data storage. This view has row to each extended attribute, and wherein row are described the type of expansion, and some row are used for providing change to follow the tracks of and synchronizing information. Extension] " the main extended view of sign in the data storage.

Row	Type	Describe
			ItemId	ItemId	Expand therewith the storage platform identity of related project
ExtensionId	ExtensionId(GUID)	The id of this expansion example
			_TypeId	TypeId	The TypeId-of this expansion identifies the definite type of this expansion, and can be for the information of retrieving with the metadata classification about this expansion
＜the overall situation changes follows the tracks of 〉	…	The overall situation changes trace information
			＜extended attribute 〉	＜attribute is special-purpose 〉	Each expansion type attribute there are row

(2) the expanded search view of classifying type

Each expansion type also has the search view. Be similar to main extended view, this view also provides by _ Extension and is listed as the access to the project object. ExtensionTypeName] identify the expanded search view of each classifying type. OfficeDocExt].

Row	Type	Describe
			ItemId	ItemId	Expand therewith the storage platform identity of related project
ExtensionId	ExtensionId(GUID)	The Id of this expansion example
			＜type change is followed the tracks of 〉	…	The type change trace information
＜father attribute 〉	＜attribute is special-purpose 〉	Each father's attribute there are row
			＜extended attribute 〉	＜attribute is special-purpose 〉	Exclusive attribute to each this type has row
_Extension	The CLR type of expansion example	The type of the expansion of CLR object-statement

C) nested element

All nested elements are stored among project, expansion or the relationship example. Therefore, they can visit by inquiring about suitable project, expansion or relation search view.

D) relation

As above discuss, relation is formed on the elementary cell that links between projects in the storage of storage platform data.

(1) primary relation search view

Each data storage provides-the primary relation view. This view provides the information about all relationship example in the data storage. Relationship] " identify the primary relation view.

Row	Type	Describe
			ItemId	ItemId	The identity of source endpoint (ItemId)
RelationshipId	RelationshipId(GUID)	The id of this relationship example
			_RelTypeId	RelationshiPTypeId	The RelTypeId-of this relation identifies the type of this relationship example with the metadata classification
＜the overall situation changes follows the tracks of 〉	…	The overall situation changes trace information
			TargetItemReference	ItemReference	The identity of target end points
_Relationship	Relationship	Example to the Relationship object of this example

(2) relationship example search view

The relation of each statement also has the search view of all examples that return this particular kind of relationship. Be similar to the primary relation view, this view provides the row of name to each attribute of this relation data. RelationshipName] identify each relationship example search view. DocumentAuthor].

Row	Type	Describe
			ItemId	ItemId	The identity of source endpoint (ItemId)
RelationshipId	RelationshipId(GUID)	The id of this relationship example
			＜type change is followed the tracks of 〉	…	The type change trace information
TargetItemReference	ItemReference	The identity of target end points
			＜parent name 〉	ItemId	The name attribute of source endpoint identity (another name of ItemId)
＜destination name 〉	The class of ItemReference or derivation	The name attribute of target end points identity (another name of TargetItemReference and model (cast))
			＜attribute of a relation 〉	＜attribute is special-purpose 〉	Attribute to each contextual definition has row
_Relationship	The CLR type of relationship example	The type of CLR object-statement relation

e)

9. upgrade

All views are read-only in the storage of storage platform data. Be the new example of establishment data model element (project, expansion or relation), or upgrade existing example, must use ProcessOperation or the ProcessUpdategram method of storage platform API. The ProcessOperation method is the process of single storage, and it is the data definition storage of " operation " of action that intend to be carried out by the consumption refinement. The ProcessUpdategram method is the process of storage, and it takes to be called one group of orderly operation of " more new element (updategram) ", and the set of execution is intended in their common refinements.

Operational format is extendible, and is provided at the various operations on the pattern element. Some common operation comprises:

1. project operation:

A.CreateItem (creating a new project in the related context embedding or hold)

B.UpdateItem (upgrading an existing project)

2. relational operation:

A.CreateRelationship (related example is quoted or held in establishment)

B.UpdateRelationship (upgrading a relationship example)

C.DeleteRelationship (removing a relationship example)

3. extended operation

A.CreateExtension (add one and expand to existing project)

B.UpdateExtension (upgrading an existing expansion)

C.DeleteExtension (deletion one expansion)

10. change and follow the tracks of and gravestone

More discuss fully as following, provided to change by the data storage and follow the tracks of and the gravestone service. This section is provided at the general introduction of the change trace information that represents in the data storage

A) change tracking

Each the search view that is provided by the data storage comprises the row that change trace information be used to providing; Those row are public to all items, expansion and relational view. It is indirectly to provide by the search view that makes up view itself thereon that the storage platform pattern view that is defined clearly by the Model Design person does not automatically provide change trace information-this information.

Each element in the data storage can obtain changing trace information from two places: " master " element view and " classifying type " element view. Item] " and item eye diagram [AcmeCorp.Document] .[Document of classifying type] in obtain change trace information about the AcmeCorp.Document.Document item types.

(1) change in " master " search view is followed the tracks of

Change trace information in the main search view provide about the establishment of element and upgrade version information, about which synchronous partner create this element information, which synchronous partner to upgrade for the last time the information of this element and from each partner's the version number that creates and upgrade of being used for about. Identify partner's (the following describes) in the synchronized relation with partner's keyword. Type [System.Storge.Store] .ChangeTrackingInfo by name _ the single UDT object of ChangeTrackingInfo comprises all these information. Define styles in the System.Storage pattern. In all global search views of project, expansion and relation, can obtain _ ChangeTrackingInfo. The type definition of _ ChangeTrackingInfo is:＜Type Name=" ChangeTrackingInfo " BaseType=" Base.NestedElement "〉＜FieldProperty Name=" CreationLocalTS " Type=" SqlTypes.SqlInt64 " Nullable=" False "/＜FieldProperty Name=" CreatingPartnerKey " Type=" SqlTypes.SqlInt32 "

 Nullable＝″False″/>    <FieldProperty Name＝″CreatingPartnerTS″     Type＝″SqlTypes.SqlInt64″

 Nullable＝″False″/>    <FieldProperty Name＝″LastUpdateLocalTS″     Type＝″SqlTypes.SqlInt64″

 Nullable＝″False″/>    <FieldProperty Name＝″LastUpdatingPartnerKey″Type＝″SqlTypes.SqlInt32″

 Nullable＝″False″/>    <FieldProperty Name＝″LastUpdatingPartnerTS″ Type＝″SqlTypes.SqlInt64″

 Nullable＝″False″/>   </Type>

These attributes comprise following information:

Row	Describe
		_CreationLocalTS	The creation-time mark of local machine
_CreatingPartnerKey	Create the partner's of this entity PartnerKey. If entity is local the establishment, this is the PartnerKey of local machine
		_CreatingPartnerTS	Locate to create the time mark of the time of this entity the partner corresponding to _ CreatingPartnerKey
_LastUpdateLocalTS	Local zone time mark corresponding to update time of local machine
		_LastUpdatePartnerKey	The last PartnerKey that upgrades the partner of this entity. If finish this locality that is updated in for the last time to this entity, then this is the PartnerKey of local machine.
_LastUpdatePartnerTS	Locate to upgrade the time mark of the time of this entity the partner corresponding to _ LastUpdatingPartnerKey.

(2) change in " classifying type " search view is followed the tracks of

Except identical information with the global search view was provided, the search view of each classifying type provided the additional information that is recorded in the synchronous regime of each element in the synchronous topology.

Row	Type	Describe
			＜the overall situation changes follows the tracks of 〉	…	Change the information of following the tracks of from the overall situation
_ChangeUnitVersions	MultiSet＜change unit version 〉	The description of the version number of the change unit in the specific element
			_ElementSyncMetadata	ElementSyncMetadata	About an additional version independent elements data to the interested project in synchronous operation storehouse

_VersionSyncMetadata

VersionSyncMetadata

About an additional version special use metadata to the interested version in synchronous operation storehouse

B) gravestone

Data are stored as project, expansion and relation gravestone information are provided. The gravestone view provides in the place information about movable and gravestone entity (project, expansion and relation). Project and expansion gravestone view are not proposed the access to corresponding objects, and concern that the gravestone view provides the access to relationship object (relationship object is for empty in the situation of gravestone relation).

(1) project gravestone

Item] from system retrieval project gravestone.

Row	Type	Describe
			ItemId	ItemId	The identity of project
_TypeID	TypeId	The type of project
			＜item attribute 〉	…	Attribute to all items definition
_RootItemId	ItemId	The ItemId that comprises this first non-embedded project of purpose
			_ChangeTrackingInfo	The CLR example of ChangeTrackingInf o type	This purpose changes trace information
_IsDeleted	BIT	This is sign, the 0th, and campaign item, the 1st, gravestone project
			_DeletionWallclock	UTCDATETIME	Press deleted entry purpose partner's time on UTC wall clock date, if this project is movable, it is empty

(2) expansion gravestone

Extension] from system retrieval expansion gravestone. Expansion changes the trace information interpolation that provides for project the has been provided information of ExtensionId attribute.

Row	Type	Describe
			ItemId	ItemId	The identity that has the project of this expansion
ExtensionId	ExtensionId	The ExtensionId of this expansion
			_TypeID	TypeId	The type of this expansion

_ChangeTrackingInfo	The CLR example of ChangeTrackingInfo type	The change trace information of this expansion
			_IsDeleted	BIT	This is sign, the 0th, and campaign item, and 1 be gravestone expansion
_DeletionWallclock	UTCDATETIME	During UTC wall clock day by the partner who deletes this expansion. If this expansion is movable, it is empty

(3) concern gravestone

Relationship] concern gravestone from system retrieval. Concern the information that the gravestone info class is similar to be provided expansion. Yet, provide additional information at the target ItemRef of relationship example. In addition, go back the choice relation object.

Row	Type	Describe
			ItemId	ItemId	The identity (identity of the source endpoint of relation) that has the project of this relation
RelationshipId	RelationshipId	The RelationshipId of this relation
			_TypeID	TypeId	The type of relation
_ChangeTrackingInfo	The CLR example of ChangeTrackingInfo type	The change trace information of this relation
			_IsDeleted	BIT	This is sign, the 0th, and campaign item, and 1 be gravestone expansion
_DeletionWallclock	UTCDATETIME	Press the partner's of this relation of deletion time on UTC wall clock date. If this relation is movable, it is empty
			_Relationship	The CLR example of relation	This is the relationship object of activity relationship, and gravestone concerned that it is for empty
TargetItemReference	ItemReference	The identity of target end points

(4) gravestone is removed

For preventing that gravestone information from unrestrictedly increasing, the data storage provides gravestone to remove task. This task determines when can give up gravestone information. This task is calculated the boundary of local establishment the/renewal version, and blocks gravestone information by giving up all gravestone versions more early subsequently.

11. assistant API and function

Base map also provides some assistant's functions. Provide these functions to help the common operation on this data model.

A) function [System.Storage] .GetItem

// given ItemId returns a project object

Item Getltem(Itemld Itemld)

B) function [System.Storage] .GetExtension

// given ItemId and ExtensionId return an EXPANDING DISPLAY AREA

Extension GetExtension(Itemld Itemld，Extensionld Extensionld)

C) function [System.Storage] .GetRelationship

// given ItemId and RelationshipId return-relationship object

Relationship GetRelationship(Itemld Itemld，Relationshipld Relationshipld)

12. metadata

The metadata that has two classes in storage, to represent: example metadata (type of project etc.), and genre metadata.

A) pattern metadata

The conduct of pattern metadata is stored in the data storage from the example of the item types of meta schema.

B) example metadata

Application program use-case metadata is come the type of queried for items, and the expansion that is associated with project of searching. The ItemId of given project, application program can be inquired about the overall situation eye diagram, returning the type of this project, and is worth to inquire about the Meta.Type view to return the information about the type of the statement of this project with this. For example,

// given project example is returned metadata project object

SELECT m._Item AS metadataInfoObj

FROM[System.Storage].[Item]i INNER JOIN[Meta].[Type]m ON i._Typeld＝m.Itemld

WHERE i.Itemld＝@Itemld

G. security

Generally speaking, all objects that can protect arrange access rights with the access mask form shown in Figure 26. In this form, low 16 be used for the object special use access rights, follow 7 standard access authorities that are used for being applied to most of object types, high 4 are used to specify the generic access rights, and each object type is mapped to the authority of one group of standard and object special use with it. The ACCESS_SYSTEM_SECURITY position is corresponding to the authority of the SACL of access object.

In the access mask structure of Figure 26, the authority of project special use is placed on the special-purpose authority section of object (low 16). Because in the present embodiment, storage platform represents two groups of API:Win32 and storage platform API to keeper's security, for promoting the design of the special-purpose authority of storage platform object, must consider the authority of file system object special use.

The security model that is used for storage platform of the present invention has fully been described in relevant patent incorporated herein by reference. In this, Figure 27 (part a, b and c) draws the embodiment by security model, as the new equally safety zone of protection that opens from existing safety zone.

H. notify and change tracking

Press another aspect of the present invention, storage platform provides the notice ability that allows the application program tracking data to change. This feature is mainly for the application program that keeps the service logic on volatile state or the executing data change event. Application program is registered in the notice on project, project expansion and the project relationship. Submitting to data change notice to be transmitted asynchronously. Application program can be filtered notice by project, expansion and relationship type and action type.

By an embodiment, storage platform API 322 provides two class interfaces for notice. The first, the application program registration changes event by the simple data that the change to project, project expansion and project relationship triggers. The second, application program creates the group that " supervisory programme " object comes supervision project, project expansion and project Relations Among. After thrashing or system's off-line surpass the scheduled time, can preserve and again create the state of supervisory programme object. Single notice can reflect a plurality of renewals.

About finding in the additional detail of this function relevant patent can be formerly incorporated herein by reference.

I. synchronous

According to another aspect of the present invention, storage platform provides synchronous service 330, the Multi-instance (each has its data storage 302) that its (i) allows storage platform is according to one group of their partial content of regular and synchronized flexibly, and (ii) for the third party provides a foundation structure, to come the data storage of synchronous storage platform of the present invention with other data source that realizes proprietary protocol.

Storage platform occurs between one group of duplicate that participates in synchronously to storage platform. For example, with reference to figure 3, may want provides synchronous between another teledata storage 338 under the data storage 302 of storage platform 300 and another example control in storage platform (may operate on the different computer system). Whole membership qualifications of this group need not to be known at any given time for any given duplicate.

Different duplicate can be made change (that is side by side) independently. Synchronous procedure definition makes each duplicate know the change that other duplicate is made. This synchronizing capacity is many main (multi-master) inherently.

Synchronizing capacity of the present invention allows duplicate:

Determine which change another duplicate knows;

Request is about the information of the ignorant change of this duplicate;

Transmission is about the information of the ignorant change of another duplicate;

Determine when that two changes conflict each other;

Use change in this locality;

Transmitting the collision decomposition scheme assembles with assurance to other duplicate; And

Appointment policy based on the collision decomposition scheme is decomposed conflict.

Storage platform to storage platform synchronously

The basic application of the synchronous service 300 of storage platform of the present invention is the Multi-instance of synchronous storage platform (each is with its data storage). Service is in storage platform pattern level operation (rather than in the bottom table at database engine 314) synchronously. Therefore, for example " scope (Scope) " is used for defining synchronous group discussed below.

Synchronously service is by the principle operation of " pure change (net change) ". Not record and send each operation (such as transactional replication) that therefore synchronously service but send the final result of these operations often is merged into single final result with the result of a plurality of operations.

The affairs border is not considered in synchronously service usually. In other words, if in single affairs, two changes are made in storage platform data storages, do not guarantee that these change to be applied to atomically on all other duplicate-can to illustrate one and change and other change is not shown. The exception of this principle is that if in same affairs same project is made two changes, then these changes guarantee that being sent atomically and be applied to other copies. Therefore, project is the consistency unit of serving synchronously.

A) synchronous (Sync) controlling application program

Arbitrary application program can be connected to synchronous service and start sync (synchronously) operation. Such application program provides carries out synchronously all required parameters of (synchronous overview below seeing). Such application program is called as synchronous controlling application program (SCA) here.

When synchronous two storage platform examples, started synchronously by SCA in a side. This SCA notice local synchronization service and long-range partner are synchronous. At opposite side, synchronously service is by being waken up by the message of sending from the synchronous service of initiating machine. (mapping that sees below) responds based on the persistent configuration information that exists at target machine for it. Synchronously service can move on schedule or in response to event. In these cases, the synchronous service of realization timetable becomes SCA.

For enabling synchronously, need to take two steps. At first, the Model Design person must be with suitable synchronous semantic note storage platform pattern (as mentioned below appointment change unit). Secondly, synchronously must correctly configuration (as described below) on all machines with the example that participates in synchronous storage platform.

B) pattern note

The basic conception of service is the concept that changes unit (Change Unit) synchronously. Change the unit and be the pattern fragment of the minimum of individually being followed the tracks of by storage platform. Each is changed the unit, and synchronously service can determine that it is changed or is not changed since synchronous for the last time.

Change unit in the designated mode reaches some purposes. At first, it has determined how online synchronous service says another word. Make when changing in changing the unit, whole change unit is sent to other duplicate, because synchronously service does not know which part that changes the unit is changed. Secondly, it has determined the granularity of collision detection. When same change unit being made two concurrent changes (these terms are specific definition in follow-up chapters and sections), synchronously service causes conflict; On the other hand, make concurrent change if difference is changed the unit, then occur without conflict, and change is automatically merged. The 3rd, it has seriously affected the amount of the metadata that is kept by system. Each is changed the unit keep many synchronous service metadatas; Therefore, make the less meeting in change unit increase synchronous overhead.

Definition changes the unit need to find out correct trading off. For this reason, synchronously service allows the Model Design person to participate in this process.

In one embodiment, the change unit greater than an element is not supported in synchronously service. Yet its supports to allow the Model Design person specify a plurality of attributes of an element of the ability of the change unit less than element-be about to be combined in the independent change unit. In this embodiment, this is to use following syntax to realize:＜Type Name=" Appointment " MajorVersion=" 1 " MinorVersion=" 0 " ExtendsType=" Base.Item "

  ExtendsVersion＝″1″>

<Field Name＝″MeetingStatus″Type＝″the storage platformTypes.uniqueidentifier Nullable＝″False″/>

<Fileld Name＝″OrganizerName″Type＝″the storage platformTypes.nvarchar(512)″ Nullable＝″False″/>

<Filed Name＝″OrganizerEmail″Type＝″the storage plattorm Types.nvarchar(512)″   TypeMajorVersion＝″1″                  MultiValued＝″True″/>

…

<ChangeUnit Name＝″CU_Status″>   <Field Name＝″MeetingStatus″/>

</ChangeUnit>

<ChangeUnit Name＝″CU_Organizer″/>   <Field Name＝″OrganizerName″/>   <Field Name＝″OrganizerEmail″/>

</ChangeUnit>

…   </Type>

C) synchronously configuration

The one group of storage platform partner who wishes some Partial synchronization of their data of maintenance is called as synchronous community. Although the member of community wishes to keep synchronously, they need to not represent data in identical mode; In other words, synchronous convertible their synchronous data of partner.

In reciprocity situation, allow equity side to all their partner to keep the conversion mapping be unpractical. Replace ground, the method for definition " community's file " is taked in synchronously service. Community's file is to represent " Shared Folders " of synchronous hypothesis abstract with it of all members of community.

The most handy example explanation of this concept. If Joe wishes to keep his My Documents (my document) file of some computers synchronous, Joe defines community's file, as is called JoeDocuments. On every computer, Joe is configuration one mapping between the JoeDocuments file of supposing and local My Documents file subsequently. From this point, when the computer of Joe was synchronized with each other, they were talked by the document among the JoeDocuments rather than their local project. With the method, the computer of all Joe is understood mutually, and needn't know whom other people is-and community's file becomes the common language of synchronous community.

Configuration synchronously service comprises three steps: (1) is defined in the mapping between local folders and the community's file; (2) definition determines which obtains synchronous synchronous overview (as synchronous with whom, and which subset should be sent out, which is received); And the different synchronous overview of (3) definition timetable that should move, or manually move them.

(1) community's file-mapping

Community's file mapping is stored on the individual machine as the XML configuration file. Each mapping has following pattern :/mappings/communityFolder

Community's file of this element name mapping. Name is followed the syntactic rule of file. / mappings/localFolder

The local folders that this element name mapping is transformed into. This name is followed the syntactic rule of file. In order to shine upon effectively, file must exist. Project in this file be counted as to each this mapping synchronously. / mappings/transformations

How this element definition is transformed into local folders and reverse conversion how with project from community's file. If lack or for empty, do not carry out conversion. Particularly, this means without ID mapped. This configuration is mainly used in creating the high-speed cache of file. / mappings/transformations/mapIDs

The newly-generated local ident of this element request is endowed all from the project of community's file mapping, rather than reuses the ID of community. ID mapping is safeguarded in the synchronous operation storehouse, since revolution change project. / mappings/transformations/localRoot

All root Elements in this element request community file are as the sub-project of designated root. / mappings/runAs

The request for this mapping is processed in this element control under whose is authorized. If do not exist, then suppose the sender. / mappings/runAs/sender

Existing this element to show, must be impersonate to the sender of the message of this mapping, and processes request under his voucher.

(2) overview

Overview is to separate synchronously required total parameter group synchronously. Provide it to the synchronous operation storehouse to start synchronously by SCA. Storage platform comprises following information to the synchronous synchronous overview of storage platform:

Local folders is as the source and target that changes;

Synchronous Remote Folder name-this file must be by shining upon from long-range partner's issue as defined above with it;

Direction-synchronously service support only sends, receives only and send-receive synchronous;

Local filter device-selection sends any local information to long-range partner. Be expressed as the storage platform inquiry on the local folders;

Remote filter device-selection receives what remote information-be expressed as storage platform inquiry on community's file from long-range partner;

How conversion-definition is changed between project and native format;

Local security-appointment is to use from the change of remote endpoint retrieval under the license of remote endpoint (personification), or the user is synchronous at local boot; And

Collision decomposition policy-appointment conflict whether should be rejected, charge to daily record or automatic classifying-under latter event, which collision decomposition device and its configuration parameter are used in appointment.

CLR class when service provides the operation that allows the synchronous overview of simple construction synchronously. Overview can be serialized into the XML file or serialize from the XML file, so that easily storage (often with timetable). Yet the standard of not storing all overviews in storage platform is local; Welcome SCA to make up overview at the point that needn't forever keep. Note, do not need to have local mapping and start synchronously. Can in overview, specify all synchronizing informations. Yet be the synchronous request that starts in response to by long-range side, need mapping.

(3) timetable

In one embodiment, synchronously service does not provide its scheduled basis structure. On the contrary, it depends on another assembly and finishes this task-available Windows Scheduler in Microsoft Windows operating system. Synchronously service comprises command line utility, and it takes on SCA and based on the synchronous overview triggering synchronous that is kept in the XML file. This utility program is so that become very easy on schedule or in response to disposing Windows Scheduler such as user login or the event such as publish.

D) conflict is processed

The synchronously conflict in the service is processed and is divided into three phases: the collision detection when (1) occurs in the change application-this step judges whether to use safely change; (2) automatic collision decomposition and charge to daily record-at the automatic collision decomposition device of this step (after occurring in and then collision detection) information, if with check whether conflict can be decomposed-can not, optionally daily record is charged in conflict; And (3) if conflict check with decomposition-some conflicts and be logged, and occur in outside the simultaneous session, take then that this step-at this moment, the conflict that is logged can be decomposed and remove from daily record.

(1) collision detection

In the present embodiment, synchronously service detection two class conflicts: based on knowledge and Constraint-based.

(a) based on the conflict of knowledge

When two duplicate same change unit is made when independently changing, the conflict based on knowledge occurs. If two change them and make in mutual ignorant situation, then be called independently-in other words, first version is not covered by second knowledge, and vice versa. Synchronously service detects all that conflict automatically based on the knowledge of above-mentioned duplicate.

The bifurcated that conflict is thought of as in the vncsion history that changes the unit is useful sometimes. If in changing the life of unit, do not clash, its vncsion history be simple chain-each occur in previous after. In the situation based on the conflict of knowledge, two change parallel the generation, cause chain splitting, become the version tree.

(b) conflict of Constraint-based

There is the situation of destroying integrity constraint when together using that independently changes. For example, two duplicate with a same file of name establishment can cause occuring such conflict in same catalogue.

The conflict of Constraint-based involves two and independently changes (resembling the conflict based on knowledge), but they do not affect same change unit. On the contrary, their different change unit of impact, but between them, have constraint.

The synchronously constraint of service detection when changing application destroys, and automatically causes the conflict of Constraint-based. The conflict of decomposing Constraint-based needs self-defined code usually, and it revises those changes in the mode of not destroying constraint; Synchronously service does not provide the general mechanism of doing like this.

(2) conflict is processed

When detecting conflict, synchronously service can be taked one of three actions (being selected by the synchronous startup person in the synchronous overview): (1) refuses this change, and it is turned back to the sender; (2) conflict is logged into the conflict daily record; Or (3) automatic classifying conflict.

Be rejected if change, synchronously service does not operate as this change arrives this duplicate. NACK is sent back to the promoter. Mainly upper useful without leader's duplicate (such as file server), it is infeasible conflict being charged to daily record there to this decomposition policy. On the contrary, those duplicate force other duplicate to process those conflicts by refusing them.

Startup person's configuration conflict in their synchronous overview decomposes synchronously. A plurality of collision decomposition devices-at first by specifying the tabulation of collision decomposition device, attempt one by one decomposing, until one of them success are made up in synchronously service support in the following manner in single overview; The second, by the collision decomposition device is associated with the conflict type, such as conflict to the decomposer of guiding renewal-renewal based on knowledge, but daily record is charged in all other conflicts.

(a) automatic collision decomposition

Synchronously service provides the collision decomposition device of some acquiescences. Its tabulation comprises:

The local win: if with the data collision of this locality storage, then disregard the change that enters;

Long-range win: if conflict with the change that enters, then disregard local data;

Write at last win: this locality win or the long-range win of selecting each change unit based on the time mark that changes (notice that synchronously service does not generally rely on clock value; This collision decomposition device is this regular sole exception);

Determine: identical to guarantee on all duplicate, but an insignificant mode embodiment selecting winner-synchronously service relatively realizes this feature with the lexicographic of Partner ID in other cases.

In addition, ISV can realize and install their collision decomposition device. Self-defined collision decomposition device can be accepted configuration parameter; Those parameters must be by specifying in the collision decomposition section of SCA in synchronous overview

When the collision decomposition device was processed conflict, it returned the tabulation of the operation (substituting conflict changes) that needs execution to Runtime Library. Then these operations are used in synchronously service, and it has the long-range indication of correctly adjusting, with all the elements that comprise that conflict processor is considered.

When using decomposition, may detect other conflict. In such situation, new conflict must be decomposed before original processing restarts.

When conflict being considered to the branch in the vncsion history of project, collision decomposition can be regarded merging-two branches of combination as to form a single point. Therefore, collision decomposition forwards vncsion history to DAG.

(b) conflict log recording

A kind of collision decomposition device of very particular type is conflict log recording device. Synchronously service is charged to daily record as the project of ConflictRecord (conflict record) with conflict. These the record conversely with the conflict in project relevant (unless project itself is deleted). Each conflict record comprises: the change that enters that leads to a conflict; The type of conflict; Upgrade-upgrade, upgrade-deletion, delete-upgrade, insert-insert or constraint; And the knowledge of the version of the change that enters and its duplicate of transmission. The conflict of charging to daily record can be used for inspection described below and decomposition.

(c) conflict examination and decomposition

The service application programs provides API synchronously, to check conflict daily record and suggestion collision decomposition wherein. This API allows application program to enumerate all conflicts, or the conflict relevant with given project. Also allow those application programs to decompose the conflict of charging to daily record with one of following three kinds of methods: (1) long-range win-acceptance is charged to the change of daily record and is override this locality change of conflict; (2) the conflict part of the change of charging to daily record is won-ignored in this locality; And the new change of (3) suggestion-wherein, application program proposes that one merges, and with its viewpoint, this merges and decomposes conflict. In case decomposed conflict by application program, synchronously service removes them from daily record.

(d) propagation of the convergence of duplicate and collision decomposition

In the situation of complex synchronization, in a plurality of duplicate, can detect same conflict. If this situation occurs, some things occur: (1) can decompose conflict on a duplicate, and other duplicate is delivered in decomposition; (2) conflict on two duplicate by automatic classifying; And (3) manually decompose conflict (by overhaul API) on two duplicate.

For guaranteeing convergence, synchronously service is forwarded to other duplicate with collision decomposition. When the change of decomposing conflict arrived duplicate, synchronously service was automatically sought in daily record and is upgraded thus any conflict of decomposing, and eliminates them. In the case, the collision decomposition on duplicate is bound to all other duplicate.

If different duplicate has been selected different winners to same conflict, then synchronously the principle of binding collision decomposition is used in service, and automatically selects in two decomposition one and surpass another. Select the winner to guarantee all to produce same result (embodiment uses duplicate ID lexicographic relatively) constantly at all in deterministic mode.

If different copying advised different " the new change " to same conflict, then service is processed into special conflict with this new conflict synchronously, and prevents that with the log recording device that conflicts it from propagating into other duplicate. Occur when situation is everlasting manual collision decomposition like that.

To the storage of non-storage platform data synchronously

By storage platform of the present invention on the other hand, the architecture that storage platform provides ISV to be used to realize synchronous adapter, synchronously adapter makes the storage platform can be with synchronous such as legacy systems such as Microsoft Exchange, AD, Hotmail. Synchronously the many synchronous service that provided by following synchronous service is provided adapter.

No matter its title how, adapter does not need to realize as the plug-in unit of certain storage platform architecture synchronously. When needed, " synchronously adapter " can be to utilize synchronous service operation bank interface to obtain to enumerate and any application program of the service such as application such as change simply.

In order to make other people can more easily dispose and run to the synchronous of given back of the body end (backend), encourage the author of synchronous adapter to represent the synchronous adaptor interface of standard, it moves when given above-mentioned synchronous overview synchronously. Overview provides configuration information to adapter, some adapter be sent to the synchronous operation storehouse with controlling run storehouse service (as, synchronous file).

A) synchronously service

Synchronously service provides some synchronous services to the adapter author. At this section remaining part, easily storage platform is made synchronous machine thereon and be called " client computer ", and adapter just is called " server " with the non-storage platform back of the body end of its dialogue.

(1) change is enumerated

Based on the change tracking data of being kept by synchronous service, change is enumerated and is allowed synchronous adapter easily to enumerate the change that since last and this partner attempt to make synchronously the data storage folder has been occured.

Enumerate based on the concept of " anchor position (anchor) " that change-this is the opaque structure of relevant last the hyposynchronous information of expression. As described in former chapters and sections, the form of storage platform knowledge is taked in the anchor position. Utilize the synchronous adapter that changes the service of enumerating to fall into two large classifications: the adapter of " anchor position of storage " and the adapter of use " anchor position that provides " are provided.

Difference based on where be stored in about last hyposynchronous information-on the client computer or on server. Adapter usually easily store this information on client computer-back of the body end often can not easily store this information. On the other hand, if a plurality of client computer and same back of the body end are synchronous, then this information is stored on the client computer be poor efficiency and be in some cases incorrect-this makes a client computer not know that other client computer shifted the change of server onto. If adapter wishes to use the anchor position of server stores, then adapter need to send back to storage platform with it when change is enumerated.

In order to allow storage platform safeguard anchor position (being used for the Local or Remote storage), storage platform need to be known the change that successfully is applied on the server. These and only have these changes to be included in the anchor position. During change was enumerated, adapter used and confirms (Acknowledgement) interface synchronously, was successfully used to report which changes. With EOS the time, the adapter of the anchor position that use provides must be read new anchor position (it gathers the change of all successful Application) and send it to their back of the body end.

Each adapter usually needs the storage adapter exclusive data and is inserted into projects in the storage platform data storages. The common examples of this data storage is remote ident and long-range version (time mark). Synchronously service is provided for storing the mechanism of these data, and changes the mechanism that the change that receives this excessive data and will return is provided of enumerating. In most of the cases, this has eliminated the again demand of Query Database of adapter.

(2) change application

Changing to use allows synchronous adapter to be applied to local storage platform from the change that their back of the body termination is received. The expectation adapter is transformed into the storage platform pattern with change. Figure 24 illustrates the process that generates storage platform API class from the storage platform pattern.

Changing the major function of using is automatically to detect conflict. As in the storage platform situation synchronous to storage platform, two overlapping changes that conflict is defined by making when not knowing mutually. When adapter used change to use, they must specify the anchor position of it being carried out collision detection. Change if detect overlapping this locality of the knowledge covering that is not adapted device, then change application and cause conflict. Be similar to change and enumerate, adapter can be provided by anchor position storage or that provide. Change effective storage of using the special-purpose metadata of support adapter. Such data can be appended to it in the change that will use by adapter, and can be by synchronous service memory. Data can change in next time to be returned when enumerating.

(3) collision decomposition

Below the collision decomposition mechanism (comprise and charge to daily record and automatic classifying option) in IV, described also can use synchronous adapter. When using change, adapter can be specified the policy that is used for collision decomposition synchronously. If specified, conflict can be passed to the conflict handling procedure of appointment and be decomposed (if possibility). Conflict also can be logged. When attempting that this locality is changed when being applied to back of the body end, adapter might detect conflict. In such situation, adapter still can be delivered to conflict the synchronous operation storehouse, to decompose by policy. In addition, adapter can ask any conflict by synchronous service detection to send back to them in order to process synchronously. This is convenient especially to store or decompose the situation of conflicting at back of the body end.

B) adapter is realized

Although some " adapter " is the application program of utilizing the Runtime Library interface simply, yet encourage adapter to realize the adaptor interface of standard. These interfaces allow synchronous controlling application program: the request adapter is carried out synchronously by given synchronous overview; It is synchronous that cancellation is just being carried out; And receive about just carrying out synchronous progress report (Percent Complete).

3. security

Synchronously service make great efforts will be the least possible be incorporated into synchronously safe mode by the storage platform realization. Not to define synchronous new authority, but use existing authority. Particularly,

Anyone of energy read data stored items can enumerate the change to that project;

Anyone that can write the data stored items can use this project that changes to; And

Anyone of energy growth data stored items can be with synchronous metadata and this item association.

Security certificate information is not safeguarded in synchronously service. When making change at duplicate A by user U, and when it was forwarded to duplicate B, this change had been lost in the fact that A place (by U) makes at first. If B is forwarded to duplicate C with this change, then this is to finish under the mandate of B rather than the mandate at A. This just causes following restriction: if distrust a duplicate that a project is made its change, it can not transmit the change of being made by other duplicate.

When starting synchronously service, finished by synchronous controlling application program. The synchronous identity of service personification SCA, and under this identity, finish all operations (local with long-range). As an illustration, observe the change that user U can not make the local synchronization service from long-range storage platform retrieval user U not had the project of read access.

4. manageability

The distributed community that monitors duplicate is complicated problem. Synchronously service can be used " scanning (sweep) " algorithm to collect and distribute information about the state of this duplicate. The attribute of scanning algorithm guarantee about to some extent the information of duplicate of configuration finally be collected, and detect the duplicate of this failure (without responding).

On each duplicate, can obtain the monitor message of community's scope. Can be on the duplicate of choosing arbitrarily the operation monitoring instrument, to check this monitor message and to make administrative decision. On affected duplicate, must directly make configuration change.

J. traditional file interoperability

As mentioned above, at least in certain embodiments, storage platform of the present invention is intended to be implemented as the integral part of the hardware of computer system/software interface system. For example, storage platform of the present invention can be implemented as the integral part such as Microsoft Windows family operating system. In this respect, storage platform API becomes the part of operating system API, and application program is mutual by it and operating system. Therefore, storage platform becomes device, and application program is deposited information on the operating system by it, thereby and the data model of project-based storage platform substituted the traditional file systems of this operating system. For example, when in Microsoft Windows family operating system, implementing, the alternative new technology file system of in this operating system, realizing of storage platform. Current, application program visits the service of new technology file system by the Win32API that is represented by Windows family operating system.

Yet, will be appreciated that, substitute new technology file system with storage platform of the present invention fully and need the existing application program based on Win32 of recompile, therefore and such recompile may be undesirable, and to provide with certain interoperability such as existing file systems such as NTFS be useful to storage platform of the present invention. Thereby in one embodiment of the invention, storage platform makes the application program that depends on the Win32 programming model can access simultaneously the content of the data storage of the data storage of storage platform and traditional new technology file system. For this reason, storage platform uses the name custom of the superset (superset) that name is accustomed to as Win32 so that be easy to interoperability. In addition, the storage platform support is stored in file and catalogue in the storage platform volume by the Win32 API Access.

About finding in the other details of this function relevant patent can be formerly incorporated herein by reference.

K. storage platform API

Storage platform comprises API, and it makes application program can access feature and the ability of storage platform discussed above, and access is stored in the project in the data storage. This section is described the embodiment of the storage platform API of storage platform of the present invention. Details about this function can find in relevant patent incorporated herein by reference, sum up below for simplicity this information certain some.

With reference to Figure 18, the include file folder is a project, and it comprises the relation of holding with other project, and of equal value with the file system file of common concept. Each project " comprises " at least one include file folder.

Figure 19 illustrates the basic architecture by the storage platform API of present embodiment. Storage platform API uses SQL client computer 1900 and local datastore 302 dialogues, and also uses SQL client computer 1900 and long-range number storage (such as data storage 340) dialogue. Local storage also can be used DQP (Distributed Query Processing device) or serve synchronously (" Sync ") and teledata storage 340 dialogues by above-mentioned storage platform. Storage platform API 322 also takes on the bridger API of data storage notice, the subscript of application program is sent to notification engine, and as mentioned above notice is routed to application program (such as application program 350a, 350b or 350c). In one embodiment, storage platform API 322 also defines restricted " supplier " architecture, so that it can access the data among Microsoft Exchange and the AD.

Figure 20 schematically shows the various assemblies of storage platform API. Storage platform AP comprises following assembly: (1) data class 2002, and it represents storage platform element and item types; (2) the Runtime Library framework 2004, the persistence of its management object and the class 2006 that provides support; And (3) instrument 2008, it is used for generating the CLR class from the storage platform pattern.

The hierarchy of the class that draws from given pattern has directly reacted the hierarchy of type this pattern. As an example, consider the item types in the contact schema as shown in Figure 21 A and Figure 21 B, define.

Figure 22 illustrates the Runtime Library framework in the operation. The following operation of Runtime Library framework:

1. application program 350a, 350b or 350c are tied to the project of storage platform.

2. framework 2004 creates the ItemContext object 2202 corresponding to the binding project, and it is returned to application program.

3. application program is submitted the Find (searching) on this ItemContext (project context) to, to obtain the set of project; Return to be integrated into conceptive be object diagram 2204 (because relation).

4. application program change, deletion and data inserting.

5. application program is preserved change by calling Update () method.

Figure 23 illustrates the execution of " FindAll (seeking all) " operation.

Figure 24 illustrates the process that generates storage platform API class from the storage platform pattern.

Figure 25 illustrate file API based on pattern. Storage platform API comprises the name space of processing file object. This name space is called as System.Storage.Files. The data member of the class among the System.Storage.Files has directly reflected the information that is stored in the storage platform storage; This information is from file system object " upgrading " or use Win32API the machine ground to create. The System.Storage.Files name space has two class: FileItem (docuterm) and DirectoryItem (catalogue project). The member of these classes and method thereof can be predicted by the ideograph of checking among Figure 25. FileItem and DirectoryItem are read-only from storage platform API. For revising them, must use Win32API or class among the System.IO.

For API, DLL (or being simply referred to as interface) can be regarded as communicating or to its arbitrary mechanism, process, agreement that conducts interviews be used to the function that the one or more segments that make code can provide with one or more other segments by code. Perhaps, DLL can be regarded as being coupled to communicatedly the one or more mechanism, method, function call, module, object etc. of assembly of system of one or more mechanism, method, function call, module etc. of other computer. Term in the above-mentioned statement " code snippet " is intended to comprise one or more instructions or the code line of code, and comprise, as, code module, object, subroutine, function etc., the term of no matter using be what or code snippet whether by separately compiling or code snippet whether be provided as source code, intermediate code or object identification code, code snippet whether during in operation in system or the process with or they whether be positioned on same or the different machines stride that a plurality of machines distribute or the function that represented by code snippet whether fully by software, the combination by hardware or hardware and software realizes fully.

Conceptive, DLL can be generally looked, shown in Figure 30 A or Figure 30 B. It is pipeline that Figure 30 A shows interface " interface 1 ", and the first and second code snippets communicate by this pipeline. Figure 30 B shows interface and comprises interface object I1 and the I2 part of yes or no the first and second code snippets (can), and they make the first and second code snippets of system communicate by medium M. In Figure 30 B, can think that interface object I1 and I2 are the independent interface of same system, and can think that also object I1 and I2 add that medium M has consisted of interface. Although Figure 30 A and 30B show the interface on each side of Bidirectional Flow and this flow process, some realization can only have an information flow (or as described below do not have information flow) on the direction, or only has the interface object of a side. As example but not limitation be included within the definition of DLL such as using programming or the terms such as routine interface (API), entrance, method, function, subroutine, remote procedure call and The Component Object Model (COM) interface.

The aspect of this class DLL can comprise that the first code segment sends the method (wherein, " information " is used with its wide significance, and comprises data, order, request etc.) of information to the second code segment; The second code segment receives the method for information; And the structure of this information, sequence, grammer, tissue, pattern, timing and content. In this, as long as information transmits in the defined mode of interface, the operation that bottom transmission medium itself can docking port is inessential, and no matter this medium is wired or wireless, or both combinations. In some cases, on conventional meaning, when a code snippet is only accessed the function of being carried out by the second code segment, information can not transmitted in one or two direction, because communication can be or by another mechanism (as, information be placed on code snippet between the buffer memory that separates of information flow, file etc. in) or do not exist. Any of these aspects or all can be important in given situation, as, depend on the whether part of the system of loose coupling or close coupling configuration of code snippet, and therefore this tabulation should be considered to illustrative and unrestricted.

This concept of DLL is known to those skilled in the art, and can read the detailed description of the invention described above and know this concept. Yet, there is other method to realize DLL, unless and get rid of significantly, in these methods also are included in by appended claims. It is more accurate or complicated than the view of Figure 30 A and 30B that these other methods seem, but they are still carried out similar function and finish same whole result. Concise and to the point some illustrative of describing DLL is replaced and is realized now.

Decompose: can indirectly realize communication from a code snippet to another by communication being split into a plurality of distributed communication. This schematically describes in Figure 31 A and 31B. As shown in the figure, can be according to function divide into groups to describe some interface. Thus, can exploded view 30A and the interface function of 30B reach identical result, as can providing 24 at mathematics, or 2 take advantage of 2 take advantage of 3 take advantage of 2 the same. Therefore, shown in Figure 31 A, the function that is provided by interface " interface 1 " can be provided become a plurality of interfaces " interface 1A ", " interface 1B ", " interface 1C " etc. with the communication scaling with this interface, and reach identical result. Shown in Figure 31 B, the function that is provided by interface I1 can be subdivided into a plurality of interface I1a, I1b, I1c etc., and reaches identical result. Similarly, the interface I2 that receives the second code segment of information from the first code segment can be broken down into a plurality of interface I2a, I2b, I2c etc. When decomposing, the quantity that is included in the interface in the first code segment does not need to mate the quantity that is included in the interface in the second code segment. In arbitrary situation of Figure 31 A or 31B, the functional spirit of interface " interface 1 " and I1 is identical with the maintenance of Figure 30 A and 30B respectively. The decomposition of interface also can be deferred to associating, communication and other mathematics character, so that decompose difficult identification. For example, command operation can be unessential, and the function of therefore being finished by interface can be finished by another section code or interface before reaching this interface preferably, is perhaps carried out by the independent assembly of system. In addition, the those of ordinary skill in programming field is appreciated that variety of way makes different function calls and reach identical result.

Redefine: in some cases, may ignore, add or redefine some aspect (such as parameter) of DLL, and still reach expected result. This is shown in Figure 32 A and the 32B. For example, the interface " interface 1 " of supposing Figure 30 A comprises function call Square (input, precision, output) (square), it comprises three parameters, input (input), precision (precision) and output (output), and issued to the second code segment by the first code segment. If middle parameter p recision is unimportant under given situation, shown in Figure 32 A, it also can be left in the basket or even be replaced by meaningless (meaningless) (in this case) parameter. Also can add inessential additional (in addition) parameter. In either case, as long as return output in input by after the second code segment square, just can reach square (square) function. Precision might be extremely significant parameter to a certain downstream or the other parts of computing system also; Yet in case recognize that precision is optional to calculating square this limited purpose, it can be replaced or ignore. For example, not to transmit an effective pricision value, but in situation the about result not being had a negative impact, transmit such as insignificant values such as dates of birth. Similarly, shown in Figure 32 B, interface I1 is by interface I1 ' replacement, and it is redefined to ignore or adds parameter to interface. Interface I2 can be redefined similarly is interface I2 ', and it is redefined to ignore unnecessary parameter, or the parameter that can process elsewhere. Main points herein are in some cases, and DLL can comprise the unwanted aspect of a certain purpose, such as parameter, therefore can ignore or redefine them, or process elsewhere them and be used for other purpose.

Embedded code: some or all functions that merge two independent code modules also are feasible, so that " interface " between them changes form. For example, the function of Figure 30 A and 30B can be transformed into respectively the function of Figure 33 A and 33B. In Figure 33 A, the first and second previous code snippets of Figure 30 A are merged into the module that comprises both. In this case, this code snippet still can communicate with one another, but this interface goes for being more suitable for the form of individual module. Thus, for example, formal calling (Call) and to return (Return) statement will be no longer essential, but be still effectively according to similar processing or the response of interface " interface 1 ". Similarly, shown in Figure 33 B, the part of Figure 30 B (or owning) interface I2 can write incoming interface I1 embeddedly and form interface I1 ". As shown in the figure, interface I2 is divided into I2a and I2b, and interface section I2a is embedded in and writes code among the interface I1 and form interface I1 ". For concrete example, consider the interface 1 execution function call square (input, output) of Figure 30 B, it is received by interface I2, processed the value be delivered to input (it is asked square) by the second code segment afterwards, it is used output and transmits back the result who asks square. In this case, the processing of being carried out by the second code segment (input is asked square) can be carried out never calling in the situation of this interface by the first code segment.

Break away from: can indirectly finish communication from a code snippet to another by communication being split into a plurality of discrete communications. This schematically describes in Figure 34 A and 34B. Shown in Figure 34 A, provide one or more segments of middleware (to break away from interface (Divorce Interface), because function and/or interface function that they break away from from original interface), to transform the communication on the first interface " interface 1 ", so that they meet different interfaces, be " interface 2A ", " interface 2B " and " interface 2C " in this situation. This can finish in such a case, for example, the installation basis of using according to " interface 1 " Protocol Design with communicate such as operating system, using different interfaces but then change this operating system, is interface " interface 2A ", " interface 2B " and " interface 2C " in this situation. Main points are to have changed the clean interface that is used by the second code segment so that it no longer with the employed interface compatibility of first code segment, therefore make old interface and new interface compatible with intermediary. Similarly, shown in Figure 34 B, it is disconnected to receive information from interface I1 to use disengaging interface DI1 to introduce third generation chip, and use breaking away from interface DI2, to introduce third generation chip disconnected with to for example interface I2a and I2b transmission interface function, redesign interface I2a and I2b with use DI2, but provide identical functional outcome. Similarly, DI1 and DI2 can work to convert the interface I1 of Figure 30 B and the function of I2 to a new operating system jointly, and identical or similar functional outcome is provided.

Rewrite: another possible variation is dynamically to rewrite code, replaces the function of interface with anything else, and still reaches identical overall result. For example, a kind of system can be arranged, wherein, (JIT) compiler or interpreter provide the code snippet that presents in the intermediate language (such as Microsoft IL, Java ByteCode etc.) to timely (Just-in-Time) in the execution environment (such as the environment that provided by the .Net framework, java runtime environment or other similar time of running of type environment). Can write JIT compiler and be transformed into the second code segment dynamically will communicate by letter from the first code segment, that is, make them meet the needed distinct interface of second code segment (original or different second code segments). This has description in Figure 35 A and 35B. As among Figure 35 A see that this mode is similar to above-mentioned disengaging situation. It can be finished under such a case, and for example, the installation fundamental operation system that uses according to " interface 1 " Protocol Design communicates, and then changes this operating system to use different interfaces. JIT compiler can be used for order the new interface that the air communication of base application meets operating system has been installed. Described such as Figure 35 B, can use this method that dynamically rewrites interface to carry out dynamic Decomposition, perhaps change interface.

Should be noted that above-mentioned also in every way serial of situation by alternative embodiment realization and the same or analogous result of interface, walk abreast or intervene code combination with other. Thus, the alternative embodiment that above presents not is mutual limit, and can be mixed, coupling and combination to be to produce the situation identical or equivalent with the general situation that presented among Figure 30 A and the 30B. Also should be noted that, as most of programming constructs, the present invention may not describe other the similar mode that reaches with the same or analogous function of interface, but they are still represented by the spirit and scope of the present invention, namely, should be noted that it is the function that represented by the interface as the basis of the value of interface or by its favourable outcome of enabling at least in part.

III. expand and inherit

A basic concept of the present invention is to utilize project, it use to a certain extent by pattern description and come modelling real world application by labyrinth, behavior and the operation of hardware/software interface System Implementation. For abundant subtype function is provided, and in various embodiment of the present invention, hardware/software interface system (for convenient, hereinafter will referred to as " WinFS ") can provide a kind of mechanism, can use " expansion " to come expansion project (and item types) by it. Expansion provides additional data structure (attribute, relation etc.) to the item types structure that has existed.

(and particularly in chapters and sections II.E.6. (a) and II.F.3, the discussing) of discussing in this article such as the front, although be the initial sets that will supply a pattern for storage platform, but storage platform allows the client to comprise that independently software marketing merchant (ISV) creates new pattern (that is, new project and nested element type) in some embodiment at least. The item types or the nested element type that define owing to the initial sets by the storage platform pattern inaccurately meet the demand that ISV uses, and therefore are necessary to allow the ISV types of customization. This is to allow with the concept of expanding. Expansion is strong typing example but (a) they can not have an independent existence and (b) they must be attached to project or nested element. And except solving the demand of pattern extensibility, expansion also will solve " multiple type " problem. Because storage platform is not supported multiple inheritance or overlapping subtype in some embodiments, therefore use and to use expansion as the mode of the overlapping type instance of modelling (for example, a document can be " legal documents ", also can be " security document ").

A. type system

In various embodiment of the present invention, the WinFS type system provides a kind of mechanism that defines the structure of data. Type system is used for the data that expression is stored in WinFS. The WinFS type is stated in the WinFS pattern. Name space of WinFS mode-definition, it is as the logic grouping of a set type and other WinFS pattern element. The WinFS pattern can use WinFS mode-definition language (SDL) (it may use the XML language) to state. The below is the example of a possible pattern statement:

<Schema Namespace＝″System.Storage″>

   Type definitions

</Schema>

The WinFS pattern is also as the type version unit. WinFS defines the system model of some guidance systems. These are System.Storage schema name word spaces, and it comprises the type declarations of root type in the system, and System.Storage.WinFS schema name word space, all base scalar types in its statement system.

The WinFS type system is stated one group of simple scalar type. These types are as the most basic building block of all other types in the WinFS type system. These types are stated in schema name word space System.Storage.WinFS. Following table definition fundamental type set.

The WinFS type	Managed SQL type	The CLR type	Describe
				String	SqlString	String	It is 2^31 character length that variable-length Unicode data have maximum length. Use " max " (maximum) key length to fix or unfettered from 1-4000 character.
Binary	SqlBinary	Byte[]	It is 2^32 byte length that the binary data of variable-length has maximum length. Use " max " (maximum) key length to fix or unfettered from 1-8000 byte.
				Boolean	SqlBoolean	Boolean	Can be the Boolean of NULL
Byte	SqlByte	Byte	Single without symbol-byte
				Int16	SqlInt16	Int16	Integer data from-2^15 (32,768) to 2^15-1 (32,767)
Int32	SqlInt32	Int32	Integer (integer) data from-2^31 (2,147,483,648) to 2^31-1 (2,147,483,647)
				Int64	SqlInt64	Int64	Integer (integer) data from-2^63 (9223372036854775808) to 2^63-1 (9223372036854775807)
Double	SqlDouble	Double	The floating point precision logarithmic data is from-3.40E+38 to 3.40E+38
				Single	SqlSingle	Single	The floating point precision logarithmic data is from-1.79E+308 to 1.79E+308
Decimal	SqlDecimal	Decimal	SQLDecimal has the value scope larger than CLRDecimal type. Precision 28 numbers always in memory

			Word and ratio are 0.
				DateTime	SqlDateTime	DateTime	Date and time from December 31,1 day to 9999 January in 1753, has the accuracy of three centiseconds or 3.33 seconds
Guid	SqlGuid	Guid	Whole world unique identifier (GUID)
				Xml	SqlXmlReader	XmlReader	For milestone B, WinFS.Xml will be mapped to " String " type. Real XML data type support is expected among the milestone C.
Stream	TBD	TBD	The binary data type uses the storage of supporting document flow to be used for effectively access. This type will be supported in milestone C.

It is a scalar type that WinFS enumerates, and it states the constant of one group of name, is called value list. Enumeration type can used the Anywhere use of scalar type. Here be the example of enumerating statement:

<Enumeration Name＝″Gender″>

   <Value Name＝″Male″/>

   <Value Name＝″Female″/>

</Enumeration>

Enumerated value is based on zero. Gender.Male represents to be worth 0 and Gender.Female represents to be worth 1 in the above example.

Complicated type is by name and one group of attribute definition. Attribute is member's field of type, and by name and type definition. The type of attribute can be scalar (comprising enumeration type) or can be other complicated type. The WinFS type that can be used as the type of attribute is called as nested type. The example of nested type can be only exists as the property value of the attribute of complicated WinFS type--and this example is nested in the example of a complicated type. Nested type is to use the statement of NestedType (nested type) pattern element. Here be some examples of life type statement:

<NestedType Name＝″Address″BaseType＝″System.Storage.NestedObject″>

  <Property Name＝″Street″Type＝″WinFS.String″Size＝″256″

  Nullable＝″false″/>

     <Property Name＝″City″Type＝″WinFS.String″Size＝″256″

  Nullable＝″false″/>

     <Property Name＝″State″Type＝″WinFS.String″Size＝″256″

  Nullable＝″false″/>

     <Property Name＝″Country″Type＝″WinFSString″Size＝″256″

  Nullable＝″false″/>

  </NestedType>

  <ItemType Name＝″Person″BaseType＝″System.Storage.Item″>

     <Property Name＝″Name″Type＝″WinFS.String″Size＝″256″

  Nullable＝″false″/>

     <Property Name＝″Age″Type＝″WinFS.Int32″

  Nullable＝″false″Default＝″1″/>

     <Property Name＝″Picture″Type＝″WinFS.Binary″Size＝″max″/>

     <Property Name＝″Addresses″Type＝″MultiSet″MultiSetOfType＝″Address″/>

  </ItemType>

For the attribute of type String and Binary, must specify Size (size) attribute. This attribute is specified the full-size that is included in the value among the Property (attribute). Attribute can use the Nullable attribute to state alternatively can be the constraint of null. The value of this attribute must provide a value when being applied in the example that creates the type for " false (vacation) " expression. Another optional Property (attribute) attribute is Default (acquiescence) attribute, and it specifies the default value of Property (attribute). This value will be assigned to Property (attribute) when example creates, do not provide it if use.

Addresses in upper example (address) attribute is MultiSet (multiple setting) type. The attribute of MultiSet (multiple setting) type is also referred to as multi-valued attribute. MultiSet (multiple setting) comprises the example of one group of Address (address) type in this example. MultiSet (multiple setting) is similar to set. It can comprise the example of zero or a plurality of complicated types. The type of the example in MultiSet (multiple setting) must be complicated nested type. MultiSet (multiple setting) type is not supported the WinFS scalar type example of (comprising enumeration type). The attribute of MultiSet (multiple setting) type can not be and default value can not be arranged for null's.

WinFS supports the single inheritance of type. All types in WinFS must and can only be inherited a WinFS type from one. The type of inheriting is called derived type and is called base type from its type that derives this type. Base type in BaseType (base type) attribute in WinFS statement element. Suppose that type A derives from base type B, and B and then derive from Type C. Type C is ancestors' type of type A and type B. Type A is descendants's type of type B and C. The data example that is stored among the WinFS is the example of single type all the time. Yet the data example can be considered as one group of example that comprises the type of the type and all ancestors' types thereof. For the data example as the example of such set type, call the ancestors' of any other type in the group that is not in the end to derive (most-derived) type type. Independent typed data example is to be exactly the example of a last derived type. Usually, the type that the last derived type of independent typed element is called it. Derived type is inherited all properties of stating in its base type. Derived type can be stated new attribute but can not cover the attribute that defines in the base type. The attribute of stating in derived type must not use the name identical with the attribute of base type.

The major advantage of inheriting in data model comes from the replaceability of inheriting type. Example below considering:

  <NestedType Name＝″Name″BaseType＝″System.Storage.NestedObject″>

    <Property Name＝″FirstName″Type＝″WinFS.String″/>

    <Property Name＝″LastName″Type＝″WinFS.String″/>

  </Nestedype>

  <NestedType Name＝″NameWithMiddleInitial″BaseType＝″Name″>

    <Property Name＝″MiddleInitial″Type＝“WinFS.String″/>

  </NestedType>

  <NestedType Name＝″Person″BaseType＝″System.Storage.Item″>

    <Property Name＝″RealName″Type＝″Name″/>

    <Property Name＝″OtherNames″Type＝″MultiSet″MultiSetOfType＝″Name″/>

  </NestedType>

In the above example, type Person (individual) has the attribute RealName that type is Name (name) (true name) and as the attribute OtherNames (other name) of one group of Name (name) type. Usually requiring attribute RealName (true name) to only have its type is the example of Name (name). Yet by inheriting, allowing the monodrome example is the value of RealName (true name), as long as Name (name) type is one of the ancestors of the last derived type of this element. Therefore, the example of NameWithMiddleInitial (name with middle initial) will allow for the value of attribute RealName (true name).

Expand identical rule to set a property. Attribute OtherNames (other name) comprises a group element. For each independent type example (they are members of this set), the last derived type of this example must have Name (name) as its one of ancestors. Therefore, some examples in OtherNames (other name) set can be the examples of Name (name) type, although other example may be the example of NameWithMiddleInitial (name with middle initial) type.

Inherit and also support easily inquiry, because might in the WinFS system, find out all examples of certain type. When searching all examples of a type, the example that it is descendants of this type that query engine also will return all its last derived types. Yet, only have project, expansion and relationship type (not being attribute type) to support these operations. For nested type (being again nested element, attribute or complex properties type), the example that only is included in single multiple the setting a property is supported this operation.

B. type family

In a word, four different categorical serieses of WinFS type system definition:

Nested element type (being again nested type or attribute type)

Item types

Relationship type

Expansion type

Each categorical series has a different attribute and usage set in the WinFS type system. Four types of root types as each categorical series of System.Storage schema name word space statement. Following chapters and sections describe these type systems in detail.

1. nested element type

Unlike other WinFS categorical series, nested type can be used as the type of the attribute of complicated WinFS type. The example of nested type is only with in the example that is nested in another complicated type. Yet the example of nested type can not be by global query--namely, application can not be write all examples that a given nested type in the WinFS memory is returned in a simple inquiry.

2. item types

The WinFS project is that its ancestors are examples of the type of System.Storage.Item type. This type is the complicated type as the root of item types series. System.Storage.Item has stated that an ItemID by name (item id) type is the attribute of Guid. This is a specific properties of project, as the major key of project. The value that guarantees this attribute is unique for the project in the given WinFS memory. This attribute can not be null, and must be when being applied in the example that creates item types assignment. ItemID (item id) attribute also is immutable--it never changes and must not be reused.

Query engine can return the example of given item types in the WinFS memory. This inquiry can be returned all examples of the type and all type descendants types thereof. This paper describes the center role that project has after a while in WinFS system operational semantics.

3. relationship type

Relationship type can be present between the project relation. The WinFS relationship type is described binary system relation, and wherein specifying a project is source and to specify another project be target. Relation is that its ancestors are examples of the type of System.Storage.Relationship type. This type is the root of relationship type hierarchical structure. Column Properties under the System.Storage.Relationship type declarations:

SourceItemID (source item id)--as the ItemID (item id) of the project in the source of relationship example

RelationshipID (relations I D)--with respect to the unique identifier of source item purpose relation; (SourceItemID (source item id), RelationshipID (relations I D)) is to forming the major key that concerns among the WinFS

The ItemID (item id) of TargetItemId (destination item ID)--the target of relation

Mode (mode)--one of 3 kinds of possible relationship example modes: Holding (holding), Embedding (embedding) or Reference (quoting)

The name of Name (name)--inclusion relation is used for holding relation

IsHidden (whether hide)--boolean properties, application can be alternatively filter the relation that is shown of not needing with it

SourceItemID (source item id), RelationshipID (relations I D), TargetItemId (destination item ID) and Mode (mode) property value are immutable. They at the relationship example creation-time by assignment and can not change.

Relationship type is claimed as the complicated type with following additional constraint:

Source and target end points standard: each end points is specified the type of name and the project that is cited

Institute's permission mode of the example of relationship type: relationship example can not have the value of unallowed Mode (mode) attribute in the relation statement

Here be the example of relation statement:

      <RelationshipType Name＝″DocumentAuthor″

       BaseType＝″System.Storage.Relationship″

       AllowsHolding＝″true″

       AllowsEmbedding＝″false″

       AllowsReference＝″true″>

         <Source Name＝″Document″Type＝″Core.Document″/>

         <Target Name＝″Author″Type＝″Core.Contact″/>

         <Property Name＝″Role″Type＝″WinFS.String″/>

         <Property Name＝″DisplayName″Type＝″WinFS.String″/>

      </RelationshipType>

DocumentAuthor (document author) relation is with example the restriction of Holding (holding) or Reference (quoting) to be stated. The example that this means DocumentAuthor (document author) relation can have the example with value Mode=" Reference " or Mode=" Holding ". Do not allow to have the example of value Mode=" Embedding ".

The source endpoint of " Document (document) " by name of relation statement item types " Core.Document " and the target end points of item types " Core.Contact ". Relation has also been stated two adeditive attributes. Relationship example and project are stored dividually and are accessed. All relationship example can be from overall extended view access. Can write all examples that given relationship type is returned in an inquiry.

A given project, all these projects are that the relation in source can be enumerated based on SourceItemID (source item id) attribute of relation. Equally, for a given project, this project is that all relations of target can use TargetItemId (destination item ID) attribute of relation to enumerate in same memory.

A) relation is semantic

Following chapters and sections are described the semanteme of different relationship example modes:

Hold relation: hold the life-span management based on reference count that relation is used for the modelling destination item. A project can be zero or a plurality of source endpoints that are related to project. The project that is not the project of embedding can be one or more related targets of holding. Destination item must with relationship example in same memory.

The relation of holding is implemented the life-span management of target end points. Hold relationship example and be atomic operation as the establishment of the project of target. Can create the additional relation of holding take same project as target. When last have a given project as the target end points hold relationship example when deleted, destination item is also deleted.

The type of the end points project of appointment will be implemented when will create at the example of relation in the relation statement. The type of end points project can not be changed after opening relationships.

Hold to close to tie up to and play the part of a pivotal player when forming WinFS entry name word space. All are held relation and participate in the name space statement. " Name (name) " attribute in the relation statement is relevant to the name of source item order statement destination item. This relevant name is unique and can not is null for the relation of holding that all are derived from a given project. The sequence table that has of this relevant name begins the given project that forms the complete name of project to from root Element.

The relation of holding forms directed acyclic graph (DAG). When the relation held created, system guaranteed not produce circulation, thereby the Guarantee item name space forms DAG. For the more information of WinFS name space and item Path, with reference to " WinFS name space " standard.

Embed relation: the concept of the Absolute control in the life-span of embedding relational model destination item. They support compound term purpose concept. Embed relationship example and be atomic operation as the establishment of the project of target. A project can be the source of zero or a plurality of embedding relations. Yet project can be one and target that embeds relation only. Project as the target that embeds relation can not be to hold related target. Destination item must with relationship example in same memory.

Implement when the end points item types of appointment will be created at the example of relation in the relation statement. The type of end points project can not change after opening relationships. The relation of embedding does not participate in the WinFS name space. Name (name) property value that embeds relation must be null.

Quote relation: the relation of quoting is not controlled the life-span of the project that it quotes. The relation of quoting does not guarantee the existence of target, does not guarantee the target type such as appointment in the relation statement yet. This means that the relation of quoting can imagine. And the relation of quoting can be quoted the project in other WinFS memory.

The relation of quoting in WinFS will be for the relation of most of non-life-span managements between the modelling project. Owing to do not force the existence of target, therefore quote the relation that relation is convenient to the modelling loose coupling. The relation of quoting can be used at other WinFS memory destination item of (comprise and be stored in other machine). The relation of embedding does not participate in the WinFS name space. The value that embeds Name (name) attribute of relation must be null.

B) relation rule and constraint

The additional Rule and constraint of the below is applicable to relation:

A project must be the target of (embedding relation with regard to one) or (one or more holds relation). An exception is root Element. A project can be zero or a plurality of targets of quoting relation.

Concern that as embedding the project of target can not be to hold related source. It can be the source of quoting relation.

A project can not be to hold related source, if it promotes from file. It can be the source that embeds relation and quote relation.

A project that promotes from file can not be the target that embeds relation.

When relationship type A is when deriving from the base relationship type B, following rule is applicable:

Relationship type A can further limit endpoint type. Endpoint type must be the subtype of the corresponding endpoint type among the base relationship B. If end points is further limited, then be necessary for new name of this end points statement. If do not limit end points, then the standard of end points is optional

Relationship type A can further be limited in the example mode that allows of stating in the base relationship. Restricted example mode is gathered the subset of the base type that must be the example type that allows.

The name of end points is considered as the attribute name: name or its base type with the name of attribute or end points is not identical for they.

The source and target element is optional, if corresponding endpoint type is not further limited by the relation that is derived

Here be from concern the example of the statement of the relationship type of deriving at this paper DocumentAuthor defined above (document author):

       <RelationshipType Name＝″LegalDocumentAuthor″

       BaseType＝″Core.DocumentAuthor″

       AllowsHolding＝″false″

       AllowsEmbedding＝″false″

       AllowsReference＝″true″>

         <Source Name＝″LegalDocument″Type＝″Legal.Document″/>

         <Property Name＝″CaseNumber″Type＝″WinFS.String″/>

       </RelationshipType>

LegalDocumentAuthor (legal documents author) relation also limits source endpoint but does not limit the target end points. The source endpoint type is Legal.Document, and it is derived from Core.Document. The target end points is not further limited in this example, has therefore omitted object element. Relation also further limits the example mode that allows. It does not allow the permission mode of Holding (holding) mode and only reservation is to quote.

4. expansion type

The WinFS expansion is that its ancestors are examples of the type of System.Storage.Extension type. This type is the complicated type for the root of expansion type series.

System.Storage.Extension defines two attributes:

ItemID (item id)-with the ItemID (item id) of the project that is associated of expansion

ExtensionID (Extended ID)--expansion is relevant to the unique identifier of ItemID (item id). (ItemID (item id), ExtensionID (Extended ID)) is to unique identification expansion example.

Following restriction is applicable to expansion type:

The expansion type example can not be independent of project and exist. Having same ItemID (item id) must be present in the memory before the expansion type example creates as the item types example of expanding ItemID (item id). Do not exist if having the project of given ItemID (item id), then can not create expansion. When this project was deleted, all expansions with same ItemID (item id) were deleted.

At the most example of a given last derivation expansion type can be associated with an independent project.

Expansion can not be the source and target of relation.

Not constraint on the type of the expansion that can be associated with given item types. Allow any expansion type to expand any item types. When the Multi-instance of different expansion types was attached to a project, they were all irrelevant each other aspect structure and behavior two. Expansion example and project are stored dividually and are accessed. All expansion examples can be from overall extended view access. Can write all examples that the expansion of given type is returned in an inquiry, no matter they are associated with the project of what type. The ItemID (item id) of expansion represents which project they belong to and can be used for retrieving corresponding project object from an overall situation eye diagram. And, a given project, all expansion examples that are associated with this project can use ItemID (item id) attribute of expansion to enumerate.

C. the function that strengthens

In some embodiment of the present invention, hardware/software interface system utilization expansion and succession be so that the relation between the various projects of formalization, thereby strengthen the ability of a plurality of projects of inquiry.

1. inherit

Figure 36 illustrates the subset of a series of projects that connect each other and their relation. Document (document) project 3602 and Contact (contact person) project 3604 are directly to concern that by appointment 3606 is relevant, in this example, concern that 3606 is " author's relations "--namely, Contact (contact person) the 3604th, " author " of Document (document) 3602. In this example, Picture (photo) project 3622, Music (music) project 3624 and Special (special) project 3626 are all inherited from Document (document) project 3604, because the type of each project is the subtype of Document (document) item types. Equally, Person (individual) project 3642 and Organization (tissue) project 3644 are inherited from Contact (contact person) project 3604. In some embodiment of the present invention, the project of these successions (Person (individual) 3622, Music (music) 3624, Special (special) 3626, Person (individual) 3642 and Organization (tissue) 3644) is not only inherited the attribute of corresponding parents' project (Document (document) 3602 and Contact (contact person) 3604), and they also inherit the relation of appointment between these two parents' projects. For example, Person (individual) 3622 inherit with Contact (contact person) 3664 concern 3662, with Person (individual) 3642 concern 3664 and with Organization (tissue) 3644 concern 3666. Similar set of relationship also by shown in each other project inherit.

Yet, be important to note that, concern that inheritance is not to occur automatically and not in each context. For example, describe when a type can itself can not be inherited by heritable attribute (that is, inheritance control). The inheritance parameter is preserved and is adjusted by hardware/software interface system.

2. expansion

Figure 37 A illustrates the shortcoming be used to the standard subtype of the project of using special-purpose purpose. In this accompanying drawing, Contact (contact person) can be by four application, APP1, APP2, APPX and APPY access. APP1 and APP2 access criteria Contact (contact person), but each needs the contact object (adding additional field) of an expansion APPX and APPY, thereby derive Contact ' and Contact ", they each inherit from Contact (contact person). Yet problem is three different examples that have now basic Contact (contact person) project--one in Contact (contact person), one in Contact ', and one at Contact " in.

The part solution of this problem shown in Figure 37 B, be expanded the attribute of Contact (contact person) to comprise the needed field of the such application of requirement. In this case, expansion Contact (contact person) is to comprise the added field that is required by APPX. Yet, directly expand the field of project a such as Contact (contact person) and can only carry out once, thereby APPY can not use this method.

In one embodiment of the invention, more fully solution is to use the expansion different and independent from Contact (contact person) itself to expand Contact (contact person). Like this, APPX can expand Contact (contact person) to comprise its APPX added field, and APPY also can expand Contact (contact person) to comprise its APPY added field simultaneously. Subsequently these expansions be can search for and can inquire about, and thereby these expansions support multiple typed form to be used for hardware/software interface system.

IV. conclusion

Shown in before, the present invention is directed to the storage platform for tissue, search and shared data. The concept of the data storage outside existing file system and the Database Systems is expanded and enlarged to storage platform of the present invention, and designed to be used the storage of all types of data, comprise structurized, non-structured or partly-structured data for example concerns (tabular) data, XML, and a kind of data that are known as the new model of project. By the data of its common storage function and medelling, storage platform of the present invention is allowed for the more effective application and development of client, Knowledge Worker and enterprise. It provides abundant and extendible API, and described interface not only can use performance intrinsic in its data model, and comprises and expanded existing file system and database access method. Be appreciated that in the situation that does not break away from its wide in range inventive concept the change that can carry out above-described embodiment. Therefore, the present invention is not limited to disclosed special embodiment, and is intended to be changed by the institute in the covering the spirit and scope of the present invention of claims defined.

As becoming clearly according to the above, all of various systems of the present invention, method and aspect or a part can embody with the form of program code (that is, instruction). This program code can be stored on the computer-readable medium, magnetic, electricity or the storage medium of light for example, in non-limiting situation, comprise floppy disk, CD-ROM, CD-RW, DVD-ROM, DVD-RAM, tape, flash memory, hard disk drive or other machinable medium, wherein when program code was loaded into machine and for example carries out in computer or the server and by machine, described machine just became be used to implementing device of the present invention. The present invention can also embody with the form of the program code that is transmitted at some transmission mediums, on the transmission medium for example on electric wire or cable, by optical fiber, on network, comprise internet or in-house network, the perhaps transmission by any other form, wherein, received and when being loaded into machine and for example carrying out in the computer and by machine, described machine just becomes be used to implementing device of the present invention when program code. When general processor is implemented, described program code combines with processor, in order to unique device of the operation that is similar to specific logic circuit is provided.

Claims (42)

1. extension purpose method, but described project consists of the discrete memory cell of the information that can be processed by hardware/software interface system, described method comprises that the example (" expansion ") that utilizes strong typing expands described project, but described expansion consists of the discrete memory cell of the information that can be processed by described hardware/software interface system.

2. the method for claim 1 is characterized in that, described expansion is additional to described project.

3. the method for claim 1 is characterized in that, described expansion can not be independent of described project and exist, if thereby described project stop to exist, then described expansion also stops to exist.

4. the method for claim 1 is characterized in that, described project is expanded by a plurality of expansions.

5. method as claimed in claim 4 is characterized in that, described a plurality of expansions are used for the overlapping type instance of modelling.

6. method that is used for extended attribute, described attribute consists of can be by the complex properties type of hardware/software interface system processing, described method comprises utilizes strong typing example (" expansion ") to expand described attribute, but described expansion consists of the discrete memory cell of the information that can be processed by described hardware/software interface system, and is associated with described attribute.

7. method as claimed in claim 6 is characterized in that, described expansion is additional to described attribute.

8. method as claimed in claim 6 is characterized in that, described expansion can not be independent of described attribute and exist, if thereby described attribute stop to exist, then described expansion also stops to exist.

9. method as claimed in claim 6 is characterized in that, described attribute is expanded by a plurality of expansions.

10. method as claimed in claim 9 is characterized in that, described a plurality of expansions are used for the overlapping type instance of modelling.

11. method that is used for hardware/software interface system organization and a plurality of projects of effective query, but described project consists of the discrete memory cell of the information that can be processed by hardware/software interface system, described a plurality of project comprises the first relation, it is relevant with the second project with the first project, described method comprises, instantiation for the 3rd project, the subtype example that described the 3rd project is described the first project, described the 3rd project are automatically from the relation of described the first project succession with described the second project.

12. method as claimed in claim 11 is characterized in that, for the instantiation of the 4th project, and the subtype example that described the 4th project is described the second project, described the 4th project is automatically from the relation of described the second project succession with described the first project.

13. method as claimed in claim 12 is characterized in that, described the 4th project is also automatically from the relation of described the second project succession with described the 3rd project.

14. method as claimed in claim 11, it is characterized in that, for each of more than first subtype example of described the first project, each of described more than first subtype example is automatically inherited relation with described the second described project from described the first project.

15. method as claimed in claim 14, it is characterized in that, for each of more than second subtype example of described the second project, each of described more than second subtype example is automatically inherited relation with described the first described project from described the second project.

16. method as claimed in claim 15 is characterized in that, each of described more than first subtype example is automatically inherited each relation with described more than second subtype example from described the first project.

17. method as claimed in claim 16 is characterized in that, each of described more than second subtype example is automatically inherited each relation with described more than first subtype example from described the second project.

18. the hardware for the treatment of a plurality of projects/software interface system, wherein, but project consists of the discrete memory cell of the information that can be processed by described hardware/software interface system, described system comprises that one is used for coming extension purpose subsystem with strong typing example (" expansion "), but consist of can be by the memory cell that disperses of the information of described hardware/software interface system processing in described expansion.

19. system as claimed in claim 18 is characterized in that, described expansion is additional to described project.

20. system as claimed in claim 18 is characterized in that, described expansion can not be independent of described project and exist, if thereby described project stop to exist, then described expansion also stops to exist.

21. system as claimed in claim 18 is characterized in that, described project is expanded by a plurality of expansions.

22. the hardware for the treatment of a plurality of attributes/software interface system, described attribute consists of can be by the complex properties type of hardware/software interface system processing, described system comprises that one is used for coming with strong typing example (" expansion ") subsystem of extended attribute, but consist of can be by the memory cell that disperses of the information of described hardware/software interface system processing in described expansion.

23. the system as claimed in claim 22 is characterized in that, described expansion is additional to described attribute.

24. the system as claimed in claim 22 is characterized in that, described expansion can not be independent of described attribute and exist, if thereby described attribute stop to exist, then described expansion also stops to exist.

25. the system as claimed in claim 22 is characterized in that, described attribute is expanded by a plurality of expansions.

26. the hardware for the treatment of a plurality of projects/software interface system, wherein, but project consists of the discrete memory cell of the information that can be processed by described hardware/software interface system, described system comprises that one is used for the subsystem of tissue and the described a plurality of projects of effective query, described a plurality of project comprises the first relation, it is relevant with the second project with the first project, wherein, and described subsystem:

For the instantiation of the 3rd project, the subtype example that described the 3rd project is described the first project is automatically set up the relation between described the 3rd project and described the second project;

For the instantiation of the 4th project, the subtype example that described the 4th project is described the second project is automatically set up the relation between described the 4th project and described the first project; And

Automatically set up the relation between described the 4th project and described the first project.

27. system as claimed in claim 26, for each of more than first subtype example of described the first project, and for each of more than second subtype example of described the second project, described subsystem:

Automatically set up each of described more than first subtype example and the relation of described the second project;

Automatically set up each of described more than second subtype example and the relation of described the first project; And

Automatically set up each relation of each and described more than second subtype example of described more than first subtype example;

28. the hardware for the treatment of a plurality of projects/software interface system, wherein, but project consists of the discrete memory cell of the information that can be processed by described hardware/software interface system, described system comprises that one is used for coming extension purpose subsystem with strong typing example (" expansion "), but consist of can be by the memory cell that disperses of the information of described hardware/software interface system processing in described expansion.

29. system as claimed in claim 28 is characterized in that, described expansion is additional to described project.

30. system as claimed in claim 28 is characterized in that, described expansion can not be independent of described project and exist, if thereby described project stop to exist, then described expansion also stops to exist.

31. system as claimed in claim 28 is characterized in that, described project is expanded by a plurality of expansions.

32. the hardware for the treatment of a plurality of attributes/software interface system, described attribute consists of can be by the complex properties type of hardware/software interface system processing, described system comprises that one is used for coming with strong typing example (" expansion ") subsystem of extended attribute, but consist of can be by the memory cell that disperses of the information of described hardware/software interface system processing in described expansion.

33. system as claimed in claim 32 is characterized in that, described expansion is additional to described attribute.

34. system as claimed in claim 32 is characterized in that, described expansion can not be independent of described attribute and exist, if thereby described attribute stop to exist, then described expansion also stops to exist.

35. system as claimed in claim 32 is characterized in that, described attribute is expanded by a plurality of expansions.

36. the hardware for the treatment of a plurality of projects/software interface system, wherein, but project consists of the discrete memory cell of the information that can be processed by described hardware/software interface system, described system comprises that one is used for the subsystem of tissue and the described a plurality of projects of effective query, described a plurality of project comprises the first relation, it is relevant with the second project with the first project, wherein, and described subsystem:

For the instantiation of the 3rd project, the subtype example that described the 3rd project is described the first project is automatically set up the relation between described the 3rd project and described the second project;

For the instantiation of the 4th project, the subtype example that described the 4th project is described the second project is automatically set up the relation between described the 4th project and described the first project; And

Automatically set up the relation between described the 4th project and described the first project;

37. system as claimed in claim 36 is characterized in that, for each of more than first subtype example of described the first project, and for each of more than second subtype example of described the second project, described subsystem:

Automatically set up each of described more than first subtype example and the relation of described the second project;

Automatically set up each of described more than second subtype example and the relation of described the first project; And

Automatically set up each relation of each and described more than second subtype example of described more than first subtype example;

38. one kind comprises the computer-readable medium for extension purpose computer-readable instruction, but described project consists of the discrete memory cell of the information that can be processed by hardware/software interface system, described computer-readable instruction comprises be used to utilizing strong typing example (" expansion ") to expand the instruction of described project, but described expansion consists of the discrete memory cell of the information that can be processed by described hardware/software interface system, wherein, described expansion is additional to described project, and wherein, described expansion also stops to exist when described project stops to exist.

39. one kind comprises the computer-readable medium for the computer-readable instruction of extended attribute, described attribute consists of can be by the complex properties type of hardware/software interface system processing, described computer-readable instruction comprises be used to utilizing strong typing example (" expansion ") to expand the instruction of described attribute, but described expansion consists of the discrete memory cell of the information that can be processed by described hardware/software interface system, wherein, described expansion is additional to described attribute, and wherein, described expansion also stops to exist when described attribute stops to exist.

40. one kind comprises the computer-readable medium for the computer-readable instruction of tissue and a plurality of projects of effective query, but described project consists of the discrete memory cell of the information that can be processed by hardware/software interface system, described computer-readable instruction comprises instruction, is used for:

Instantiation the first project, the second project and the first relation that the first project is relevant with the second project;

Instantiation the 3rd project, the subtype example that described the 3rd project is described the first project; And

Automatically set up the relation of the succession between described the 3rd project and described the second project.

41. computer-readable medium as claimed in claim 40 is characterized in that, also comprises being used for instruction:

Instantiation the 4th project, the subtype example that described the 4th project is described the second project; And

Automatically set up the relation of the succession between described the 4th project and described the first project.

42. computer-readable medium as claimed in claim 41 is characterized in that, also comprises instruction, is used for automatically setting up the relation of the succession between described the 3rd project and described the 4th project.

Images