WinFS

**WinFS** (short for *Windows Future Storage*) is the code name for a data storage and management system based on relational databases, developed by Microsoft and first demonstrated in 2003 as an advanced storage subsystem for the Microsoft Windows operating system, designed for persistence and management of structured, semi-structured as well as unstructured data.

WinFS includes a relational database for storage of information, and allows any type of information to be stored in it, provided there is a well defined schema for the type. Individual data items could then be related together by relationships, which are either inferred by the system based on certain attributes or explicitly stated by the user. As the data has a well defined schema, any application can reuse the data; and using the relationships, related data can be effectively organized as well as retrieved. Because the system knows the structure and intent of the information, it can be used to make complex queries that enable advanced searching through the data and aggregating various data items by exploiting the relationships between them.

 File:WinFSCalendar.png
While WinFS and its shared type schema make it possible for an application to recognize the different data types, the application still has to be coded to render the different data types. Consequently, it would not allow development of a single application that can view or edit all data types; rather what WinFS enables applications to understand is the structure of all data and extract the information that it can use further. When WinFS was introduced at the 2003 Professional Developers Conference, Microsoft also released a video presentation, named IWish, showing mockup interfaces that showed how applications would expose interfaces that take advantage of a unified type system. The concepts shown in the video ranged from applications using the relationships of items to dynamically offer filtering options to applications grouping multiple related data types and rendering them in a unified presentation.

WinFS was billed as one of the pillars of the "Longhorn" wave of technologies, and would ship as part of the next version of Windows. It was subsequently decided that WinFS would ship after the release of Windows Vista, but those plans were shelved in June 2006, with some of its component technologies being integrated into upcoming releases of ADO.NET and Microsoft SQL Server. While it was then assumed by observers that WinFS was finished as a project, in November 2006 Steve Ballmer announced that WinFS was still in development, though it was not clear how the technology was to be delivered.

## Motivation

Many filesystems found on common operating systems, including the NTFS filesystem which is used in modern versions of Microsoft Windows, store files and other objects only as a stream of bytes, and have little or no information about the data stored in the files. Such file systems also provide only a single way of organizing the files, namely via directories and file names.

Because a file system has no knowledge about the data it stores, applications tend to use their own, often proprietary, file formats. This hampers sharing of data between multiple applications. It becomes difficult to create an application which processes information from multiple file types, because the programmers have to understand the structure and semantics of all the files. Using common file formats is a workaround to this problem but not a universal solution; there is no guarantee that all applications will use the format. Data with standardized schema, such as XML documents and relational data fare better, as they have a standardized structure and run-time requirements.

Also, a traditional file system can retrieve and search data based only on the filename, because the only knowledge it has about the data is the name of the files that store the data. A better solution is to tag files with attributes that describe them. Attributes are metadata about the files such as the type of file (such as *document*, *picture*, *music*, *creator*, etc.). This allows files to be searched for by their attributes, in ways not possible using a folder hierarchy, such as finding *"pictures which have person X"*. The attributes can be recognizable by either the file system natively, or via some extension. Desktop search applications take this concept a step further. They extract data, including attributes, from files and index it. To extract the data, they use a filter for each file format. This allows for searching based on both the file's attributes and the data in it.

However, this still does not help in managing related data, as disparate items do not have any relationships defined. For example, it is impossible to search for *"the phone numbers of all persons who live in Acapulco and each have more than 100 appearances in my photo collection and with whom I have had e-mail within last month"*. Such a search could not be done unless it is based on a data model which has both the semantics as well as relationships of data defined. WinFS aims to provide such a data model and the runtime infrastructure that can be used to store the data, as well as the relationships between data items according to the data model, doing so at a satisfactory level of performance.

## Overview

WinFS natively recognizes different types of data, such as *picture*, *e-mail*, *document*, *audio*, *video*, *calendar*, *contact*, among others; rather than just leaving them as raw unanalyzed bytestreams (as most file systems do). Data stored and managed by the system are instances of the data type recognized by the WinFS runtime. The data are structured by means of properties. For example, an instance of a *résumé* type will surface the data by exposing certain properties like *Name*, *Educational Qualification*, *Experience*, among others. Each of the properties may be of simple types like *strings*, *integers*, or *dates* or complex types like *contacts*. Different data types expose different properties. Besides that, WinFS also allows different data instances to be related together, such as a document and a contact can be related by an *Authored By* relationship. Relationships are also exposed as properties; for example if a document is related to a contact by a *Created By* relationship, then the document will have a *Created By* property. When it is accessed, the relationship is traversed and the related data returned. By following the relations, all related data can be reached.
WinFS promotes sharing of data between applications by making the data types accessible to all applications, along with their schemas. So any application, when it wants to use a WinFS type, by using the schema can find out the structure of the data and utilize the information. So, an application has access to all data on the system, even though the developer did not have to write parsers to recognize the different data formats. It can also use the relationships and related data to create dynamic filters to present the information the application deals with, in different ways. The WinFS API further abstracts the task of accessing data. All WinFS types are exposed as .NET objects with the properties of the object directly mapping to the properties of the data type. Also, by letting different applications which deal with the same data share the same WinFS data instance rather than storing the same data in different files, the hassles of synchronizing the different stores when the data change are removed. Thus WinFS can reduce redundancies.

