1461129296-632537f1-f4f7-4540-905a-776e5f18d3f6

1. A pressure sensor comprising:
a sensor membrane formed from conductive material for exposure to fluid at a pressure to be sensed;
a compensation membrane formed from conductive material and sealed from the fluid at the pressure to be sensed; and,
associated circuitry connected to the sensor membrane for converting deflection into an output signal indicative of the fluid pressure and connected to the compensation membrane for converting deflection into an adjustment to the output signal that compensates for membrane deflection due to thermal expansion; wherein,
each membrane is less than 0.1 grams.
2. A pressure sensor according to claim 1 wherein the sensor membrane partially defines a first chamber containing fluid at a reference pressure, the compensation membrane is in a chamber sealed from the fluid at a pressure to be sensed.
3. A pressure sensor according to claim 2 further comprising:
a first recess defined in a substrate covered by the first membrane so as to define the first chamber, the first chamber containing a fluid at a reference pressure such that the first membrane deflects due to a pressure difference between the reference pressure and the fluid pressure; and
a second recess defined in the substrate covered by a capping member so as to define, and seal from the fluid pressure, the second chamber, the second membrane dividing the second chamber into sections fluidically sealed from each other such that the second membrane deflects at a predetermined pressure difference between the sections.
4. A pressure sensor according to claim 3 wherein the sensor is a capacitative sensor, with a conductive layer deposited in each of the first and second chambers and the first and second membranes are conductive, such that the conductive layer in the first chamber and the first membrane form capacitor electrodes and the deflection of the first membrane changes the capacitance which the associated circuitry converts to the output signal.
5. A pressure sensor according to claim 1 wherein the fluid pressure is air pressure within a pneumatic tire.
6. A pressure sensor according to claim 1 wherein the membranes are at least partially made from a metal-nitride compound.
7. A pressure sensor according to claim 1 wherein each membrane is approximately 0.5 \u03bcm thick.
8. A pressure sensor according to claim 1 wherein each membrane is circular with a diameter less than 500 microns.
9. A pressure sensor according to claim 1 wherein the membranes are laminates having at least two layers, at least one of the layers being at least partially formed from conductive material.
10. A pressure sensor according to claim 9 wherein the layers within the laminate are be formed from the deposition of different metal ceramics.
11. A pressure sensor according to claim 10 wherein the metal ceramics are metal nitrides or mixed metal nitrides.
12. A pressure sensor according to claim 9 wherein one or more of the layers of the laminate is metal.
13. A pressure sensor according to claim 1 wherein the membranes are non-planar.
14. A pressure sensor according to claim 13 wherein the membranes are corrugated.
15. A pressure sensor according to claim 14 wherein the flexible corrugated membranes each have a corrugation factor of 8.
16. A pressure sensor according to claim 15 wherein the sensor has a linear response up to about 1 MPa.
17. A pressure sensor according to claim 15 wherein the membrane corrugations have a period of between 5 microns and 15 microns.
18. A pressure sensor according to claim 17 wherein the membranes are substantially circular and the corrugations are annular.
19. A pressure sensor according to claim 14 wherein the corrugations have a substantially square-shaped cross-sectional profile.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A computer-implemented method performed with a computing system for exploring social connections in an in-memory database, the method comprising:
identifying an attribute in a user profile associated with a first user;
executing a query against a data element stored in an in-memory database, the query including the attribute in the user profile;
identifying a second user from results of the query, the second user associated with the data element based on a relationship between the second user and the first user defined by the attribute; and
generating displayable information associated with the second user.
2. The method of claim 1, wherein the data element is a data cube.
3. The method of claim 1 further comprising performing at least one of:
presenting an interface operable to allow the first user to email the second user;
presenting an interface operable to allow the first user to send an invitation to the second user;
presenting an interface operable to allow the first user to export information to the second user; or
presenting an interface to allow additional searches of data elements in the in-memory database based on the information associated with the second user.
4. The method of claim 1, wherein the attribute is related to a current project of the first user.
5. The method of claim 4, wherein the query includes an identification of the current project and the relationship is determined based on identification of members participating in the current project.
6. The method of claim 1, wherein the information associated with the second user includes a user profile of the second user.
7. The method of claim 1, further comprising:
identifying a change to the data element; and
updating the displayable information associated with the second user based on the change to the data element.
8. The method of claim 1, wherein the query is executed against a plurality of data elements in the in-memory database, wherein at least two of the plurality of data elements are from different data sources in the in-memory database, and
prior to executing the query against the data element stored in the in-memory database, the different data sources are replicated to the in-memory database from one or more enterprise systems communicably coupled to the in-memory database.
9. The method of claim 8, wherein executing a query against a data element stored in an in-memory database comprises executing a query against a data element stored in an in-memory database with an in-memory computational engine in the in-memory database.
10. The method of claim 1, further comprising:
identifying a plurality of additional users from results of the query, the additional users associated with the data element based on a relationship between each of the additional users and the first user defined by the attribute;
dynamically generating a graphical network representing the first user, the plurality of additional users, and the relationship between each of the additional users and the first user defined by the attribute, where the first user and the plurality of additional users are represented as nodes in the graphical network and the relationship between each of the additional users and the first user defined by the attribute are represented as connections between nodes.
11. An apparatus comprising instructions embodied on a tangible, non-transitory computer-readable media, the instructions operable when executed to cause a computing system to perform operations comprising:
identifying an attribute in a user profile associated with a first user;
executing a query against a data element stored in an in-memory database, the query including the attribute in the user profile;
identifying a second user from results of the query, the second user associated with the data element based on a relationship between the second user and the first user defined by the attribute; and
generating displayable information associated with the second user.
12. The apparatus of claim 11, wherein the data element is a data cube.
13. The apparatus of claim 11, wherein the operations further comprise performing at least one of:
presenting an interface operable to allow the first user to email the second user;
presenting an interface operable to allow the first user to send an invitation to the second user;
presenting an interface operable to allow the first user to export information to the second user; or
presenting an interface to allow additional searches of data elements in the in-memory database based on the information associated with the second user.
14. The apparatus of claim 11, wherein the attribute is related to a current project of the first user.
15. The apparatus of claim 14, wherein the query includes an identification of the current project and the relationship is determined based on identification of members participating in the current project.
16. The apparatus of claim 11, wherein the information associated with the second user includes a user profile of the second user.
17. The apparatus of claim 11, wherein the operations further comprise:
identifying a change to the data element; and
updating the displayable information associated with the second user based on the change to the data element.
18. The apparatus of claim 11, wherein the query is executed against a plurality of data elements in the in-memory database, wherein at least two of the plurality of data elements are from different data sources in the in-memory database, and
prior to executing the query against the data element stored in the in-memory database, the different data sources are replicated to the in-memory database from one or more enterprise systems communicably coupled to the in-memory database.
19. The apparatus of claim 18, wherein executing a query against a data element stored in an in-memory database comprises executing a query against a data element stored in an in-memory database with an in-memory computational engine in the in-memory database.
20. The apparatus of claim 11, wherein the operations further comprise:
identifying a plurality of additional users from results of the query, the additional users associated with the data element based on a relationship between each of the additional users and the first user defined by the attribute;
dynamically generating a graphical network representing the first user, the plurality of additional users, and the relationship between each of the additional users and the first user defined by the attribute, where the first user and the plurality of additional users are represented as nodes in the graphical network and the relationship between each of the additional users and the first user defined by the attribute are represented as connections between nodes.
21. A computing system, comprising a memory, one or more processors, and instructions stored on the memory and operable when executed by the one or more processors to cause the computing system to perform operations comprising:
identifying an attribute in a user profile associated with a first user;
executing a query against a data element stored in an in-memory database, the query including the attribute in the user profile;
identifying a second user from results of the query, the second user associated with the data element based on a relationship between the second user and the first user defined by the attribute; and
generating displayable information associated with the second user.
22. The system of claim 21, wherein the data element is a data cube.
23. The system of claim 21, wherein the operations further comprise performing at least one of:
presenting an interface operable to allow the first user to email the second user;
presenting an interface operable to allow the first user to send an invitation to the second user;
presenting an interface operable to allow the first user to export information to the second user; or
presenting an interface to allow additional searches of data elements in the in-memory database based on the information associated with the second user.
24. The system of claim 21, wherein the attribute is related to a current project of the first user.
25. The system of claim 24, wherein the query includes an identification of the current project and the relationship is determined based on identification of members participating in the current project.
26. The system of claim 21, wherein the information associated with the second user includes a user profile of the second user.
27. The system of claim 21, wherein the operations further comprise:
identifying a change to the data element; and
updating the displayable information associated with the second user based on the change to the data element.
28. The system of claim 21, wherein the query is executed against a plurality of data elements in the in-memory database, wherein at least two of the plurality of data elements are from different data sources in the in-memory database, and
prior to executing the query against the data element stored in the in-memory database, the different data sources are replicated to the in-memory database from one or more enterprise systems communicably coupled to the in-memory database.
29. The system of claim 28, wherein executing a query against a data element stored in an in-memory database comprises executing a query against a data element stored in an in-memory database with an in-memory computational engine in the in-memory database.
30. The system of claim 21, wherein the operations further comprise:
identifying a plurality of additional users from results of the query, the additional users associated with the data element based on a relationship between each of the additional users and the first user defined by the attribute;
dynamically generating a graphical network representing the first user, the plurality of additional users, and the relationship between each of the additional users and the first user defined by the attribute, where the first user and the plurality of additional users are represented as nodes in the graphical network and the relationship between each of the additional users and the first user defined by the attribute are represented as connections between nodes.