# US 2006/0242141 A1 · Abstracted metadata policy component and related architecture

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2006/0242141 A1
- Document ID: US20060242141A1
- Status: Published application
- Kind: A1
- Application number: 11/112,765
- Filed: 2005-04-21
- Published: 2006-10-26
- Earliest claimed: 2005-04-21
- Assignees: Microsoft Corporation
- Inventors: Richard Turner; David Albert; Eric Vandenberg; Peter Gurevich; Robert Wlodarczyk; Robert Sinclair; Thomas Olsen; Tomasz Kasperkiewicz
- Web page: https://patentgrep.com/patent/US20060242141A1

## CPC

- G06F 16/58: Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
- G06F 16/48: Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
- Y10S 707/99935: Query augmenting and refining, e.g. inexact access
- Y10S 707/99942: Manipulating data structure, e.g. compression, compaction, compilation
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## Abstract

A method and architecture for reading and updating metadata. A policy component is arranged to receive a request to read or update metadata that may include metadata from a plurality of standards. Each metadata format potentially includes a field corresponding to the request. The policy component determines which fields to read or update in satisfying the request by consulting a repository. The repository includes mappings that map information included in the request (e.g., a path) to locations in the metadata corresponding to the request. The policy component uses the locations to read or update the metadata.

## Claims

### Claim 1

A computer-readable medium having computer-executable instructions, comprising:
receiving a path parameter, wherein the path parameter maps to locations in metadata, wherein the metadata is formatted in a plurality of formats, wherein each of the formats potentially includes a field corresponding to the path parameter;
in response to receiving the path parameter, causing at least one output to be returned, wherein locations in the metadata that map to the path parameter are obtained and wherein the at least one output corresponds to one of the locations.

### Claim 2 (depends on 1)

The computer-readable medium of claim 1, wherein the path parameter comprises a non fully-qualified path.

### Claim 3 (depends on 2)

The computer-readable medium of claim 2, wherein obtaining locations in the metadata that map to the path parameter comprises using the non fully-qualified path as a key to find the locations in a repository.

### Claim 4 (depends on 1)

The computer-readable medium of claim 1, further comprising determining the one of the locations by finding a first one of the locations that exists in the metadata.

### Claim 5 (depends on 4)

The computer-readable medium of claim 4, wherein the locations are stored in a repository in an order of preference and searched in the order to find the first one of the locations that exists in the metadata.

### Claim 6

In a computing environment, a method, comprising:
receiving a request to update metadata, wherein the metadata is formatted in a plurality of formats, wherein each of the formats potentially includes a field associated with the update;
obtaining locations in the metadata that indicate fields in the metadata that correspond to the update;
updating the metadata via the locations.

### Claim 7 (depends on 6)

The method of claim 6, wherein the request comprises a path that does not explicitly identify a location in the metadata to update.

### Claim 8 (depends on 7)

The method of claim 7, wherein obtaining locations in the metadata that indicate fields in the metadata that correspond to the update comprises accessing a repository to obtain a list of mappings that map the path to one or more locations in the metadata.

### Claim 9 (depends on 6)

The method of claim 6, wherein the locations are ordered and wherein updating the metadata via the locations comprises updating a field at a first location in the metadata and deleting all other fields indicated by the locations.

### Claim 10 (depends on 6)

The method of claim 6, wherein updating the metadata via the locations comprises updating each field indicated by each location with a value to keep the fields consistent.

### Claim 11 (depends on 6)

The method of claim 6, wherein updating the metadata via the locations comprises one or more of creating a new field, updating an existing field, and deleting a field indicated by the locations.

### Claim 12 (depends on 6)

The method of claim 6, further comprising updating fields at other locations in accordance with a metadata specification associated with one of the formats.

### Claim 13 (depends on 12)

The method of claim 12, wherein at least some of the rules specified by the metadata specification are stored in a repository that is accessed when updating the fields at the other locations.

### Claim 14

In a computing environment, an apparatus, comprising:
a policy component arranged to receive a request to read or update metadata, wherein the metadata is formatted in a plurality of formats, wherein each of the formats potentially includes a field associated with the request, wherein the policy component is further arranged to determine which fields to read or update in satisfying the request; and
a repository arranged to store mappings that map information included in the request to locations in the metadata corresponding to the request.

### Claim 15 (depends on 14)

The apparatus of claim 14, further comprising a metadata reader arranged to read data formatted in one of the formats, wherein the policy component is further arranged to communicate with the metadata reader when reading metadata.

### Claim 16 (depends on 14)

The apparatus of claim 14, further comprising a metadata writer arranged to update data formatted in one of the formats, wherein the policy component is further arranged to communicate with the metadata reader when updating metadata.

### Claim 17 (depends on 14)

The apparatus of claim 14, wherein determining which fields to read in satisfying the request comprises obtaining the mappings -from the repository and finding a first one of the locations for which metadata exists.

### Claim 18 (depends on 14)

The apparatus of claim 14, wherein determining which fields to update in satisfying the request comprises obtaining the mappings from the repository and updating a field corresponding to each location.

### Claim 19 (depends on 14)

The apparatus of claim 14, wherein determining which fields to update in satisfying the request comprises obtaining the mappings from the repository, updating a single field corresponding to a location, and deleting the other fields corresponding to other locations.