Access to all the data in the system allows complex searches for data to be performed across all the data items managed by WinFS. In the example used above (*"the phone numbers of all persons who live in Acapulco and each have more than 100 appearances in my photo collection and with whom I have had e-mail within last month"*), WinFS can traverse the *subject* relationship of all the photos to find the *contact* items. Similarly, it can filter all emails in last month and access the *communicated with* relation to reach the contacts. The common contacts can then be figured out from the two sets of results and their phone number retrieved by accessing the suitable property of the contact items.

WinFS, in addition to fully schematized data (like XML and relational data), supports semi-structured (like images, which has an unstructured bitstream plus structured metadata) as well as unstructured (like files) as well. It stores the unstructured components directly as files while storing the structured metadata in the structured store. Internally, WinFS uses a relational database to manage data. However, it does not limit the data to belonging to any particular data model, like relational or hierarchical, but can be of any well-defined schema. The WinFS runtime maps the schema to a relational modality, by defining the tables it will store the types in and the primary keys and foreign keys that would be required to represent the relationships. WinFS includes mappings for object and XML schemas by default; mappings for other schemas needs to be specified. Object schemas are specified using XML; WinFS generates code to surface the schemas as .NET classes. ADO.NET can be used to directly specify the relational schema, though a mapping to the object schema needs to be provided to surface it as classes. All relationship traversals are performed as joins on these tables. WinFS also automatically creates indexes on these tables, to facilitate fast access to the information. Indexes significantly speed up joins, and thus traversing relationships to retrieve related data is performed very fast. Indexes are also used during searching of information; searching and querying use the indexes so that the operations complete quickly, much like desktop search systems.

## Development

Template:Graphical timeline
The development of WinFS is an extension to a feature which was initially planned in the early 1990s. Dubbed *Object File System*, it was supposed to be included as part of Cairo. OFS was supposed to have powerful data aggregation features,  but the Cairo project was shelved, and with it OFS. However, later during the development of COM, a storage system, called Storage+, based on then-upcoming SQL Server 8.0, was planned, which was slated to offer similar aggregation features. This, too, never materialized, and a similar technology, *Relational File System* (RFS), was conceived to be launched with SQL Server 2000. However, SQL Server 2000 ended up being a minor upgrade to SQL Server 7.0 and RFS was not implemented.

But the concept was not scrapped. It just morphed into WinFS. WinFS was initially planned for inclusion in Windows Vista, and build 4051 of Windows Vista, then called by its codename "Longhorn", given to developers at the Microsoft Professional Developers Conference in 2003, included WinFS, but it suffered from significant performance issues. In August 2004, Microsoft announced that WinFS would not ship with Windows Vista; it would instead be available as a downloadable update after Vista's release.

On August 29, 2005, Microsoft quietly made Beta 1 of WinFS available to MSDN subscribers. It worked on Windows XP, and required the .NET Framework to run. The WinFS API was included in the *System.Storage* namespace. The beta was refreshed on December 1, 2005 to be compatible with version 2.0 of the .NET Framework. WinFS Beta 2 was planned for some time later in 2006, and was supposed to include integration with Windows Desktop Search, so that search results include results from both regular files and WinFS stores, as well as allow access of WinFS data using ADO.NET.

However, on June 23, 2006, the WinFS team at Microsoft announced that WinFS would no longer be delivered as a separate product, and some components would be brought under the umbrella of other technologies - like the object-relational mapping components into ADO.NET Entity Framework; support for unstructured data, adminless mode of operation, support for file system objects via the FILESTREAM data type, and hierarchical data in SQL Server 2008, then codenamed *Katmai*, as well as integration with Win32 APIs and Windows Shell and support for traversal of hierarchies by traversing relationships into later releases of Microsoft SQL Server; and the synchronization components into Microsoft Sync Framework. However, having a shared-schema storage system built into a future iteration of Microsoft Windows has not yet been ruled out.

With that announcement, most analysts assumed that the WinFS project was being killed off. But in November 2006, Steve Ballmer said in an interview that WinFS is being actively developed but integration into the Windows codebase will come only after the technology has fully incubated. It was subsequently confirmed in an interview with Bill Gates and that Microsoft plans to migrate applications like Windows Media Player, Windows Photo Gallery, Microsoft Office Outlook etc. to use WinFS as the data storage back-end.

## Data storage

### Architecture

 File:WinFSArch.svg
WinFS uses a relational engine, which is derived from SQL Server 2005, to provide the data relations mechanism. WinFS stores are simply SQL Server database (.MDF) files with the FILESTREAM attribute set. These files are stored in access-restricted folder named "System Volume Information" placed into the volume root, in folders under the folder "WinFS" with names of GUIDs of these stores.

At the bottom of the WinFS stack lies *WinFS Core* which interacts with the filesystem and provides file access and addressing capabilities. The relational engine leverages the WinFS core services to present a structured store and other services such as locking which the WinFS runtime uses to implement the functionality. The WinFS runtime expose *Services* such as *Synchronization* and *Rules* which can be used to synchronize WinFS stores or perform certain actions on the occurrence of certain events.

