DDEX (DATA DESIGNER EXTENSIBILITY) DEFAULT OBJECT IMPLEMENTATIONS

• US 20090006446A1
• Filed: 06/28/2007
• Published: 01/01/2009
• Est. Priority Date: 06/28/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Provine, Stephen Wharton
• Granted Patent: US 7,917,887 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/20 Software design

Abstract

A system and method for providing DDEX (data designer extensibility) default object implementations by bundling information associated with a support entity and information required to instantiate a new default instance is provided. Metadata associated with the definition of the support entity indicates if a default implementation exists and includes information associated with the creation of the default implementation. The metadata of the support entity is analyzed to automatically create and return a default implementation if the provider does not supply a specific implementation.

Claims

1. A system that provides a DDEX (data designer extensibility) default object implementation, comprising:

a support entity creating component that attaches metadata associated with a default implementation to the definition of a support entity; and

a default implementation creating component that analyzes the metadata to determine the default implementation for the support entity.

2. The system of claim 1, wherein the metadata includes an attribute that indicates existence of the default implementation.

3. The system of claim 2, wherein the attribute includes an identifier that specifies a uniquely recognizable value that represents a lookup of the default implementation.

4. The system of claim 1, wherein the default implementation is employed to instantiate an instance, the instance returned to a client.

5. The system of claim 1, further comprising an implementation retrieval component that retrieves an implementation for the support entity.

6. The system of claim 5, further comprising a querying component that queries one or more third party providers to determine whether the third party providers support the support entity.

7. The system of claim 5, further comprising an analysis component that analyzes a response from a third party provider to determine at least one of a specific implementation provided by the third party provider or the default implementation created based at least in part on the metadata.

8. A method of providing a DDEX (data designer extensibility) default object implementation, comprising:

analyzing metadata associated with a support entity; and

determining a default implementation based on the analysis.

9. The method of claim 8, further comprising querying at least one provider to determine if the at least one provider supports the support entity.

10. The method of claim 9, further comprising retrieving a provider specific implementation if the at least one provider supports the support entity.

11. The method of claim 10, further comprising employing the provider specific implementation to create an instance, the instance returned to a client.

12. The method of claim 9, further comprising creating an instance by employing the default implementation if the at least one provider does not support the support entity, the instance returned to a client.

13. The method of claim 8, further comprising determining an attribute included in the metadata that indicates existence of the default implementation.

14. The method of claim 13, further comprising determining an identifier associated with the attribute to lookup the default implementation for the support entity.

15. The method of claim 8, further comprising defining metadata associated with the default implementation of the support entity, the metadata attached to a definition of the support entity.

16. A system that provides a DDEX (data designer extensibility) default object implementation, comprising:

means for defining a support entity; and

means for bundling information associated with a default implementation of the support entity with the definition.

17. The system of claim 16, further comprising means for analyzing metadata associated with a support entity to determine the default implementation of the support entity.

18. The system of claim 17, further comprising means for determining an attribute that indicates the existence of a default implementation.

19. The system of claim 18, further comprising means for looking up the default implementation based at least in part on an identifier included in the attribute.

20. The system of claim 17, further comprising means for creating an instance based at least in part on the default implementation.