Abstract: The subject disclosure relates to techniques for providing data experience(s) via disparate semantic annotations based on a respective user scenario. Semantic information for respective data types of data set(s) may be received. The data types may be annotated based on the semantic information to obtain respective data annotations. In response to receipt of a search query from a client, a search result that includes at least a portion of one or more data annotations is generated to be sent to the client. The search query may request performance of a search against the semantic information to obtain first semantic information associated with first data type(s) of the data types. The portion of the one or more data annotations may include the first semantic information. The first semantic information may describe operation(s) to be performed on data of at least one of the first data type(s).

Abstract: Aspects extend to methods, systems, and computer program products for consuming streamed data records. An application binds members (e.g., columns) of a structure (e.g., record) from a data source to memory buffers, and may specify one or more members be retrieved individually or be ignored entirely. The application requests one or more records from the data source be fetched into the memory buffers until it comes across a member that doesn't match the binding. The data source notifies of the application of data that is ready to be read from the exception member. The application can create or update binding information for the member, read data from the member, or ignore the member. When finished, the application requests the data source continue processing record(s). Additional members are copied into the memory buffers until the last member is read for the (set of) record(s) or another exception member is discovered.

Abstract: Aspects extend to methods, systems, and computer program products for consuming streamed data records. An application binds members (e.g., columns) of a structure (e.g., record) from a data source to memory buffers, and may specify one or more members be retrieved individually or be ignored entirely. The application requests one or more records from the data source be fetched into the memory buffers until it comes across a member that doesn't match the binding. The data source notifies of the application of data that is ready to be read from the exception member. The application can create or update binding information for the member, read data from the member, or ignore the member. When finished, the application requests the data source continue processing record(s). Additional members are copied into the memory buffers until the last member is read for the (set of) record(s) or another exception member is discovered.

Abstract: Systems and methods that enable relationship information to be carried along with data objects when serializing/deserializing data objects among application tiers. A tracking component tracks information on relationships associated with a data object, and further enables subsequent change processing on the data object's relationship information. Accordingly, relationship information can be carried along with the data object, such that database operation can be performed without requirement of additional information from the database (e.g., foreign key information that is part of associated graphs).

Abstract: Systems and methods that enable relationship information to be carried along with data objects when serializing/deserializing data objects among application tiers. A tracking component tracks information on relationships associated with a data object, and further enables subsequent change processing on the data object's relationship information. Accordingly, relationship information can be carried along with the data object, such that database operation can be performed without requirement of additional information from the database (e.g., foreign key information that is part of associated graphs).

Abstract: The subject disclosure relates to techniques for providing data experience(s) via disparate semantic annotations based on a respective user scenario. An annotation component can synthesize semantic information for respective data types of data set(s), associate the semantic information with the respective data types to obtain respective data annotations, and in response to receiving a query from a client, send at least a portion of the respective data annotations to the client. Further, a data aggregation component can aggregate the respective data annotations and at least a portion of the data set(s). Other embodiments relate to performing, via an application, operations utilizing a data type based on respective semantic annotations associated with the data type. Yet other embodiments relate to receiving external data annotation(s) and associating the external data annotation(s) with portion(s) of the respective data types to derive portion(s) of the respective semantic annotations.

Abstract: Systems and methods that enable relationship information to be carried along with the entity when serializing/deserializing entities among application tiers. A tracking component tracks information on relationships associated with an entity, and further enables users to perform subsequent change processing on the entity's relationship information. Accordingly, relationship information can be carried along with the entity such that database operation can be performed without requirement of additional information from the database (e.g., foreign key information that is part of associated graphs).

Abstract: Systems and methods that enable relationship information to be carried along with the entity when serializing/deserializing entities among application tiers. A tracking component tracks information on relationships associated with an entity, and further enables users to perform subsequent change processing on the entity's relationship information. Accordingly, relationship information can be carried along with the entity such that database operation can be performed without requirement of additional information from the database (e.g., foreign key information that is part of associated graphs).

Abstract: Systems and methods that enable relationship information to be carried along with the entity when serializing/deserializing entities among application tiers. A tracking component tracks information on relationships associated with an entity, and further enables users to perform subsequent change processing on the entity's relationship information. Accordingly, relationship information can be carried along with the entity such that database operation can be performed without requirement of additional information from the database (e.g., foreign key information that is part of associated graphs).

Abstract: A programming interface for a computer platform can include various functionality. In certain embodiments, the programming interface includes one or more of the following groups of types or functions: those related to core file system concepts, those related to entities that a human being can contact, those related to documents, those common to multiple kinds of media, those specific to audio media, those specific to video media, those specific to image media, those specific to electronic mail messages, and those related to identifying particular locations.