WinFS runs as a service which runs three processes - *WinFS.exe*, which hosts relational datastore, *WinFSSearch.exe*, which hosts the indexing and querying engine, and *WinFPM.exe (WinFS File Promotion Manager)*, which interfaces with the underlying file system. It allows programmatic access to its features, via a set of .NET Framework APIs, that enables applications to define custom made data types, define relationships among data, store and retrieve information, and allow advanced searches. The applications can then aggregate the data and present the aggregated data to the user.

#### Data store

WinFS stores data in relational stores, which are exposed as virtual locations called *stores*. A WinFS store is a common repository where any application can store data along with its metadata, relationships and schema. WinFS runtime can apply certain relationships itself; for example, if the values of the *subject* property of a picture and the *name* property of a contact are same, then WinFS can relate the contact with the picture. Relations can also be specified by other applications or the user.

WinFS provides a unified storage, but stops short of defining the format that is to be stored in the data stores. Instead it supports data to be written in application specific formats. But applications must provide a schema that defines how the file format should be interpreted. For example, a schema could be added to allow WinFS to understand how to read and thus be able to search and analyze, say, a PDF file. By using the schema, any application can read data from any other application, and also allows different applications to write in each other’s format by sharing the schema.

Multiple WinFS stores can be created on a single machine. This allows different classes of data to be kept segregated; for example, official documents and personal documents can be kept in different stores. WinFS, by default, provides only one store, named "DefaultStore". WinFS stores are exposed as shell objects, akin to Virtual folders, which dynamically generates a list of all items present in the store and presents them in a folder view. The shell object also allows searching information in the datastore.

A data unit that has to be stored in a WinFS store is called a WinFS *Item*. A WinFS item, along with the core data item, also contains information on how the data item is related to other data. This *Relationship* is stored in terms of logical links. Links specify which other data items the current item is related with. Put in other words, links specify the relationship of the data with other data items. Links are physically stored using a link identifier, which specifies the name and intent of the relationship, such as *type of* or *consists of*. The link identifier is stored as an attribute of the data item. All the objects which have the same link id are considered to be related. An XML schema, defining the structure of the data items that will be stored in WinFS, must be supplied to the WinFS runtime beforehand. In Beta 1 of WinFS, the schema assembly had to be added to the GAC before it could be used.

### Data model

WinFS models data using the data items, along with their relationships, extensions and rules governing its usage. WinFS needs to understand the type and structure of the data items, so that the information stored in the data item can be made available to any application that requests it. This is done by the use of schemas. For every type of data item that is to be stored in WinFS, a corresponding schema needs to be provided to define the type, structure and associations of the data. These schemas are defined using XML.

Predefined WinFS schemas include schemas for documents, e-mail, appointments, tasks, media, audio, video, and also includes system schemas that include configuration, programs, and other system-related data. Custom schemas can be defined on a per-application basis, in situations where an application wants to store its data in WinFS, but not share the structure of that data with other applications, or they can be made available across the system.

#### Type system

 File:WinFS1.svg
The most important difference between a file system and WinFS is that WinFS knows the type of each data item that it stores. And the type specifies the properties of the data item. The WinFS type system is closely associated with the .NET framework’s concept of classes and inheritance. A new type can be created by extending and nesting any predefined types.

WinFS provides four predefined base types – *Items*, *Relationships*, *ScalarTypes* and *NestedTypes*. An Item is the fundamental data object which can be stored, and a Relationship is the relation or link between two data items. Since all WinFS items must have a type, the type of item stored defines its properties. The properties of an Item may be a ScalarType, which defines the smallest unit of information a property can have, or a NestedType, which is a collection of more than one ScalarTypes and/or NestedTypes. All WinFS types are made available as .NET CLR classes.

Any object represented as a data unit, such as contact, image, video, document etc., can be stored in a WinFS store as a specialization of the Item type. By default, WinFS provides Item types for Files, Contact, Documents, Pictures, Audio, Video, Calendar, and Messages. The File Item can store any generic data, which is stored in file systems as files. But unless an advanced schema is provided for the file, by defining it to be a specialized Item, WinFS will not be able to access its data. Such a file Item can only support being related to other Items.

 File:WinFS2.svg
A developer can extend any of these types, or the base type Item, to provide a type for his custom data. The data contained in an Item is defined in terms of properties, or fields which hold the actual data. For example, an Item *Contact* may have a field *Name* which is a ScalarType, and one field *Address*, a NestedType, which is further composed of two ScalarTypes. To define this type, the base class Item is extended and the necessary fields are added to the class. A NestedType field can be defined as another class which contains the two ScalarType fields. Once the type is defined, a schema has to be defined, which denotes the primitive type of each field, for example, the Name field is a String, the Address field is a custom defined Address class, both the fields of which are Strings. Other primitive types that WinFS supports are Integer, Byte, Decimal, Float, Double, Boolean and DateTime, among others. The schema will also define which fields are mandatory and which are optional. The Contact Item defined in this way will be used to store information regarding the Contact, by populating the properties field and storing it. Only those fields marked as mandatory needs to be filled up during initial save. Other fields may be populated later by the user, or not populated at all. If more properties fields, such as *last conversed date*, need to be added, this type can be extended to accommodate them. Item types for other data can be defined similarly.

 File:WinFS3.svg
