JPH05216799A - Name managing system - Google Patents

Abstract

PURPOSE:To manage the correspondence of a name related to conversion by automatically converting the name of a certain name space to the name of the other name space regardless of limit concerning the syntax rule of the name, usable character group or the length of the name. CONSTITUTION:A syntax rule converting means 2 converts the name based on the difference of the syntax rule of the names between the name space at the converting source and the name space at the converting destination. A character converting means 4 converts the name based on the difference of the usable character group between the name space at the converting source and the name space at the converting destination. An overlap-proof name preparing means 7 executes a processing for preparing any name not to be overlapped with the name already defined in the name space at the converting destination. Name managing means 8, 10 and 12 register and manage data concerning correspondence between the name in the name space at the converting source and the name in the name space at the converting destination.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a name management system, and more particularly to a plurality of name spaces corresponding to a plurality of computers in a network (computer network composed of a plurality of computers using common resources (computer resources)). The present invention relates to a name management method for converting names between names and for associating names (names indicating the same resource in different name spaces).

[0002]

2. Description of the Related Art Conventionally, in this type of name management system, it is possible to convert a name in one namespace to automatically create a name in another namespace and to associate the names with each other. In the namespace (namespace corresponding to the above "some namespace") and the destination namespace (namespace corresponding to the above "other namespace"), the syntax rules of the names and available characters It was limited to the case where the groups (groups of characters constituting the name) were the same. If the name syntax rules and available characters are different, the administrator who manages each namespace
It was converted and matched.

Regarding the limitation on the length of the name, when the length of the converted name exceeds the limitation of the length of the name in the conversion destination namespace, the conversion is not performed and the name itself is ignored. Or, the converted name was truncated in the middle.

[0004]

In the above-mentioned conventional name management method, it is possible to automatically convert a name between different namespaces, and the syntax rule of the name and the usable character group are the same. Since it is limited to, the conversion by human (administrator) is required for other conversions,
There was a drawback that the burden on the administrator was large.

If the length of the name after conversion exceeds the limit of the length of the name in the name space of the conversion destination, the name itself is ignored without conversion, or the name after conversion is truncated. However, there is a drawback that the name may not be used or there is a risk that different resources are equated.

In view of the above points, an object of the present invention is to convert the name of one namespace to convert the name of another namespace regardless of the syntax rules of the name, restrictions on the usable character groups and the length of the name. To provide a name management method that can automatically create a name that does not duplicate a name that already exists in the other namespace when creating a name and can associate the name related to the creation is there.

[0007]

According to the name management method of the present invention, in the name management method for managing the names of resources in the network, the difference in the syntax rules of names between the conversion source namespace and the conversion destination namespace. Syntax conversion means for performing name conversion based on the above, character conversion means for performing name conversion based on the difference in the usable character group between the conversion source namespace and the conversion destination namespace, and the conversion destination namespace Registration of data to avoid duplication avoiding name creation process that creates a name that does not duplicate the name already defined in the above, and the correspondence between the source namespace name and the destination namespace name. And a name management means for managing.

[0008]

In the name management system of the present invention, the syntax rule conversion means performs the name conversion based on the difference in the syntax rules of the names in the conversion source namespace and the conversion destination namespace, and the character conversion means Performs name conversion based on the difference in the usable character groups between the namespace and the destination namespace, and creates a name that does not duplicate the name that is already defined in the destination namespace by the duplicate avoidance name creation method. The name management means registers and manages data relating to the correspondence between the name of the conversion source namespace and the name of the conversion destination namespace.

[0009]

The present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of an embodiment of the name management system of the present invention. The name management system of the present embodiment is a name creation control means 1 for performing overall control when converting an arbitrary name existing in an arbitrary namespace and creating a name that can exist in another namespace. A syntax rule conversion means 2 for converting a name based on a difference in a syntax rule between names in a conversion source namespace and a conversion destination namespace, and syntax rule data 3 having data regarding a syntax rule for a name in each namespace. , Character conversion means 4 for performing name conversion (character conversion) based on the difference in usable character groups in the conversion source namespace and the conversion destination namespace, and character conversion data 5 having data relating to character conversion, Namespace 6 (namespace (A)), which is a namespace corresponding to the computer (referred to as computer A) in which the name management method of the present embodiment is implemented, and the namespace of the conversion destination have already been defined. That a processing overlap avoidance name creating unit 7 for to create a unique name to name, the name management device 8 for registration and management of (A) (B) name association data 9,
It has data on the correspondence between the name existing in the namespace (A) and the name existing in the namespace (B) (A)
(B) Name association data 9, (A) (C) Name association means 10 for registering and managing the name association data 11, Names existing in the namespace (A) and existing in the namespace (C) (A) (C) name association data 11 having data relating to association with a name
(D) Name management means 12 for registering and managing the name association data 13, and data relating the association between the name existing in the namespace (A) and the name existing in the namespace (D) (A). (D) Name association data 1
And 3 are included.

