Abstract: The claimed subject matter provides a system and/or a method that facilitates implementing a binding between a radio frequency identification (RFID) process and a device. An RFID process can receive a tag read event from a device and make the tag read event available for at least one high level application. A binding engine can bind the RFID process to the device while decoupling a design time activity and a deployment time activity associated with the RFID process. In addition, the binding engine can include at least one of a device mapping component that employs a device binding; and a component configuration module that employs a component binding.

Abstract: The claimed subject matter provides a system and/or a method that facilitates configuring at least one radio frequency identification (RFID) device. An RFID network can include at least one device associated with a device group, wherein the device group corresponds to a characteristic. An organizational manager can uniformly configure the at least one device based at least in part upon membership of the device group.

Abstract: Systems and methodologies that facilitate evolving a data model via a combination of an explicit logical model definition, logical model changes, functional units, an explicit/implicit physical model and physical model changes, to derive a data model transformation. Such an arrangement can provide for a rich set of transformations, which can be automatically applied to a data model instantiation. The subject invention enables leveraging a common set of code, by defining the set of transformations across an arbitrary data model.

Abstract: Systems and methodologies that facilitate data handling among participants with mismatched schema sets of an extensible data model, via employing a versioning component. The versioning component can identify and separate the mismatched and matched data, and direct the mismatched portion to a bit bucket component. The bit bucket component can further persistently store the mismatched data, to enable interaction among participants with mismatched data types. The data can be re-integrated to ensure that round trip data is available to the next participant.

Abstract: A system that facilitates checking the consistency of a user-defined data type in relation to a database environment. The invention can employ a user-defined type (UDT) storage format whereby values can be self-describing, including the runtime type of the value. The invention can take the type definition that is persisted in the metadata catalogs as a streaming input and generate a type-specific state machine thereafter. At every point in the checking process, the type-specific state machine can be aware of the next data type that is to be encountered in the check. Whenever an embedded UDT is encountered, the current type-specific state machine can be suspended and saved. The embedded UDT can be checked before proceeding. In this way, the complex check can be effected using memory space proportional to the number of levels in the UDT as opposed to the number of bytes in the object.

Abstract: Systems and methodologies of partially deserializing a Complex Type Object, via a deserializer that intercepts and materializes such object on demand. The object or a subset thereof can be deserialized to produce an Instance of Complex Type that is implemented by a property store. The deserializer can include an analyzer component that analyzes the Property Store.

Abstract: A database API is presented that can expose data of non-native data-types, i.e., types that are unknown at API design-time. A broad type-system is used that is understood by both a server and a client. The API can dynamically discover, at run-time, data types that were defined using this broad type-system. The API can retrieve metadata that references a non-native data type in a client type library. A retrieved instance of the non-native data type, in serialized form, may be deserialized using the metadata.

Abstract: Efficient hierarchical searching is based on object type. By pre-computing additional information and storing it in a fast-lookup structure, it is possible to quickly identify objects that satisfy an object retrieval request. Furthermore, it is also possible to use this technique to avoid object hydration for operations in the store. Moreover, it is possible to leverage database statistical structures such as histograms to estimate the number of qualifying objects without having to examine each object.

Abstract: The subject invention provides a system and/or a method that facilitates employing a security technique to an RFID network. An interface can receive role-based authorization data related to an operating system. A security component can enhance security to at least one of a manipulation of a process and a utilization of a device within the RFID network based at least in part upon role-based authorization data.

Abstract: The subject invention provides a system and/or a method that facilitates employing a model based at least upon a framework, wherein the model can be utilized to build an RFID application. A receiver component can receive data, wherein a model component can create a model based at least in part upon the received data that facilitates creating and/or executing the RFID application. The framework can be, but is not limited to, an entity, a framework class, a hierarchical framework of at least one class, an interface, an exception, a component architecture, a schema, an object model, and/or an API. The model can be utilized to create, deploy, manage, and/or execute the RFID application to provide a generic operation and/or a business specific scenario.

Abstract: The subject invention provides a system and/or a method that facilitates implementing an RFID process by providing creation and/or execution of the RFID process as it relates to a provider(s) and the associated devices related to such provider(s). A receiver component can receive information relating to at least one or more providers. An RFID server component can employ the information in connection with providing an RFID process that can be applied generically to a plurality of devices associated with a subset of providers. An RFID engine can process an RFID event including an event processing tree that abstracts a logical entity, wherein the logical entity consists of a logical source can define the RFID process.