WinFS creates tables for all defined Items. All the fields defined for the Item form the columns of the table and all instances of the Item are stored as rows in the table for the respective Items. Whenever some field in the table refers to data in some other table, it is considered a relationship. The schema of the relationship specifies which tables are involved and what the kind and name of the relationshp is. The WinFS runtime manages the relationshp schemas. All Items are exposed as .NET CLR objects, with a uniform interface providing access to the data stored in the fields. Thus any application can retrieve object of any Item type and can use the data in the object, without being aware of the physical structure the data was stored in.

WinFS types are exposed as .NET classes, which can be instantiated as .NET objects. Data are stored in these type instances by setting their properties. Once done, they are persisted into the WinFS store. A WinFS store is accessed using an *ItemContext* class (see Data retrieval section for details). ItemContext allows transactional access to the WinFS store; i.e. all the operations since binding an ItemContext object to a store till it is closed either all succeed or are all rolled back. As changes are made to the data, they are not written to the disc; rather they are written to an in-memory log. Only when the connection is closed are the changes written to the disc in a batch. This helps to optimize disc I/O. The following code snippet, written in C#, creates a contact and stores it in a WinFS store.

```
 //Connect to the default WinFS store
 using(ItemContext ic = ItemContext.Open())
 {
 //Create the contact and set the data in appropriate properties
 ContactEAddress contact = new ContactEAddress();

 //Name is a ComplexType
 contact.Name = new PersonName();
 contact.Name.Displayname = "Doe, John";
 contact.Name.FirstName = "John";
 contact.Name.LastName = "Doe";

 //Telephone number is a ComplexType
 contact.TelephoneNumber = new TelephoneNumber(); //ComplexType
 contact.TelephoneNumber.Country = CountryCode.Antarctica;
 contact.TelephoneNumber.Areacode = 4567;
 contact.TelephoneNumber.Number = 9876543210;

 //Age is a SimpleType
 contact.Age = 111;

 //Add the object to the user's personal folder.
 //This relates the item with the Folder pseudo-type, for backward
 //compatibility, as this lets the item to be accessed in a folder
 //hierarchy for apps which are not WinFS native.
 Folder containingFolder = UserDataFolder.FindMyPersonalFolder();
 containingFolder.OutFolderMemberRelationship.AddItem(ic, contact);

 //Find a document and relate with the document. Searching begins by creating an
 //ItemSearcher object. Each WinFS type object contains a GetSearcher() method
 //that generates an ItemSearcher object which searches documents of that type.
 using (ItemSearcher searcher = Document.GetSearcher(ic))
 {
 Document d = searcher.Find(@"Title = 'Some Particular Document'");
 d.OutAuthoringRelationship.AddItem(ic, contact);
 }
 //Since only one document is to be found, the ItemContext.FindOne() method
 //could be used as well.

 //Find a picture and relate with it
 using (ItemSearcher searcher = Picture.GetSearcher(ic))
 {
 Picture p = searcher.Find(@"Occasion = 'Graduation' and Sequence = '3'");
 p.OutSubjectRelationship.AddItem(ic, contact);
 }

 //Persist to the store and close the reference to the store
 ic.Update();
 ic.Close();
 }

```

#### Relationships

A datum can be related to one more item, giving rise to a one-to-one relationship, or with more than one items, resulting in a one-to-many relationship. The related items, in turn, may be related to other data items as well, resulting in a network of relationships, which is called a many-to-many relationship. Creating a relationship between two Items create another field in the data of the Items concerned which refer the row in the other Item’s table where the related object is stored.

 File:WinFS4.svg
In WinFS, a Relationship is an instance of the base type Relationship, which is extended to signify a specialization of a relation. A Relationship is a mapping between two items, a Source and a Target. The source has an Outgoing Relationship, whereas the target gets an Incoming Relationship. WinFS provides three types of primitive relationships – *Holding Relationship*, *Reference Relationship* and *Embedding Relationship*. Any custom relationship between two data types are instances of these relationship types.

* **Holding Relationships** specifies ownership and lifetime (which defines how long the relationship is valid) of the Target Item. For example, the Relationship between a folder and a file, and between an Employee and his Salary record, is a Holding Relationship – the latter is to be removed when the former is removed. A Target Item can be a part of more than one Holding Relationships. In such a case, it is to be removed when all the Source Items are removed.
* **Reference Relationships** provide linkage between two Items, but do not have any lifetime associated, i.e., each Item will continue to be stored even without the other.
* **Embedding Relationships** give order to the two Items which are linked by the Relationship, such as the Relationship between a Parent Item and a Child Item.

Relationships between two Items can either be set programmatically by the application creating the data, or the user can use the WinFS Item Browser to manually relate the Items. A WinFS item browser can also graphically display the items and how they are related, to enable the user to know how their data are organized.