FIG. 2 shows a process (name a → name a1 → name a2 → name a3 → name a4) of converting an arbitrary name (here, name a) by the name management system of this embodiment.
And FIG.

FIG. 3 is a diagram for explaining a mode in which an arbitrary name (here, name a) is divided by the syntax rule conversion means 2 based on the syntax rule of the name in the namespace of the conversion destination. is there.

FIG. 4 shows that "characters in the character group usable in the namespace (A) and characters in the character group usable in the namespace (B) included in the character conversion data 5 are associated with each other. Is a diagram showing "data for".

FIG. 5 is a diagram for explaining the processing by the duplicate avoidance name creating means 7.

Next, the operation of the name management system of the present embodiment thus constructed will be described.

First, the name a existing in the namespace (A)
Will be described and a name a4 existing in the namespace (B) will be created (in this case, the namespace (A) corresponds to the "source namespace", and the namespace ( B) corresponds to the "namespace of the conversion destination") (see FIG. 2).

The name creation control means 1 uses the name space (A)
An arbitrary name a existing in (name space 6) is taken out and passed to the syntax rule conversion means 2.

The syntax rule conversion means 2 uses the syntax rule data 3
Namespaces in (A) Name syntax rules and namespaces (B)
In accordance with the syntax rules of the name, the name a is converted into a part p1 (a part requiring character conversion), a part p2 (a part not requiring conversion) and a part p3 (a part performing conversion other than character conversion).
(See FIG. 3) and the name a after division is passed to the name creation control means 1.

The name creation control means 1 passes the divided name a to the character conversion means 4.

The character conversion means 4 converts the part p1 in the name a based on the character conversion data 5. That is, the character conversion means 4 refers to the character conversion data 5 to convert each character forming the part p1 of the name a that needs character conversion to
Convert to a character in the character group that can be used in the namespace (B). For example, as shown in FIG. 4, the character "a" that can be used in the namespace (A) is replaced with the character "A" that can be used in the namespace (B), and the character "A" that can be used in the namespace (A) is replaced. Replace "b" with the letter "B" available in namespace (B).

The character converting means 4 also adjusts the length of the name of the portion p1 based on the limitation of the length of the name of the namespace (B). That is, when the name length limit in the namespace (B) is exceeded, extra characters (characters exceeding the length limit) are truncated from the portion p1.

The part p1 thus converted (character conversion) is called a part p1 ', and the part p1 in the name a is called.
The name after 1 is converted into the part p1 'is called the name a1 (see FIG. 2).

The character conversion means 4 transfers the name a1 to the name creation control means 1, and the name creation control means 1 transfers the name a1 to the syntax rule conversion means 2.

The syntax rule conversion means 2 uses the syntax rule data 3
Based on the above, the part p3 in the name a1 is converted. In addition,
The part p3 is a part in which conversion other than the character conversion in the part p1 (character conversion corresponding to one-to-one as shown in FIG. 4) is performed, and means the following part. It is a character string that represents a specific function related to a resource accessed by a name that has self (part p3), and a partial namespace (which is determined to be converted to a specific character string (including a character string of one character) ( A) A portion indicating a character string (such as a character string including all or part of the name b) for specifying the resource pointed to by the name b other than the name a

In the conversion of the part p3 corresponding to the above, the syntax rule conversion means 2 refers to the syntax rule data 3 and replaces a specific character string in the part p3 with a fixed character string. Further, in the conversion of the part p3 corresponding to the above, the part p3 is converted into the name in the namespace (B) corresponding to the already converted name b by referring to the (A) and (B) name correspondence data 9. Replace.

The part p3 thus converted is called a part p3 ', and the part p3 in the name a1 is the part p3.
The name after being converted into 3'is called a name a2 (see FIG. 2).

Since the part p2 does not need to be converted,
In the name space (B), the character string in the part p2 is used as it is (therefore, the name a2 has the part p2).

After the conversion from the part p3 to the part p3 'is completed, the syntax rule conversion means 2 follows the syntax rules of the name of the namespace (B) in the syntax rule data 3 to generate the parts p1', p2 and parts. Assemble p3 '. Further, the syntax rule conversion means 2 follows the syntax rules of the name in the namespace (B) to select arbitrary character strings (including a character string of one character) α and β.
Between the parts. The name after such assembly and insertion is called the name a3 (see FIG. 2).

In FIG. 2, part p2 is not converted in the process of converting name a to name a3, but part p1 is converted.
Has been converted to the part p1 ', and the part p3 is the part p3'.
Has been converted to. Further, the character strings α and β are inserted in the name a3.

The syntax rule conversion means 2 is the name creation control means 1
The name a3 to the duplicate avoidance name creating means 7.

The duplicate avoidance name creating means 7 determines, via the name managing means 8, whether or not the name a3 already exists (is already defined) in the namespace (B).

In the above judgment, "name a3 is namespace (B)
If it does not exist ”, the duplicate avoidance name creating means 7 sets the name a3 to the name a4.

In the above judgment, "name a3 is namespace (B)
Exists, the duplicate avoidance name creating means 7 further transforms the name a3 to create a name that does not duplicate a name already defined in the namespace (B). That is, the duplicate avoidance name creating means 7 converts the name a3 in the following procedure (see FIGS. 5A to 5F).

In the name a3, the character string included in the character-converted portion p1 ′ is referred to as a character string q0 (see FIG. 5A).

The length of the character string when the length of the name a3 matches the name length limit of the namespace (B) is max.
Let q.

When the length of the character string q0 is shorter than maxq, the character string q0 is set as the character string q (FIG. 5B).
reference). If the length of the character string q0 is equal to maxq, the last character of the character string q0 is truncated and the character string q0 is truncated.
(See FIG. 5C).