Abstract: The subject innovation provides a system and/or a method that facilitates developing schemas for a file storage system. A type definition component can provide a schema grammar, wherein a generator component can employ the schema grammar to build the schema for the file storage system. The schema grammar can describe information types stored in the file storage system that are represented as instances of complex types that are part of a type system that supports inheritance. The schema grammar can support a declaration of an association between types, versioning specifications, and/or content indexing specifications.

Abstract: A system and method facilitating a unified framework for accessing structured and unstructured data is provided. The invention includes a source document having data that is parsed into a data document component providing a hierarchical representation of data associated with the source document and a data set component providing a relational representation of at least a portion of the data associated with the source document. The invention further provides for a schema defining a structure of the relational representation to be associated with the source document and/or inferred by the data set component. Data stored in the data document component and the data set component are synchronized, thus a change made to data stored in the data set component is reflected in data stored in the data document component. Further, a change made to data stored in the data document component is reflected in data stored in the data set component if utilized according to the schema.

Abstract: A query processor's capabilities may be employed to identify a range rows resulting from a user query to be returned. A server cursor may be declared, opened, fetched from and closed in a single batched request in order to avoid keeping state on a database server between requests. A single block fetch may be used within the batch to retrieve a requisite number of rows from a specified ordinal position. Where server cursors are not available, an intermediate table may be used to hold a subset of the rows resulting from the user query, and row numbers may be added to facilitate selecting the range of rows from that intermediate table. Intelligence within a query processor may be leveraged to support identifying the range of rows to be returned without maintaining state between client requests.

Abstract: The present invention relates to systems and methods for employing a trigger based mechanism to detect changes in a database table, providing a notification when the database table changes and registering to receive the notification. The systems and methods employ a listeners table to store information associated with registered database tables. Alter a database table changes, a trigger mechanism associated with the database change facilitates a search of the listeners table for a parameter associated with the changed database table. If the changed database table is registered, the information from the listeners table is provided to a delivery service which transmits a message indicating the registered database table changed. After receiving the message, a notification runtime service can route a notification to a client(s) registered to receive the notification. The foregoing mitigates performing time intensive queries and utilizing inconsistent query results.

Abstract: The present invention relates to a system and methodology to facilitate XML data communications and processing. A diffgram data structure is provided that includes one or more states of a plurality of data records. The state information can be determined by examining one or more data sources for differences from one or more reference data sources. If differences are detected between the data sources, the diffgram can be constructed in an XML compatible format with both previous state indications and current state indications that describes the state differences between the data sources. Error information and/or other administrative information or codes can also be provided to facilitate database management and/or processing.

Abstract: A method of synchronizing data between multiple endpoints each storing a copy of the data in accordance with different underlying schemas. An application model that provides a logical representation of an underlying schema is extended with a synchronization model that provides a logical representation of changes made to the data. The synchronization model comprises functions that provide synchronization information on the changes in a common format. Using such synchronization information, changes in a copy of the data stored in a first underlying schema on a first endpoints are applied to another copy of the data stored in a second underlying schema on a second endpoint in synchronization relationship with the first endpoint.

Abstract: An application program interface (API) for a data platform. The API includes a generic data access component that exposes at least one of stores, sessions, transactions, and query services of the data platform, which data platform is associated with a data store. A data classes component of the API provides canonical, application-independent classes that expose types and relationships of a data model of the data platform. The API includes a domain data classes component of application-specific and framework-specific classes that expose domain-specific properties and behaviors of the data platform. The data platform can be a common data platform that interfaces to the data store to provide data services accessible by a plurality of disparate application frameworks, which data services allow a corresponding application of the different frameworks to access the data store.

Abstract: The claimed subject matter relates to an architecture that can facilitate an incremental approach to an Object-Relational mapping solution. The architecture can provide a rich data model that is defined at the value layer. The rich data model can expose an interface that conforms with the interfaces exposed by common storage-specific data providers. The architecture can extend common storage-specific data provider to support common command representations, and provide entity services that work in terms of the rich data model as well as object services such as identity management, updating and change tracking.

Abstract: Systems and methods that enable relationship information to be carried along with the entity when serializing/deserializing entities among application tiers. A tracking component tracks information on relationships associated with an entity, and further enables users to perform subsequent change processing on the entity's relationship information. Accordingly, relationship information can be carried along with the entity such that database operation can be performed without requirement of additional information from the database (e.g., foreign key information that is part of associated graphs).

Abstract: The present invention relates to a system and methodology to facilitate XML data communications and processing. A diffgram data structure is provided that includes one or more states of a plurality of data records. The state information can be determined by examining one or more data sources for differences from one or more reference data sources. If differences are detected between the data sources, the diffgram can be constructed in an XML compatible format with both previous state indications and current state indications that describes the state differences between the data sources. Error information and/or other administrative information or codes can also be provided to facilitate database management and/or processing.