#### Rules

WinFS includes *Rules*, which are executed when a certain condition is met. WinFS rules work on data and data relationships. For example, a rule can be created which states that whenever an Item is created which contains field *"Name"* and if the value of that field is some particular name, a relationship should be created which relates the Item with some other Item. WinFS rules can also access any external application. For example, a rule can be built which launches a *Notify* application whenever a mail is received from a particular contact. WinFS rules can also be used to add new properties fields to existing data Items.

WinFS rules are also exposed as .NET CLR objects. As such any rule can be used for any purpose. A rule can even be extended by inheriting from it to form a new rule which consists of the condition and action of the parent rule plus something more.

### RAV

WinFS supports creating *Rich Application Views* (RAV) by aggregating different data in a virtual table format. Unlike database view, where each individual element can only be a scalar value, RAVs can have complex Items or even collection of Items. The actual data can be across multiple data types or instances and can even be retrieved by traversing relationships. RAVs are intrinsically paged (dividing the entire set of data into smaller *pages* containing disconnected subsets of the data) by the WinFS runtime. The page size is defined during creation of the view and the WinFS API exposes methods to iterate over the pages. RAVs also supports modification of the view according to different grouping parameters. Views can also be queried against.

### Access control

Even though all data are shared, everything is not equally accessible. WinFS uses the Windows authentication system to provide two data protection mechanisms. First, there is share-level security that controls access to your WinFS share. Second, there is item level security that supports NT compatible security descriptors. The process accessing the item must have enough privileges to access it. Also in Vista there is the concept of *"integrity level"* for an application. Higher integrity data cannot be accessed by a lower integrity process.

## Data retrieval

 File:WinFSFlowChart.svg
The primary mode of data retrieval from a WinFS store is querying the WinFS store according to some criteria, which returns an enumerable set of items matching the criteria. The criteria for the query is specified using the OPath query language. The returned data are made available as instances of the type schemas, conforming to the .NET object model. The data in them can be accessed by accessing the properties of individual objects.

Relations are also exposed as properties. Each WinFS Item has two properties, named *IncomingRelationships* and *OutgoingRelationships*, which provides access to the set of relationship instances the item participates in. The other item which participates in one relationship instance can be reached through the proper relationship instance.

The fact that the data can be accessed using its description, rather than location, can be used to provide end-user organizational capabilities without limiting to the hierarchical organization as used in file-systems. In a file system, each file or folder is contained in only one folder. But WinFS Items can participate in any number of holding relationships, that too with any other items. As such, end users are not limited to only file/folder organization. Rather, a contact can become a container for documents; a picture a container for contacts and so on. For legacy compatibility, WinFS includes a pseudo-type called *Folder* which is present only to participate in holding relationships and emulate file/folder organization. Since any WinFS Item can be related with more than one Folder item, from an end user perspective, an item can reside in multiple folders without duplicating the actual data. Applications can also analyze the relationship graphs to present various filters. For example, an email application can analyze the related contacts and the relationships of the contacts with restaurant bills and dynamically generate filters like *"Emails sent to people I had lunch with"*.

### Searches

The WinFS API provides a class called the *ItemContext* class, which is bound to a WinFS store. The *ItemContext* object can be used to scope the search to the entire store or a subset of it. It also provides transactional access to the store. An object of this class can then spawn an *ItemSearcher* object which then takes the type (an object representing the type) of the item to be retrieved or the relationship and the OPath query string representing the criteria for the search. A set of all matches are returned, which can then be bound to an UI widget for displaying *en masse* or enumerating individually. The properties items can also be modified and then stored back to the data store to update the data. The ItemContext object is *closed* (which marks the end of association of the object with the store) when the queries are made or changes merged into the store.

Related items can also be accessed through the items. The *IncomingRelationships* and *OutgoingRelationships* properties gives access to all the set of relationship instances, typed to the name of the relationship. These relationship objects expose the other item via a property. So, for example, if a picture is related to a picture, it can be accessed by *traversing* the relationship as:

```
 ContactsCollection contacts = picture.OutgoingRelationships.Cast(typeof(Contact)).Value;
 //This retrieves the collection of all outgoing relationships from a picture object
 //and filters down the contacts reachable from them and retrieves its value.

 //Or the relationship can be statically specified as
 ContactsCollection contacts = picture.OutgoingRelationships.OutContactRelationship.Contact;

```

```
 using ( ItemContext ic = ItemContext.Open() )
 {
 //Searching begins by creating a ItemSearcher object. The searcher is created from a
 //relationship instance because the contacts being searched for are in relation. The
 //first parameter defines the scope of the search. An ItemContext as the scope means
 //the entire store is to be searched. Scope can be limited to a set of Items which may
 //be in a holding relationship with the contacts. In that case, the set is passed as
 //the scope of the search.
 ItemSearcher searcher = OutContactRelationship.GetTargetSearcher(ic, typeof(Contact));
 ContactCollection contacts = searcher.FindAll("OutContactRelationship.Contact.Name LIKE 'A\*'");
 ic.Close();
 }

```

