# US 2008/0306947 A1 · Taxonomy editor

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

- Number: US 2008/0306947 A1
- Document ID: US20080306947A1
- Status: Published application
- Kind: A1
- Application number: 11/808,319
- Filed: 2007-06-08
- Published: 2008-12-11
- Earliest claimed: 2007-06-08
- Assignees: Hewlett-Packard Development Company, L.P.
- Inventors: Pavel Kolesnikov
- Web page: https://patentgrep.com/patent/US20080306947A1

## CPC

- G06F 16/367: {Ontology}
- G06F 16/907: Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A repository 10 stores metadata, including at least one taxonomy definition 16 and records 14, which may be classified using the defined taxonomies. An editor 20 may be used to edit taxonomy definitions, using a local copy 22. To check the edit, a taxonomy search service in repository 10 may be called to check for consistency, whether or not the data in the repository 10 exposed on repository interface 18.

## Claims

### Claim 1

A method of operating a repository, comprising:
storing at least one taxonomy definition defining a taxonomy and the plurality of taxonomy values in the repository;
storing records having associated taxonomy values in the repository;
editing the taxonomy definition of at least one taxonomy in a taxonomy editor; and
calling a repository service from the taxonomy editor for at least one candidate taxonomy to cause the repository service to search the metadata repository for inconsistency between the at least one candidate taxonomy and the data stored in the repository.

### Claim 2 (depends on 1)

A method according to claim 1 wherein
the repository is a stateless metadata repository having an interface;
the step of calling a repository service comprises sending a message from the taxonomy editor to the interface of the metadata repository, the message indicating the candidate taxonomy;
the method further comprising sending a reply message from the interface of the metadata repository, the message including information from the repository service regarding any inconsistency found between the candidate taxonomy and the at least one taxonomy definition and/or the records in the repository.

### Claim 3 (depends on 2)

A method according to claim 2, wherein the interface of the metadata repository exposes at least one check routine, the method including calling the or each check routine to cause the repository service to check for a specific inconsistency between the at least one candidate taxonomy and the data stored in the repository.

### Claim 4 (depends on 3)

A method according to claim 3 comprising calling a deleted taxonomy check routine to check for any records using as a data type any deleted taxonomy or using as a data value a deleted value from the at least one candidate taxonomy.

### Claim 5 (depends on 3)

A method according to claim 3 comprising calling a deleted data values check routine to check for any records using data including data values deleted from the at least one candidate taxonomy.

### Claim 6 (depends on 3)

A method according to claim 3 comprising calling a duplicate taxonomy check routine to check for any data types defined using any deleted taxonomies or deleted taxonomy values from the at least one candidate taxonomy.

### Claim 7 (depends on 3)

A method according to claim 3 comprising calling a deleted taxonomy check routine to check for any duplicated taxonomy identifiers with the at least one candidate taxonomy.

### Claim 8 (depends on 1)

A method according to claim 1 wherein each taxonomy has a taxonomy identifier, and the method comprises:
calling the repository service to check for any duplicated taxonomy identifiers with the at least one candidate taxonomy;
calling the repository service to check for any data types defined using any deleted taxonomies or taxonomy values from the at least one candidate taxonomy;
calling the repository service to check for any records using as a data type any deleted taxonomies from the at least one candidate taxonomy; and
calling the repository service to check for any records using data values deleted from any of the at least one candidate taxonomy.

### Claim 9

A repository system, including:
a metadata repository storing metadata including records defining taxonomies and records using the taxonomies to define taxonomy values, the metadata repository having a service interface exposing a data update service for updating the data in records and also exposing a taxonomy search service; and
a taxonomy editor arranged as a client of the metadata repository, arranged to call the data update service to edit the definitions of taxonomies and to edit the taxonomy values stored in records;
wherein the taxonomy editor is arranged to call the taxonomy search service for at least one called taxonomy to cause the taxonomy search service to search the metadata repository for inconsistency between the at least one called taxonomy and the metadata stored in the repository.

### Claim 10 (depends on 9)

A repository system according to claim 9 wherein the taxonomy search service is arranged to return the identity of records having a taxonomy value incompatible with the at least one called taxonomy.

### Claim 11 (depends on 9)

A repository system according to claim 9 wherein the taxonomy search service is arranged to return the identity of records having a data type incompatible with the at least one called taxonomy.

### Claim 12 (depends on 9)

A repository system according to claim 9 wherein the taxonomy search service is arranged to return the identity of records having a data value incompatible with the at least one called taxonomy.

### Claim 13 (depends on 9)

A repository system according to claim 9 wherein the taxonomy search service is arranged to return any data type defined using the at least one called taxonomy or values from the at least one called taxonomy that are no longer available.

### Claim 14 (depends on 9)

A repository system according to claim 9 wherein each taxonomy has an identity number; and
the taxonomy search service is arranged to return any taxonomy having a duplicate identity number to the at least one called taxonomy.