If the name formed by replacing the character string q0 in the name a3 with the character string q does not overlap the name already existing in the namespace (B), the name is set to the name a4.

A character string (including a character string of 1 character) that can be used in the namespace (B) is added after the character string q to create a character string q ′ whose length does not exceed maxq (see FIG. See d)).

The character string q ′ is replaced with the character string q0 to convert the name a3 into the name x (see FIG. 5 (e)).

It is determined whether or not the name x is the same as the name existing in the namespace (B), and if not, the name x is set as the name a4. In the case of overlapping in the above determination, the process of and is repeated (a character string different from the previous process is added to the end of the character string q in the process of) and repeated until it is determined that there is no overlap in the above determination. ..

The last character is truncated from the character string q set in (3) to form a character string q ″ (see FIG. 5F).

The character string q ″ is replaced with the character string q, and the procedure from to is repeated.

The part p1 'after the conversion by the duplicate avoidance name creating means 7 is called a part p1'', and the name after the conversion of the name a3 is called the name a4 (see FIG. 2).
(See (e)).

The duplicate avoidance name creating means 7 passes the name a4 to the name managing means 8.

The name management means 8 registers the association between the name a4 and the name a in the (A) and (B) name association data 9, and the name a and the namespace (B) existing in the namespace (A).
Manages the association with the name a4 existing in the. That is, after the above registration, the name a in the namespace (A)
And the name a4 in the namespace (B) refer to the same resource.

Second, as described above, "name a4 and name a4"
After the registration of "Correlation with", when an arbitrary name in the namespace (A) is accessed, the name (here, namespace (B)) in another namespace (here, namespace (B)) corresponding to the name a is accessed. Now, the operation when the name a4) is requested will be described. The resource indicated by the name a in the namespace (A) and the name a4 in the namespace (B) (the name a in the namespace (A) and the name a4 in the namespace (B) represent the same resource in the network). Are present in a computer (referred to as computer B) corresponding to the namespace (B).

When the resource designated by the name a is accessed in the computer A, the name management means 8
(A) (B) With reference to the name association data 9, the name a4 corresponding to the name a is extracted and passed to the computer B.

Computer B uses name a4 to access the resource pointed to by name a4 for the user of computer A.

[0049]

As described above, according to the present invention, after the name conversion based on the difference in the syntax rules of the name and the name conversion based on the difference in the usable character groups, the conversion destination namespace is Converts names in a namespace, regardless of syntax rules for names, restrictions on available character sets, or name length restrictions, by taking steps to create names that do not duplicate names defined in. When creating a name for another namespace, a name that does not duplicate a name that already exists in the other namespace is automatically created (without the need for an administrator) and created. There is an effect that the names can be associated with each other.

With this effect, the same resource can be efficiently managed and used in any of the plurality of computers corresponding to the plurality of namespaces in the network.

[Brief description of drawings]

FIG. 1 is a block diagram showing the configuration of an embodiment of the present invention.

FIG. 2 is a diagram for explaining a process of converting a name according to the name management method shown in FIG.

FIG. 3 is a diagram for explaining a mode in which a name is divided by the syntax rule conversion means in FIG.

FIG. 4 is a diagram showing an example of data showing association of character groups of names in the character conversion data in FIG.

FIG. 5 is a diagram for explaining processing (name conversion procedure) performed by the duplicate avoidance name creating means in FIG. 1;

[Explanation of symbols]

 1 name creation control means 2 syntax rule conversion means 3 syntax rule data 4 character conversion means 5 character conversion data 6 name space 7 duplicate avoidance name creation means 8, 10, 12 name management means 9 (A) (B) name correspondence data 11 (A) (C) name association data 13 (A) (D) name association data

Claims (1)

[Claims] 1. A name management method for managing the names of resources in a network, and a syntax rule conversion means for converting a name based on a difference in a syntax rule of a name between a conversion source namespace and a conversion destination namespace. , Character conversion means that performs name conversion based on the difference between the usable character groups in the source namespace and the destination namespace, and a name that does not duplicate the name already defined in the destination namespace A name management means for registering and managing data related to the correspondence between the name of the conversion source namespace and the name of the conversion destination namespace. Characteristic name management method.