The above code snippet creates an ItemSearcher object that searchs on the *OutContactRelationship* instance that relates pictures and contacts, in effect searching all pictures related with a contact. It then runs the query *Name LIKE 'A\*'"* on all contacts reachable through *OutContactRelationship*, returning the list of *"contacts whose names start with A and whose pictures I have"*. Similarly more relationships could be taken into account to further narrow down the results. Further, a natural language query processor, which parses query in natural language and creates a well-formed OPath query string to search via proper relationships, can allow users to make searches such as *"find the name of the wine I had with person X last month"*, provided financial management applications are using WinFS to store bills.

Different relations specify a different set of data. So when a search is made which encompasses multiple relations, the different sets of data are retrieved individually and a union of the different sets is computed. The resulting set contains only those data items which correspond to all the relations.

### Notifications

WinFS also includes better support for handling data that changes frequently. Using WinFS *Notifications*, applications choose to be notified of changes to selected data *Items*. WinFS will raise an *ItemChangedEvent*, using the .NET Event model, when a subscribed-to Item changes, and the event will be published to the applications.

## Data sharing

WinFS allows easy sharing of data between applications, and among multiple WinFS stores, which may reside on different computers, by copying to and from them. A WinFS item can also be copied to a non-WinFS file system, but unless that data item is put back into the WinFS store, it will not support the advanced services provided by WinFS.

The WinFS API also provides some support for sharing with non-WinFS applications. WinFS exposes a shell object to access WinFS stores. This object maps WinFS items to a virtual folder hierarchy, and can be accessed by any application. WinFS data can also be manually shared using network shares, by sharing the legacy shell object. Non-WinFS file formats can be stored in WinFS stores, using the File Item, provided by WinFS. Importers can be written, to convert specific file formats to WinFS Item types.

In addition, WinFS provides services to automatically synchronize items in two or more WinFS stores, subject to some predefined condition, such as "*share only photos*" or "*share photos which have an associated contact X*". The stores may be on different computers. Synchronization is done in a peer-to-peer fashion; there is no central authority. A synchronization can be either manual or automatic or scheduled. During synchronization, WinFS finds the new and modified Items, and updates accordingly. If two or more changes conflict, WinFS can either resort to automatic resolution based on predefined rules, or defer the synchronization for manual resolution. WinFS also updates the schemas, if required.

## Application support

### Shell namespace

WinFS Beta 1 includes a shell namespace extension, which surfaces WinFS stores as top level objects in *My Computer* view. Files can be copied into and out of the stores, as well as applications can be directly used to save there. Even folders such as *My Documents* can be redirected to the stores. WinFS uses *Importer* plug-ins to analyze the files as they were being imported to the store and create proper WinFS schemas and objects, and when taking the objects out, re-pack them into files. If importers for certain files are not installed, they are stored as generic *File* types.

### Microsoft Rave

*Microsoft Rave* is an application that shipped with WinFS Beta 1. It allows synchronization of two or more WinFS stores, and supports synchronization in *full mesh* mode as well as the *central hub* topology. While synchronizing, Microsoft Rave will determine the changes made to each store since the last sync, and update accordingly. When applying the changes, it also detects if there is any conflict, i.e., the same data has been changed on both stores since the last synchronization. It will either log the conflicting data for later resolution or have it resolved immediately. Microsoft Rave uses peer-to-peer technology to communicate and transfer data.

### StoreSpy

 File:Storespy.jpg
With WinFS Beta 1, Microsoft included an unsupported application called *StoreSpy*, which allowed one to browse WinFS stores by presenting a hierarchical view of WinFS Items. It automatically generated virtual folders based on access permissions, date and other metadata, and presented them in a hierarchical tree view, akin to what traditional folders are presented in. The application generated tabs for different Item types. StoreSpy allowed viewing *Items*, *Relationships*, *MultiSet*, *Nested Elements*, *Extensions* and other types in the store along with its full metadata. It also presented a search interface to perform manual searches, and save them as virtual folders. The application also presented a graphical view of WinFS Rules. However, it did not allow editing of Items or their properties, though it was slated for inclusion in a future release. But the WinFS project was cut back before it could materialize.

### Type Browser

WinFS also includes another application, named *WinFS Type Browser*, which can be used to browse the WinFS types, as well as visualize the hierarchical relationship between WinFS types. A WinFS type, both built-in types as well as custom schemas, can be visualized along with all the properties and methods that it supports. It also shows the types that it derives from as well as other types that extend the type schema. However, while it was included with WinFS, it was released as an unsupported tool.

### OPather

WinFS Beta 1 also includes an unsupported application, named *OPather*. It presents a graphical interface for writing Opath queries. It can be used by selecting target object type and specifying the parameters of the query. It also includes Intellisense-like parameter completion feature. It can then be used to perform visualization tasks like binding results of a query to a *DataGrid* control, create views of the data in WinFS itself, or just extract the query string.

### Project "Orange"

Microsoft launched a project to build a data visualization application for WinFS. It was codenamed *"Project Orange"* and was supposedly built using Windows Presentation Foundation. It was supposed to provide exploration of *Items* stored in WinFS stores, and data relationships were supposed to be a prominent part of the navigation model. It was supposed to let people allow organization of the WinFS stores graphically as well – productizing many of the concepts shown in the IWish Concept Video. However, since the WinFS project went dark, the status of this project is unknown.

