# US 2012/0084074 A1 · Association Of Semantic Meaning With Data Elements Using Data Definition Tags > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2012/0084074 A1 - Document ID: US20120084074A1 - Status: Published application - Kind: A1 - Application number: 12/895,870 - Filed: 2010-10-01 - Published: 2012-04-05 - Earliest claimed: 2010-10-01 - Assignees: Microsoft Corporation - Inventors: Ben Chronister; Bryan Dove - Web page: https://patentgrep.com/patent/US20120084074A1 ## CPC - G06F 16/367: {Ontology} - G06F 16/313: {Selection or weighting of terms for indexing} - G06F 16/353: into predefined classes - G06F 16/81: Indexing, e.g. XML tags; Data structures therefor; Storage structures - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Technology is described for associating semantic meaning with data elements. The system can include a messaging module configured to receive a message having data elements. A storage module can store the data elements from the message in a structured format. A message dictionary can be configured to identify a type of the message received and to lexically identify data elements of the message using the message dictionary and the type of message. In addition, a taxonomy module can be configured to provide a semantic meaning for the data elements of the lexically identified portions of the message. Further, a data definition tag repository can store data definition tags and link the message dictionary, the taxonomy, and storage location of the data elements in the storage module. The data definition tags can enable the semantic meaning of data elements to be queried. ## Claims ### Claim 1 A system for associating semantic meaning with data elements, comprising: a messaging module configured to receive a message having data elements; a message dictionary to identify a type of the message received and to lexically identify data elements of the message using the message dictionary and the type of message; a storage module to store the data elements in a structured format; a taxonomy module configured to provide a semantic meaning for the data elements in the lexically identified portions of the message; a data definition tag repository configured to store data definition tags and link the message dictionary, the taxonomy, and storage location of the data elements in the storage module to enable a semantic meaning of data elements to be queried. ### Claim 2 (depends on 1) The system as in claim 1, wherein the data elements have data definition tags associated with the data elements based on the location that the data elements are defined to appear in the message by the message dictionary. ### Claim 3 (depends on 1) The system as in claim 1, further comprising a semantic view module configured to generate semantic views of the data elements based on a taxonomy from the taxonomy module and using the data definition tags. ### Claim 4 (depends on 1) The system as in claim 1, further comprising a mapping view module configured to generate a combined semantic view using application metadata. ### Claim 5 (depends on 1) The system as in claim 1, further comprising a specific application used to query information about a semantic data topic. ### Claim 6 (depends on 1) The system as in claim 1, further comprising an application metadata module configured to provide information to create mapping views dynamically and to provide data to the application for combining multiple semantic views based on metadata associated with the application data specifications. ### Claim 7 (depends on 1) The system as in claim 1, wherein the mapping view module can merge a plurality of taxonomies provided by a plurality of applications into a shared taxonomy. ### Claim 8 (depends on 1) The system as in claim 1, wherein the storage module has a relational database and the relational database includes relational tables for storing the data elements in a storage device; and a processor to process retrieval of data elements from the relational database. ### Claim 9 (depends on 1) The system as in claim 1, wherein the messaging module can infer the message dictionary associated with the message based on message characteristics. ### Claim 10 (depends on 1) The system as in claim 1, wherein the taxonomy module is configured to create derived fields by referencing relationships specified between specific data fields using a taxonomy in the taxonomy module. ### Claim 11 A method for associating semantic meaning with data elements, comprising: receiving a message having data elements; identifying lexical divisions in the message using a message dictionary to identify a type of a message and expected locations of data elements in the message; providing a taxonomy that includes a semantic meaning for the data elements; storing the data elements in storage locations of a storage module in a structured format; and linking the storage locations of the data elements with the taxonomy and message dictionary using data definition tags in a data tag repository, to enable data elements stored in the storage module to be queried based on semantic meanings of the data elements. ### Claim 12 (depends on 11) The method as in claim 11, further comprising associating taxonomic tags with data elements based on the location that the data elements are defined to appear in the message using the message dictionary. ### Claim 13 (depends on 11) The method as in claim 11, further comprising expressing a data view in terms of a taxonomy query using a semantic view module. ### Claim 14 (depends on 11) The methods as in claim 11, further comprising inferring the message dictionary associated with the message based on message characteristics. ### Claim 15 (depends on 11) The method as in claim 11, further comprising creating mapping views dynamically to provide data views to an application by combining multiple semantic views based on application metadata associated with the application. ### Claim 16 (depends on 11) The method as in claim 11, further comprising merging a plurality of taxonomies provided by a plurality of applications into a shared taxonomy. ### Claim 17 (depends on 11) The method as in claim 11, further comprising creating derived fields by referencing relationships specified between specific data elements using the taxonomy. ### Claim 18 (depends on 11) The system as in claim 11, further comprising creating semantic views of the data elements based on taxonomy queries. ### Claim 19 A method for associating semantic meaning with data elements, comprising: receiving a message having data elements; identifying lexical portions of the message using a message dictionary to identify a type of a message and expected locations of data elements in the message; providing a taxonomy that includes possible semantic definitions for the data elements; storing the data elements in a storage format of a storage module; and linking a stored location of the data elements with the taxonomy and message dictionary using data definition tags stored in a repository, to enable the semantic meaning of data elements stored in the storage module to be queried; and creating semantic views of the data elements based on relationships in the taxonomy. ### Claim 20 (depends on 19) The method of claim 19, further comprising merging a plurality of taxonomies provided by a plurality of applications into a shared taxonomy.