# US 2008/0288549 A1 · Translating case-sensitive technical identifiers

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

- Number: US 2008/0288549 A1
- Document ID: US20080288549A1
- Status: Published application
- Kind: A1
- Application number: 11/803,642
- Filed: 2007-05-14
- Published: 2008-11-20
- Earliest claimed: 2007-05-14
- Assignees: Sap SE
- Inventors: Christian Rabetge; Otto Boehrer
- Web page: https://patentgrep.com/patent/US20080288549A1

## CPC

- G06F 16/10: File systems; File servers
- Y10S 707/99932: Access augmentation or optimizing
- 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

From a case-sensitive technical identifier referencing a resource and having upper case letters, a bit string is generated. The bit string identifies whether each letter in the case-sensitive technical identifier is upper case or lower case. In addition, the upper case letters in the case-sensitive technical identifier are converted to lower case and are concatenated with the bit string to generate a case-insensitive technical identifier. Related systems, apparatus, methods, and/or articles are also described.

## Claims

### Claim 1

An article comprising a tangibly-embodied machine-readable medium operable to cause one or more machines to result in operations comprising:
accessing a case-sensitive technical identifier referencing a resource and having upper case letters;
generating a bit string based on the case-sensitive technical identifier, the bit string identifying whether each letter in the case-sensitive technical identifier is upper case or lower case;
converting the upper case letters in the case-sensitive technical identifier to lower case; and
concatenating the converted case-sensitive technical identifier with the bit string to generate a case-insensitive technical identifier.

### Claim 2 (depends on 1)

An article as in claim 1, wherein the article is further operable to cause one or more machines to result in operations comprising:
storing the case-insensitive technical identifier to allow access to the resource in a case-insensitive environment.

### Claim 3 (depends on 1)

An article as in claim 1, wherein the case-sensitive technical identifier further includes numbers and up to ten special characters, and wherein upper case numbers in the bit string correspond to the ten special characters.

### Claim 4 (depends on 3)

An article as in claim 3, wherein one of the ten special characters corresponds to a blank.

### Claim 5 (depends on 1)

An article as in claim 1, wherein the case-insensitive technical identifier characterizes a file name.

### Claim 6 (depends on 1)

An article as in claim 1, wherein the case-sensitive technical identifier is a uniform resource identifier.

### Claim 7 (depends on 1)

An article as in claim 1, wherein the article is further operable to cause one or more machines to result in operations comprising:
transmitting the case-insensitive technical identifier to a requesting node to allow access to the resource in a case-insensitive environment.

### Claim 8

A computer-implemented method comprising:
accessing a case-sensitive technical identifier referencing a resource and having upper case letters;
generating a bit string based on the case-sensitive technical identifier, the bit string identifying whether each letter in the case-sensitive technical identifier is upper case or lower case;
converting the upper case letters in the case-sensitive technical identifier to lower case; and
concatenating the converted case-sensitive technical identifier with the bit string to generate a case-insensitive technical identifier.

### Claim 9 (depends on 8)

A method as in claim 8, further comprising:
storing the case-insensitive technical identifier to allow access to the resource in a case-insensitive environment.

### Claim 10 (depends on 8)

A method as in claim 8, wherein the case-sensitive technical identifier further includes numbers and up to ten special characters, and wherein upper case numbers in the bit string correspond to the ten special characters.

### Claim 11 (depends on 10)

A method as in claim 10, wherein one of the ten special characters corresponds to a blank.

### Claim 12 (depends on 8)

A method as in claim 8, wherein the case-insensitive technical identifier characterizes a file name.

### Claim 13 (depends on 8)

A method as in claim 8, wherein the case-sensitive technical identifier is a uniform resource identifier.

### Claim 14 (depends on 8)

A method as in claim 8, further comprising transmitting the case-insensitive technical identifier to a requesting node to allow access to the resource in a case-insensitive environment.

### Claim 15

An article comprising a tangibly-embodied machine-readable medium operable to cause one or more machines to result in operations comprising:
accessing a case-insensitive technical identifier referencing a resource and having no upper case letters, the case-insensitive technical identifier including a bit string identifying whether each letter in the case-insensitive technical identifier is upper case or lower case;
determining a length of the bit string and separating the bit string from the letters in the case-insensitive technical identifier; and
converting letters in the case-insensitive technical identifier identified in the bit string to upper case to generate the case-sensitive technical identifier.

### Claim 16 (depends on 15)

An article as in claim 15, wherein the article is further operable to cause one or more machines to result in operations comprising:
storing the case-sensitive technical identifier to allow access to the resource in a case-sensitive environment.

### Claim 17 (depends on 15)

An article as in claim 15, wherein the case-sensitive technical identifier further includes numbers and up to ten special characters, and wherein upper case numbers in the bit string correspond to the ten special characters.

### Claim 18 (depends on 17)

An article as in claim 17, wherein one of the ten special characters corresponds to a blank.

### Claim 19 (depends on 15)

An article as in claim 15, wherein the case-insensitive technical identifier characterizes a file name.

### Claim 20 (depends on 15)

An article as in claim 15, wherein the case-sensitive technical identifier is a uniform resource identifier.