Abstract: The claimed subject matter provides a system and/or a method that facilitates utilizing rule-based technology with radio frequency identification (RFID) network. An interface can receive real-time RFID data from a process comprising at least one device collection in the RFID network, wherein a rules engine (RE) component can employ a declarative event policy associated with the RFID network as rules. The RE allows dynamic updates of business logic associated with applications in real-time without the re-start and/or stop the applications. The system and/or method further comprises a vocabulary component that provides terms that defines at least one of the rule, rule condition, and action based at least in part upon an industry specific nomenclature.

Abstract: Efficient hierarchical searching is based on object type. By pre-computing additional information and storing it in a fast-lookup structure, it is possible to quickly identify objects that satisfy an object retrieval request. Furthermore, it is also possible to use this technique to avoid object hydration for operations in the store. Moreover, it is possible to leverage database statistical structures such as histograms to estimate the number of qualifying objects without having to examine each object.

Abstract: A database system and method allows a user to write program code in a high-level programming language that implements a class that defines the structure of a user-defined type and methods that can be invoked on instances of the type. The class is then registered with the database system, which enforces a specific contract for user-defined types against the class. The contract comprises the following requirements. First, the class must specify one of a plurality of different formats for persisting instances of the user-defined type in a database store. Second, the class must be capable of returning a null value for the user-defined type. Third, the class must provide a method for converting the user-defined type to another type. Once these requirements are satisfied, the database system enables instances of the user-defined type to be created. A user-defined type can be used in all contexts where any other built-in type can be used.

Abstract: The present invention describes an efficient and fast framework for implementing table-valued functions (TVF's) in a relational database server. The framework provides desirable extensibility properties and has the ability to minimize performance degradations by integrating tightly with the optimization infrastructure in a query processor. The present invention also enables a managed execution environment (MEE) such as the Common-Language-Runtime (CLR), to efficiently and dynamically extend the logic of the database engine with user-supplied code.

Abstract: A new persistence format for storing objects of a user defined type in a database store enables information about the structure of the type to be communicated to the store. This information enables a number of store optimizations, including direct structural access to members of the type. Specifically, metadata is exchanged between the type implementer and the data store. The store uses the metadata to determine the storage layout for instances of the type. With this information, the store is able to detect access patterns that can be optimized to directly operate over the storage representation without hydration (deserialization) the object.

Abstract: A database system and method allows a user to write program code in a high-level programming language that implements a class that defines the structure of a user-defined type and methods that can be invoked on instances of the type. The class is then registered with the database system, which enforces a specific contract for user-defined types against the class. The contract comprises the following requirements. First, the class must specify one of a plurality of different formats for persisting instances of the user-defined type in a database store. Second, the class must be capable of returning a null value for the user-defined type. Third, the class must provide a method for converting the user-defined type to another type. Once these requirements are satisfied, the database system enables instances of the user-defined type to be created. A user-defined type can be used in all contexts where any other built-in type can be used.

Abstract: A database system and method allows a user to write program code in a high-level programming language that implements a class that defines the structure of a user-defined type and methods that can be invoked on instances of the type. The class is then registered with the database system, which enforces a specific contract for user-defined types against the class. The contract comprises the following requirements. First, the class must specify one of a plurality of different formats for persisting instances of the user-defined type in a database store. Second, the class must be capable of returning a null value for the user-defined type. Third, the class must provide a method for converting the user-defined type to another type. Once these requirements are satisfied, the database system enables instances of the user-defined type to be created. A user-defined type can be used in all contexts where any other built-in type can be used.

Abstract: A database system and method allows a user to write program code in a high-level programming language that implements a class that defines the structure of a user-defined aggregate and methods that can be invoked on instances of the user-defined aggregate. The class is then registered with the database system, which enforces a specific contract for user-defined aggregates against the class. The contract comprises the following requirements. First, the class must specify one of a plurality of different formats for persisting instances of the user-defined aggregate in a database store.

Abstract: A database system and method allows a user to write program code in a high-level programming language that implements a class that defines the structure of a user-defined type and methods that can be invoked on instances of the type. The class is then registered with the database system, which enforces a specific contract for user-defined types against the class. The contract comprises the following requirements. First, the class must specify one of a plurality of different formats for persisting instances of the user-defined type in a database store. Second, the class must be capable of returning a null value for the user-defined type. Third, the class must provide a method for converting the user-defined type to another type. Once these requirements are satisfied, the database system enables instances of the user-defined type to be created. A user-defined type can be used in all contexts where any other built-in type can be used.