## See also

* Desktop organizer
* Relational Database Management System
* Storage, a storage management system for GNOME desktop
* NEPOMUK-KDE

## References

1. ↑ "Leaked Windows hints at changes to come". http://news.zdnet.co.uk/software/0,1000000121,2131385,00.htm. Retrieved 2007-05-04.
2. ↑ "IWish Concept Video". Microsoft. http://download.microsoft.com/download/c/e/2/ce28874c-4f44-4dbd-babb-727685e2be96/WinFS\_IWish\_720x486\_2mbs.wmv. Retrieved 2008-07-14.
3. ↑ 3.0 3.1 Quentin Clark (June 23, 2006). "WinFS Update". *What's in Store*. MSDN Blogs. http://blogs.msdn.com/winfs/archive/2006/06/23/644706.aspx. Retrieved 2006-06-23.
4. ↑ "WinFS Still In The Works Despite Missing Vista". http://www.crn.com/software/196600671. Retrieved 2007-06-30.
5. ↑ 5.00 5.01 5.02 5.03 5.04 5.05 5.06 5.07 5.08 5.09 5.10 5.11 5.12 5.13 5.14 5.15 5.16 5.17 5.18 5.19 5.20 5.21 5.22 5.23 Shawn Wildermuth. "A Developer's Perspective on WinFS: Part 1". MSDN. http://msdn2.microsoft.com/en-us/library/ms996622.aspx. Retrieved 2007-06-30.
6. ↑ 6.0 6.1 6.2 6.3 Vijay Bangaru. "Unify, Organize, Explore, and Innovate. Oh my! (Part 2)". WinFS Team Blog. http://blogs.msdn.com/winfs/archive/2005/11/01/487894.aspx. Retrieved 2007-06-30.
7. ↑ 7.00 7.01 7.02 7.03 7.04 7.05 7.06 7.07 7.08 7.09 7.10 Sean Grimaldi. "The WinFS Files: Divide et Impera". MSDN. http://msdn2.microsoft.com/en-us/library/aa480690.aspx. Retrieved 2007-06-30.
8. ↑ 8.0 8.1 Thomas Rizzo. "WinFS 101: Introducing the New Windows File System". MSDN. http://msdn2.microsoft.com/en-US/library/aa480687.aspx. Retrieved 2007-06-30.
9. ↑ 9.00 9.01 9.02 9.03 9.04 9.05 9.06 9.07 9.08 9.09 9.10 "WinFS on The .NET Show". http://www.microsoft.com/downloads/info.aspx?na=90&p=&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=e049f148-460c-47af-93a0-dfd0f4edf598&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2f6%2fb%2f6%2f6b659b87-eafa-4c15-8783-1476e59bba13%2fdotnetshow41\_300k.EXE. Retrieved 2007-07-04.
10. ↑ Vijay Bangaru. "Unify, Organize, Explore, and Innovate. Oh my! (Part 1)". WinFS Team Blog. http://blogs.msdn.com/winfs/archive/2005/10/24/484380.aspx. Retrieved 2007-06-30.
11. ↑ 11.00 11.01 11.02 11.03 11.04 11.05 11.06 11.07 11.08 11.09 11.10 11.11 11.12 Paul Thurrott. "Windows Storage Foundation (WinFS) Preview". http://www.winsupersite.com/showcase/winfs\_preview.asp. Retrieved 2007-06-30.
12. ↑ Cath Everett. "Will Longhorn be worth the pain?". ZDNet. http://news.zdnet.co.uk/software/0,1000000121,39191853,00.htm. Retrieved 2007-06-30.
13. ↑ 13.0 13.1 "WinFS for Developers". NTFS.com. http://www.ntfs.com/winfs\_developers.htm. Retrieved 2007-07-04.
14. ↑ Vijay Bangaru. "WinFS Beta 1 Refresh now available". WinFS Team Blog. http://blogs.msdn.com/winfs/archive/2005/12/01/499042.aspx. Retrieved 2007-06-30.
15. ↑ Shan Sinha. "Showing off the next release of WinFS at Tech Ed 2006, in Boston! Join us!". WinFS Team Blog. http://blogs.msdn.com/winfs/archive/2006/05/22/604075.aspx. Retrieved 2007-06-30.
16. ↑ Sanjay Anand. "My tryst with Destiny, err… Integrated Storage". WinFS Team Blog. http://blogs.msdn.com/winfs/archive/2006/02/24/538925.aspx. Retrieved 2007-06-30.
17. ↑ 17.0 17.1 17.2 17.3 Quentin Clark. "Where is WinFS now?". http://perspectives.on10.net/blogs/jonudell/Where-is-WinFS-now/. Retrieved 2008-05-17.
18. ↑ Quentin Clark. "Update to the Update". WinFS Team Blog. http://blogs.msdn.com/winfs/archive/2006/06/26/648075.aspx. Retrieved 2007-06-30.
19. ↑ Daniel Kornev (December 19, 2006). "A few words about WinFS: The project is back on track". Channel 9. http://channel9.msdn.com/ShowPost.aspx?PostID=267149.
20. ↑ Nate Mook. "MS Explains WinFS, Releases Beta 1". BetaNews. http://www.betanews.com/article/MS\_Explains\_WinFS\_Releases\_Beta\_1/1125353356. Retrieved 2007-07-02.
21. ↑ 21.0 21.1 Shishir Mehrotra (September 2005). ""WinFS" Future Directions: An Overview". *Professional Developers Conference 2005 presentations*. Microsoft. http://microsoft.sitestream.com/PDC05/DAT/DAT209\_files/intro.htm. Retrieved 2006-05-22. (Currently offline, mirror).
22. ↑ Erwyn van der Meer. "First Look on WinFS Beta 1". http://bloggingabout.net/blogs/erwyn/archive/2005/08/30/9156.aspx. Retrieved 2007-07-03.
23. ↑ Vijay Bangaru. "WinFS Mailbox". WinFS Team Blog. http://blogs.msdn.com/winfs/archive/2005/09/13/465269.aspx. Retrieved 2007-06-30.
24. ↑ 24.00 24.01 24.02 24.03 24.04 24.05 24.06 24.07 24.08 24.09 24.10 24.11 Richard Grimes. "Revolutionary File Storage System Lets Users Search and Manage Files Based on Content". MSDN Magazine. http://msdn.microsoft.com/msdnmag/issues/04/01/WinFS/. Retrieved 2007-06-30.
25. ↑ 25.0 25.1 25.2 25.3 25.4 25.5 25.6 25.7 25.8 25.9 Shawn Wildermuth (July 2004). "A Developer's Perspective on WinFS: Part 2". *MSDN*. Microsoft. http://msdn2.microsoft.com/en-us/library/ms996631.aspx. Retrieved 2007-06-30.
26. ↑ 26.0 26.1 26.2 26.3 Kati Dimitrova. "About WinFS Rules". WinFS Team Blog. http://blogs.msdn.com/winfs/archive/2005/10/10/479416.aspx. Retrieved 2007-06-30.
27. ↑ Vijay Bangaru. "Unify, Organize, Explore, and Innovate. Oh my! (Part 4)". WinFS Team Blog. http://blogs.msdn.com/winfs/archive/2005/11/18/494707.aspx. Retrieved 2007-06-30.
28. ↑ Thomas Rizzo, Sean Grimaldi (October 18, 2004). "An Introduction to "WinFS" OPath". *MSDN*. Microsoft. http://msdn2.microsoft.com/en-us/library/aa480689.aspx. Retrieved 2007-06-30.
29. ↑ 29.0 29.1 "Innovative Data Programming Platform". http://www.codeplex.com/classifier/Wiki/View.aspx?title=Innovative%20Data%20Programming%20Platform&referringTitle=WinFS. Retrieved 2007-03-15.
30. ↑ 30.0 30.1 30.2 30.3 30.4 30.5 Neil Padgett. "Getting Data Into WinFS with WinFS Synchronization". WinFS Team Blog. http://blogs.msdn.com/winfs/archive/2005/11/17/494222.aspx. Retrieved 2007-06-30.
31. ↑ Wei-Meng Lee. "WinFS -StoreSpy". http://weimenglee.blogspot.com/2005/09/winfs-storespy.html. Retrieved 2007-06-30.
32. ↑ "Stefano Demiliani WeBlog:WinFS StoreSpy v0.8 for the WinHEC 2004 Longhorn Build". http://dotnetjunkies.com/WebLog/demiliani/archive/2004/05/20/14044.aspx. Retrieved 2007-03-12.
33. ↑ "StoreSpy should become StoreEditor". http://winfx.edu.pl/art1953.html. Retrieved 2007-06-30.
34. ↑ 34.0 34.1 Sanjay Nagamangalam. "Visualizing WinFS Types". WinFS Team Blog. http://blogs.msdn.com/winfs/archive/2005/09/08/462713.aspx. Retrieved 2007-07-03.
35. ↑ Luiz Miranda. "Using OPather To Help Write Queries". WinFS Team Blog. http://blogs.msdn.com/winfs/archive/2005/09/13/465218.aspx. Retrieved 2007-06-30.
36. ↑ Shishir Mehrotra. "The killer app for getting users organized". WinFS Team Blog. http://blogs.msdn.com/winfs/archive/2006/05/16/599183.aspx. Retrieved 2007-06-30.

## External links

* WinFS Blog
* WinFS at the Microsoft Developer Network[*dead link*]
* Channel 9 Videos
* WinFS Newsgroup
* WinFS Beta 1 Review
* WinFS area on NetFXGuide.com

Template:Good article

ar:وين إف إس
cs:WinFS
da:WinFS
de:WinFS
es:WinFS
fr:WinFS
ko:WinFS
it:WinFS
nl:WinFS
ja:WinFS
no:WinFS
pl:WinFS
pt:WinFS
ru:WinFS
fi:WinFS
sv:WinFS
zh:WinFS