JP2012181740A - Information storage device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information storage device in which a system is not complicated even if the device is enlarged along with an increase in the number of uses and the number of data, while allowing various functions to be provided by one kind of data structure utilizing a graph model (oriented graph).SOLUTION: An information storage device uses a graph model which accumulates information by using a data structure constituted of item node dara 111, link node data 112, and arc data 113 of a storage part 11. In this information storage device, when data input/output means 121 accepts a data manipulation request to an item node or a link node and identifies a data change request accompanied by generation of an arc, node connection propriety determination means 124 determines whether or not the upstream and downstream sides of the arc after changed are both the item nodes. Data change means 123 prohibits the data change if the upstream and downstream sides are both the item nodes, and performs the data change if any one (both) of the upstream and downstream sides is (are) not the item node(s).

Description

  The present invention relates to an information storage apparatus capable of storing a plurality of information storage methods such as bulletin board type, diary type, mail type, and shared folder type in a single data model by using a graph model.

  For services such as e-mail, WEB page, blog and bulletin board, a database is constructed for each service. For this reason, when coordinating while providing a large number of services, it is necessary to prepare a large number of databases and to build an information sharing infrastructure for linking them, which increases the cost of system development. .

  In order to solve this problem, there has been proposed an information retrieval apparatus that accumulates and retrieves information by various information accumulation methods using a single data model composed of a graph model and a rule table (Patent Document 1). ).

JP 2001-209647 A

  However, in the conventional graph model, when a relationship between a plurality of nodes is added, the number of edges (arcs) connecting the nodes increases by the added amount. For this reason, when the number of accumulated nodes becomes enormous, the number of edges (arcs) also becomes enormous, and the relationship between edges (arcs) becomes more complicated accordingly. Therefore, in the conventional method, there is a problem that when the stored information is organized, it is necessary to organize the complicatedly intertwined edges (arcs) while unraveling them. In particular, in the conventional graph model, the user can freely design a node and an edge (arc), and this problem arises.

  An object of the present invention is to provide information storage that can provide various functions with one type of data structure using a directed graph model, but does not complicate the system even when the number of users and data increases. To provide an apparatus.

  In order to solve such a problem, the present invention provides an item node composed of identifiers of both upstream arcs and downstream arcs and item information to be accumulated, and identifiers of either or both of upstream arcs and downstream arcs. A storage unit storing a data structure composed of a link node consisting of the above and an arc consisting of identifiers of upstream and downstream item nodes or link nodes, and control for storing information using the data structure of the storage unit An information storage device using a graph model having a unit, wherein the control unit accepts a data operation request to an item node or a link node, and identifies whether it is a data change request accompanied by generation of an arc If the input / output means to be used and a data change request accompanied by the generation of an arc, both the upstream and downstream sides of the arc after the change If the upstream and downstream are both item nodes, the data change is prohibited, and if either or both of the upstream and downstream sides are not item nodes, There is provided an information storage device characterized by comprising a change means for executing data change. Thereby, connection between item nodes is prohibited, and the connection relation between nodes can be prevented from becoming complicated.

  In such an information storage device, the arc in the data structure further includes label information indicating the attribute of the arc, and when the control unit receives a reference request from the input / output means to the item node or the link node, the item node or the It is preferable to further include a reference means for outputting result information including label information of arcs connected to the link node. Thus, by generating the arc by including the relationship between the node on the upstream side of the arc and the node on the downstream side of the arc in the label information, the relationship between the nodes can be shown to the user at the time of reference.

  Further, in the information storage device, the link node further includes access control information to the link node and an item node connected by a downstream arc of the link node, and the control unit further uses the access control information to link the link node. And an authority determining means for determining an operation authority for the item node, and upon receiving a data operation request from the input / output means to the item node or the link node, the operation authority for the access control information of the item node or the link node It is preferable to execute the data manipulation process according to the determination. Accordingly, since the link node holds access control information regarding all item nodes and arcs, it is possible to easily manage access control of an item node group connected downstream of a certain link node.

  According to the present invention, information relating to a plurality of services such as a bulletin board, a diary, and mail is stored in the item node, and the item node is connected via the link node, grouping and hierarchization to facilitate control of the item node, It is possible to provide an information storage device that prevents the connection relationship between item nodes from becoming complicated.

1 is a configuration diagram of an information storage sharing system using an information storage apparatus according to the present invention. FIG. It is a figure explaining a data model. It is a figure explaining a data structure. It is a figure explaining the access control range of a link node. It is a process flowchart at the time of the data operation request reception of a server apparatus. It is a flowchart of an arc connection change process. It is a figure explaining an example of information storage sharing between users. It is a figure explaining the example of the node data in FIG. 7, and arc data. FIG. 8 is an example of a screen displayed on the user terminal device 2 by the node of FIG. It is a figure explaining the example which transmits / receives mail between the users of FIG. It is a figure explaining the example of the node data in FIG. 10, and arc data. FIG. 11 is an example of a screen displayed on the user terminal device 2 by the node of FIG. It is a figure explaining the example which shares a diary between the users of FIG. It is a figure explaining the example of the node data in FIG. 13, and arc data. 14 is an example of a screen displayed on the user terminal device 2 by the node of FIG. It is a figure explaining the example which shares a bulletin board between the users of FIG. It is a figure explaining the example of the node data in FIG. 16, and arc data. FIG. 17 is an example of a screen displayed on the user terminal device 2 by the node of FIG.

  Embodiments of an information storage apparatus according to the present invention will be described below with reference to the drawings.

  FIG. 1 is a block diagram of an information storage and sharing system using an information storage apparatus according to the present invention. The information storage / sharing system shown in FIG. 1 is connected to the server device 1 via the network 3 and the server device 1 which is an information storage device according to the present invention, and refers to the information stored in the server device 1. It is comprised from the user terminal device 2 which the user who accesses accesses.

  The server device 1 is a so-called computer system, and provides services such as addition, reference, change, and deletion of items, which are information to be stored, to the user terminal device 2 via the network 3. The server device 1 includes a communication interface (I / F) unit 13 that communicates with the user terminal device 2 through the network 3, a control unit 12 that performs various controls of the server device 1, and a storage unit 11.

  The storage unit 11 includes a storage device such as a ROM, a RAM, and a magnetic hard disk, and stores various programs used by the control unit 12 and items that are accumulation target information. The storage unit 11 in FIG. 1 describes the accumulation target information and is stored in a data structure including item node data 111, link node data 112, and arc data 113.

Here, a data model schematically showing the data structure of the accumulation target information in the storage unit 11 of the server device 1 will be described with reference to FIG. The data model of FIG. 2 is a kind of so-called labeled directed graph model.
This data model is composed of an item node M1, a link node M2, and an arc M3. The item node M <b> 1 is a node having an item that is information to be accumulated, and is stored as item node data 111 in the storage unit 11. The link node M2 is a node that relays and connects the item nodes M1 and is stored as the link node data 112 of the storage unit 11. The arc M3 is a directional branch that connects the item node M1 or the link node M2 with the direction information that is the upstream / downstream order of the item node M1 or the link node M2, and is stored in the arc data 113 of the storage unit 11. . In the following description, when simply referred to as a node, both the item node M1 and the link node M2 are collectively referred to.

Looking at the item node M1 in FIG. 2, it can be seen that there is no direct connection between the item nodes M1. That is, the generation of the arc M3 that directly connects the item nodes M1 is prohibited. In this case, when generating the arc M3, it is determined whether the item nodes M1 are directly connected to each other, and if they are directly connected, the generation is prohibited. In this way, the connection between the item nodes M1 is prohibited in order to prevent a complicated topology from being formed when the number of items to be accumulated becomes enormous. This is because if the topology becomes complicated, subsequent maintenance and item arrangement become difficult. In particular, when a plurality of storage methods such as a bulletin board type, a diary type, and an e-mail type are realized with a single data model, the complexity increases.
The arc M3 is given a label indicating the relationship between the node connected in the upstream direction and the node connected in the downstream direction. By referring to such a label, the relationship between the upstream node and the downstream node can be easily grasped. Also, in this information storage and sharing system, grouping using the label attached to the arc M3, various service types such as bulletin board type, diary type, and mail type, and detailed search conditions within each service Easy to set up.

  Next, with reference to FIG. 3, the data structure of the accumulation target information accumulated in the storage unit 11 realizing such a data model will be described.

  FIG. 3A shows item node data 111 which is the data structure of the item node M1. The item node data 111 is data that the item node M1 has individually, and is composed of a node identifier, an owner identifier, an upstream arc, a downstream arc, and an item.

  The node identifier is unique data for identifying the item node data 111, and is automatically given by the computer every time the item node M1 is newly generated. The owner identifier stores, for example, a user identifier that identifies the user who created the item node M1. Note that the owner identifier can also give ownership authority to a plurality of users, and as many user identifiers as the number of users having ownership authority are stored. The owner identifier may be automatically assigned by the computer every time the item node M1 is newly generated, or may be manually input each time.

  The upstream arc stores an arc identifier that identifies the arc M3 connected upstream. When a plurality of arcs M3 are connected, a plurality of arc identifiers are stored. The downstream arc stores an arc identifier that identifies the arc M3 connected downstream. When a plurality of arcs M3 are connected, a plurality of arc identifiers are stored. An item is information (content) itself that is desired to be stored and shared. For example, various items of data such as text and images such as e-mails, diaries, and bulletin boards are stored.

  FIG. 3B shows link node data 112 which is a data structure of the link node M2. The link node data 112 includes a node identifier, an owner identifier, an upstream arc, a downstream arc, and access control information.

  The node identifier is unique data that identifies the link node data 112. Each time this link node M2 is newly created, the computer automatically gives it. The owner identifier stores, for example, a user identifier that identifies the user who created the link node M2. The owner identifier can also give ownership authority to a plurality of users, and user identifiers for only the users having ownership authority are stored. The owner identifier may be automatically assigned by the computer every time the link node M2 is newly generated, or may be manually input each time.

  The upstream arc stores an arc identifier that identifies the arc M3 connected upstream. When a plurality of arcs M3 are connected, a plurality of arc identifiers are stored. The downstream arc stores an arc identifier that identifies the arc M3 connected downstream. When a plurality of arcs M3 are connected, a plurality of arc identifiers are stored.

  The access control information is information indicating the authority to update the contents of the link node M2, the downstream arc M3, and the item node M1 connected to the downstream arc. Here, the access control information includes the link node M2, the downstream arc M3, and the item node M1 connected to the downstream arc M3 as the authority range because the directed graph model organizes information from upstream to downstream. This is because the node located upstream dominates the arc M3 or node located downstream. In the information storage and sharing system, since the item nodes M1 are not directly connected to each other, the link node M2 is always relayed between the item nodes M1 and M1, so that the link node M2 has access control. This is because setting the information eliminates the need to set access control information for all item nodes M1 and arcs M3.

  The access control information includes management authority, reference authority, link node change authority, link node sharing authority, item node changing authority, and item node sharing authority. Each authority information stores a user identifier of a user who is permitted to execute the authority. When permission is granted to a plurality of users, a plurality of user identifiers are stored.

  The management authority is an authority given to a user who can perform all operations of addition / deletion / change / reference to the link node M2, the downstream arc M3, and the item node M1 connected to the downstream arc M3. In other words, a user who has been granted management authority stores a user identifier in all authority information of reference authority, link node modification authority, link node sharing authority, item node modification authority, and item node sharing authority described later. Is the same. In addition, a user who is given management authority can change each authority information of the access control information. In addition, you may give this management authority to the user who has the owner identifier of this link node data 112. FIG.

  The reference authority is an authority to give a user who can refer to the information of the item node M1 connected to the link node M2 via the downstream arc M3. That is, with reference authority, the information of the link node M2 and the downstream arc M3, the item node M1 connected via the downstream arc M3, and the information of the downstream arc M3 of the item node M1 can be referred to.

  The link node change authority is an authority given to a user who can add / change / delete the downstream arc M3. Note that the operation of adding / changing / deleting the downstream arc M3 specifically includes an operation of adding the downstream arc M3 accompanying the addition of a new node, and a new connection between existing nodes. Along with this, an operation to add the downstream arc M3, an operation to change the arc data 113 such as a label of the downstream arc M3, an operation to delete the downstream arc M3 when the existing node is deleted, and the connection relationship between the existing nodes For example, an operation for deleting the downstream arc M3. Further, the downstream arc M3 is an upstream arc for the downstream node (link node M2 or item node M1) connected by the downstream arc, and in order to add / delete the downstream arc M3, only this link node change authority is required. In addition, the link node sharing authority or the item node sharing authority of the access control information regarding the downstream node is also required at the same time.

  The link node sharing authority is an authority given to a user who can add / delete the upstream arc M3. The operation of adding / deleting the upstream arc M3 specifically includes an operation of adding the upstream arc M3 as a new node is added, and a connection of existing nodes to each other. For example, an operation for adding the upstream arc M3, an operation for deleting the upstream arc M3 when the node is deleted, and an operation for deleting the upstream arc M3 when the connection relation between the existing nodes is canceled. . Further, the upstream arc M3 is a downstream arc for the upstream node (link node M2 or item node M1) connected by the upstream arc, and in order to add / delete the upstream arc M3, only this link node sharing authority is used. In addition, the link node change authority or the item node change authority of the access control information regarding the upstream node is also required at the same time.

The item node change authority is an authority that grants a downstream arc M3 in the item node M1 connected via the downstream arc M3 to a user who can perform addition / deletion / change operations and item change operations. . The downstream arc M3 in the item node M1 is an upstream arc for the downstream node (link node M2) connected by the downstream arc. In order to add / delete the downstream arc M3, not only this item node change authority The link node sharing authority for the access control information related to the downstream node is also required at the same time.
The item node sharing authority is an authority given to a user who can add / delete the upstream arc M3 in the item node M1 connected via the downstream arc M3. The upstream arc M3 in the item node M1 is a downstream arc for the upstream node (link node M2) connected by the upstream arc. In order to add / delete the upstream arc M3, not only this item node sharing authority The link node change authority of the access control information regarding the upstream node is also required at the same time.

  Here, the range of access control based on the access control information of the link node M2 will be described with reference to FIG. The access control range of the link node M2 is effective downstream from the link node M2, and is applied to the arc before the next link node. In FIG. 4, the range is indicated by an enclosure M2-a from the link node M2 to the arc connected to the next link node (M2-2, M2-3) including the item node M1 downstream.

  FIG. 3C shows arc data 113 which is the data structure of the arc M3. The arc data 113 includes an arc identifier, an upstream node, a downstream node, and a label. The arc identifier is unique data that identifies the arc data 113. Each time the arc M3 is newly generated, the computer automatically gives it. The upstream node specifies a node connected to the upstream side of the arc M3, and stores one node identifier of the node connected to the upstream side. The downstream node specifies a node connected to the downstream side of the arc M3, and stores one node identifier of the node connected to the downstream side. The label of the arc M3 stores information expressing the meaning of the connection relationship between the upstream item node and the downstream link node to be connected. For example, character strings representing categories and titles such as e-mails, diaries and bulletin boards are stored.

  The control unit 12 includes a CPU / MCU, various memories, a processor, and the like. The control unit 12 includes a data input / output unit 121, a data reference unit 122, a data change unit 123, a node connection availability determination unit 124, and an authority determination unit 125. Have.

  The data input / output unit 121 receives a data operation request from the user terminal device 2 via the communication I / F unit 23, determines the type of the data operation request, and sends it to the data reference unit 122 and the data change unit 123 described later. The processing for the data operation request is executed, and the processing result is transmitted to the user terminal device 2 as the data operation result via the communication I / F unit 23.

  The data reference unit 122 is a unit that controls a series of processes until the user operates the user terminal device 2 and refers to a target item using a predetermined service. For example, when receiving a mail service, a process for referring to a mail content delivered to the user is executed. The data reference unit 122 starts the operation when the data operation request received by the data input / output unit 121 is an operation for referring to the stored information. A process for referring to the item node M1 that the user wants to refer to is sequentially performed. Details of the processing will be described later with reference to FIG.

  The data changing unit 123 starts operation when the data operation request received by the data input / output unit 121 is an addition, change, or deletion operation on the item node M1, the link node M2, and the arc M3. . The user sequentially performs processing for adding, changing, and deleting the item node M1 and the like. Details of the processing will be described later with reference to FIG.

  When the data change means 123 attempts to add or change the item node M1, the link node M2, or the arc M3, the node connection availability determination means 124 performs processing for determining whether the upstream node and the downstream node can be connected. Details of the processing will be described later with reference to FIGS.

  The authority determination unit 125 determines whether the user who has requested the authority to add, change, or delete the item node M1, the link node M2, and the arc M3. Details of the processing will be described later with reference to FIGS.

  The communication I / F unit 23 is an interface for performing communication with the user terminal device 2 and corresponds to a network to be connected.

  The user terminal device 2 is a so-called personal computer, and includes an input unit (not shown) such as a keyboard, a numeric keypad, and a mouse, and a display unit (not shown) such as a liquid crystal display (LCD). To the server device 1.

  The network 3 is connected to the server device 1 and the user terminal device 2 and is a network such as a wide area communication network such as the Internet or a closed area communication network. It may be a general telephone line network.

Next, a processing flow of the server device 1 when the user operates the user terminal device 2 and makes a data operation request to the server device 1 via the network 3 will be described with reference to FIG. Note that the processing flow described below is controlled by a program executed by the control unit 12.
When the server apparatus 1 receives the data operation request from the user terminal apparatus 2, the server apparatus 1 starts data operation processing (step S1). The data operation request includes a data reference request for referring to an item, a data change request that does not affect the connection relationship between the node and the arc M3 such as an item and a label, and a data change that affects the connection relationship between the node and the arc M3. There is a request. The data operation request includes at least information for specifying the item node M1 and the link node M2 to be referenced, changed, added, and the like. Using the information included in these data operation requests, the data input / output unit 121 determines the type of data operation request from the user terminal device 2 and the like.

  The data input / output means 121 first determines in step S2 whether the data operation request is a data reference request. If it is a data reference request (step S2-Yes), the data reference means 122 starts processing. First, the node identifier of the node to be referred to included in the data reference request is acquired. For example, when logging into the service for the first time, it is the node identifier of the item node M1 that will be the home for the user. In other cases, an appropriate node identifier is acquired.

  Next, referring to the storage unit 11, the item node data 111 or the link node data 112 of the node having the acquired node identifier is acquired (step S21). Then, with reference to the acquired item node data 111 or link node data 112, it is determined whether or not the user who has requested the data reference has a reference authority (step S22).

  Specifically, if it is a data reference request to the item node M1, it is confirmed whether the arc identifier is stored in the upstream arc in the item node data 111. If the upstream arc is not stored, it is determined that this item node M1 is the node positioned at the highest level, and it is determined that the item node M1 has a reference authority. However, you may make it determine with reference authority on the condition that an owner identifier corresponds with the user identifier contained in a data reference request.

  On the other hand, when the item node M1 is not the highest level, the arc identifier stored in the upstream arc in the item node data 111 is read, and the link node M2 connected via the arc having the arc identifier is specified. Then, the reference authority and the management authority of the access control information in the link node data 112 of the link node M2 are referred to. If the user identifier included in the data reference request is included, it is determined that the user has the reference authority. Otherwise, it is determined that there is no reference authority. In addition, when there are a plurality of arc identifiers in the upstream arc, the node identifier of the link node M2 relayed to refer to the item node M1 is also acquired from the data reference request, and the arc having the arc identifier stored in the upstream arc If an arc including the node identifier in the upstream node is included in the node, the authority of the link node M2 is followed.

  If it is a data reference request to the link node M2, it is confirmed whether the user identifier included in the data reference request is stored in the management authority or reference authority of the access control information in the link node data 112. If stored, it is determined that the link node M2 has the reference authority. On the other hand, if it is not stored, it is determined that this link node M2 has no reference authority.

If there is a reference authority (step S23-Yes), the data reference means 122, if it is the item node M1, uses the item in the item node data 111 as a data operation result as a data operation request via the communication I / F unit 13 and the network 3. It transmits to the user terminal device 2 which has performed (step S10). At this time, data generated by incorporating the arc identifier of the downstream arc or the arc identifier of the upstream arc together with the label of the arc M3 into the item in the item node data 111 may be used as the data operation result (step S24).
Similarly, in the case of the link node M2, the data generated including the arc identifier of either or both of the upstream arc and the downstream arc in the link node data 112 and the label of the arc M3 is used as the communication operation result as the data operation result. The F unit 13 transmits the data operation request to the user terminal device 2 that has made a request via the network 3 (step S10). In the present embodiment, the data reference means 122 generates the data operation result so that the user terminal device 2 can visually recognize the data. However, a dedicated browsing browser for the user terminal device 2 is prepared. , It may be visible in the browser.

  On the other hand, if it is determined in step S23 that there is no reference authority, the fact is transmitted as a data operation result to the user terminal device 2 that has made a data operation request via the communication I / F unit 13 and the network 3 ( Step S10).

  Returning to step S2, the data input / output means 121 determines that the data operation request is not a data reference request (step S2-No), and in step S3, the node or arc M3 is changed as in the change of the item or label itself. A case where it is determined that the request is a data change request that does not affect the connection relationship will be described (step S3-No). That is, when the data operation request from the user terminal device 2 does not simply refer to the item or the like, the user wants to change the item in the item node data 111 or the label in the arc data 113. In addition, it is a request for changing access control information in the link node data 112. This data change request includes the node identifier of the item node M1 to be changed, the node identifier of the link node M2, the arc identifier of the arc M3, and change data to be changed.

  If the data input / output unit 121 determines in step S3 that it is not a data change request accompanied by an arc connection change, the data change unit 123 starts processing. First, the data changing unit 123 refers to the storage unit 11 and acquires the item node data 111 or the link node data 112 having the node identifier of the node to be changed included in the data change request (step S11). Then, with reference to the acquired item node data 111 or link node data 112, the authority determining unit 125 determines whether or not the user who has requested the data change has a change authority (step S12).

Specifically, if it is a data change request (item change) to the item node M1, it is confirmed whether an arc identifier is stored in the upstream arc in the item node data 111. If the upstream arc is not stored, it is determined that this item node M1 is the topmost node, and it is determined that the item node M1 has a change authority. However, the item node may determine that the change authority is granted on condition that the owner identifier matches the user identifier included in the data change request.
On the other hand, if the arc identifier is stored in the upstream arc, the arc data 113 having the arc identifier stored in the upstream arc is referred to, and the node identifier stored in the upstream node in the arc data 113 is further extracted. . The user identifier stored in the item node change authority or the management authority of the access control information in the link node data 112 having the extracted node identifier includes the user identifier of the user who made this data change request. Make sure. In this information storage and sharing system, the item node M1 is not directly connected to each other, but the link node M2 is connected to the item node M1 via the arc M3. Become node M2. Further, it may be determined that there is a change authority on the condition that the owner identifier matches the user identifier included in the data change request. Further, when there are a plurality of arc identifiers in the upstream arc, the node identifier of the link node M2 relayed to change the item node M1 is also obtained from the data change request, and the arc having the arc identifier stored in the upstream arc If the data 113 is referred to and an arc including the node identifier of the link node M2 is included in the upstream node in the arc data 113, the authority of the link node M2 is followed.

  If it is a data change request to the link node M2 (change of access control information), it is confirmed whether the user identifier included in the data change request is stored in the access control information management authority in the link node data 112. If stored, it is determined that there is an authority to change the access control information in this link node M2. On the other hand, if it is not stored, it is determined that there is no change authority in the access control information of this link node M2.

  If it is a data change request (label change) to the arc M3, the arc data 113 having the arc identifier of the arc M3 to be changed included in the data change request is referred to and stored in the upstream node in the arc data 113. Extract the node identifier. Then, link node data 112 or item node data 111 having such a node identifier is extracted. When the link node data 112 is extracted, it is confirmed whether the user identifier of the user who has made this data change request is included in the link node change authority or the management authority of the access control information in the link node data 112. If the user identifier of the user who made this data change request is included, it is determined that the user has authority to change the label in the arc data 113 of the arc M3. Further, when the item node data 111 is extracted, it is further confirmed whether there is a change authority as in the case of the data change request to the item node M1, and if the arc identifier is stored in the upstream arc, it exists upstream. The link node data 112 of the node to be extracted is extracted. It is confirmed whether the user identifier of the user who made this data change request is included in the item node change authority or the management authority of the access control information in the link node data 112. If the user identifier of the user who made this data change request is included, it is determined that the user has authority to change the label in the arc data 113 of the arc M3.

  If there is a change authority (step S13-Yes), the data changing means 123 rewrites the corresponding label, item, or access control information with the change data included in the data change request in step S14 (step S14). . On the other hand, if there is no change authority, it progresses to step S10 as it is. In step S10, the result of whether or not the change is completed is transmitted as a data operation result to the user terminal device 2 that has requested the data operation via the communication I / F unit 13 and the network 3 (step S10).

  Returning to step S3, if the data operation request from the user terminal device 2 is not simply a data reference request for referring to shared information or a data change request not accompanied by a change in arc connection, that is, the connection change of the arc M3 is changed. A case where the data change is accompanied (step S3-Yes) will be described. In the data change accompanied by the connection change of the arc M3, when adding the arc M3 with adding a new node, when adding the arc M3 with newly connecting the existing nodes, existing data In some cases, the arc M3 is deleted along with the deletion of the other node, and the arc M3 is deleted along with the cancellation of the connection relationship between the existing nodes.

  The data change request includes the item node M1, link node M2, arc M3 to be added / deleted or changed, and various data necessary for the change. Specifically, an item node M1 which becomes an upstream node or a downstream node of the arc M3 to be added / deleted, a node identifier of the link node M2 or an arc identifier of the arc M3, data necessary for adding a new node, etc. included.

  The data change process (step S4) accompanied by the connection change of the arc M3 will be described with reference to FIG. First, a case where a new node is added will be described. That is, if the data input / output unit 121 determines that the data change request from the user is the addition of the arc M3 with the addition of a new node (Yes in step S40), the data change unit 123 has received it. Temporary node data is generated based on the data included in the data change request (step S41). Specifically, if the item node M1 is added, the owner identifier necessary for the item node data 111, the item, and the node identifier of the node that is the connection destination are acquired, and temporary item node data 111 is generated. When generated, a node identifier as the item node M1 is automatically given.

  If the link node M2 is added, the owner identifier, access control information, and the node identifier of the node that is the connection destination necessary for the link node data 112 are acquired, and temporary link node data 112 is generated. When generated, a node identifier as the link node M2 is automatically given.

  Step S42 is a process of the node connection availability determination unit 124 for prohibiting the item nodes M1 from being directly connected to each other. That is, when the provisional item node data 111 is added, it is determined whether the connection destination node is the item node M1 or the link node M2, and if the connection destination node is the item node M1, the connection is prohibited (step S43). -Impossible), otherwise, it is determined that connection is possible (step S43-possible). Specifically, it is determined whether or not the item nodes M1 are directly connected depending on whether or not the node identifier of the received node as the connection destination is given to the item node M1. In this embodiment, it is possible to determine whether the node identifier itself is the item node M1 or the link node M2. However, the present invention is not limited to this. In addition, the item node data 111 or the link node data 112 may be identified.

  If it is determined in step S43 that the item nodes M1 are directly connected to each other (step S43—impossible), the process proceeds to step S10, and a message indicating that a data change request for adding this node cannot be made is transmitted to the user terminal device 2 as a data operation result. To do.

On the other hand, if it is determined in step S43 that the item nodes M1 are not directly connected to each other (step S43—possible), the process proceeds to step S44, where the authority determining unit 125 determines whether the user who has requested the data change has the change authority Determine whether or not.
Specifically, the link node change authority, the link node sharing authority, the item node changing authority, the item node sharing authority, the management authority, or the connection destination of the access control information in the link node data 112 having the access control information related to the connection destination node It is confirmed whether the owner identifier of the node of this node includes the user identifier of the user who made this data change request. If the connection destination is the item node M1, it follows the authority of the link node data 112 of the link node M2 of its own upstream arc. If the user is not the owner of the connection destination node and does not have management authority, if the temporary node data is a downstream node and the connection destination node is an upstream node, the link node change authority or item node of the connection destination node When the change authority is necessary, and the temporary node data is the upstream node and the connection destination node is the downstream node, the link node sharing authority or the item node sharing authority is required. In order to avoid a malicious node creating a new node and making a malicious change to the downstream node using the authority of this new node, adding a new node whose temporary node data is an upstream node is Only the user whose user identifier is included in the management authority instead of the link node sharing authority or item node sharing authority of the connection destination node may be permitted.

If the user has change authority (step S45—Yes), the data changing unit 123 newly generates the arc data 113. That is, the arc identifier is automatically generated, and the node identifier of the upstream node, the node identifier of the downstream node, and the label are stored according to the data change request (step S46).
In step S47, the arc identifier of the arc data 113 generated in step S46 is added to the temporary node data, and stored in the upstream arc or downstream arc as the formal item node data 111 or link node data 112, and the process proceeds to step S10.

  On the other hand, if the user does not have the change authority (No at Step S45), the process proceeds to Step S10, and transmits to the user terminal device 2 as a data operation result that the node cannot make a data change request for addition.

  Next, processing for adding or deleting or changing an existing node or existing arc, which is not node addition in step S40, will be described. The data changing unit 123 refers to the storage unit 11 and acquires node data having the node identifier of the node to be changed included in the data change request (step S48). Then, with reference to the acquired item node data 111 or link node data 112, the authority determining unit 125 determines whether or not the user who has requested the data change has a change authority (step S49).

  Specifically, if it is a data change request including the item node M1, it is confirmed whether the arc identifier is stored in the upstream arc in the item node data 111. If the upstream arc is not stored, it is determined that the item node M1 is a node located at the highest level, and it is determined that the change authority is present. However, the item node may determine that the change authority is granted on condition that the owner identifier matches the user identifier included in the data change request. On the other hand, if the upstream arc is stored, the arc data 113 having the arc identifier stored in the upstream arc is referred to, and the node identifier stored in the upstream node in the arc data 113 is further extracted. Then, the link node data 112 that is the link node M2 having the extracted node identifier is extracted. Then, with reference to the access control information in the link node data 112, the item node change authority (when the upstream node includes the item node M1 and the downstream arc of the item node M1 is changed) or the item node sharing authority (downstream) If the node side includes the item node M1 and the upstream arc of the item node M1 is changed) or the user identifier stored in the management authority includes the user identifier of the user who made this data change request If it is included, it is determined that the user has change authority. On the other hand, if not included, it is determined that there is no change authority.

  If the data change request includes the link node M2, the management authority or the link node change authority in the link node data 112 (when the link node M2 is included on the upstream node side and the downstream arc of the link node M2 is changed) Alternatively, it is confirmed whether the user identifier included in the data change request is included in the link node sharing authority (when the link node M2 is included on the downstream node side and the upstream arc of the link node M2 is changed). If it is included, it is determined that there is an authority to change the upstream arc or the downstream arc of this link node M2. On the other hand, if it is not included, it is determined that this link node M2 has no change authority.

  If it is a deletion request to the arc M3, the node identifier stored in the upstream node in the arc data 113 having the arc identifier of the arc M3 to be changed included in the data change request is extracted. Then, the link node data 112 having access control information related to the node having the extracted node identifier is extracted, and the user identifier stored in the link node change authority, the item node change authority or the management authority in the link node data 112 is extracted. If the user identifier included in the data change request is included, it is determined that the user has the authority to delete the arc data 113. Further, the node identifier of the downstream node in the arc data 113 having the arc identifier of the arc M3 is extracted, the link node data 112 having the access control information regarding the downstream node is extracted, the link node sharing authority in the link node data 112, the item If the user identifier stored in the node sharing authority or the management authority includes the user identifier included in the data change request, it may be determined that the user has the authority to delete the arc data 113.

  If there is a change authority (step S50-Yes), the data changing unit 123 proceeds to step S52. On the other hand, if there is no change authority (step S50-No), it progresses to step S10 as it is. In step S10, the result indicating whether or not the change has been completed is transmitted as a data operation result to the user terminal device 2 that has requested the data operation via the communication I / F unit 13 and the network 3. In this case, the fact that a data change request cannot be made is transmitted to the user terminal device 2 as a data operation result.

  In step S51, based on the data change request, it is determined whether or not the change target is to change the node connection relationship. If the node connection relation is to be changed, the process proceeds to step S52. If the node connection relation is not to be changed, the process proceeds to step S56.

  Step S52 is a process of the node connection availability determination unit 124 for prohibiting the item nodes M1 from being directly connected to each other. That is, first, node data for changing the connection relationship acquired in step S48 and establishing a new connection is read. Then, it is determined whether the read node is the item node data 111 or not. If the item node data 111 is mutually connected, the connection is prohibited (step S53—impossible), and otherwise, it is determined that the connection is possible (step S53—possible). Specifically, it is determined whether or not the item nodes M1 are directly connected depending on whether or not the node identifier of the received node as the connection destination is given to the item node M1. In this embodiment, the node identifier itself can be determined as the item node M1 or the link node M2. However, the present invention is not limited to this, and in the node data having the node identifier that is the connection destination, Data that can identify the item node data 111 and the link node data 112 may be provided.

  If it is determined in step S53 that the item nodes M1 are directly connected to each other, the process proceeds to step S10, and a message indicating that a data change request for adding this node cannot be made is transmitted to the user terminal device 2 as a data operation result.

  Next, in step S54, in accordance with the data change request, the existing arc data 113 is deleted and the new arc data 113 is added. That is, when the arc data 113 is newly generated, the data changing unit 123 automatically generates an arc identifier and stores the node identifier of the upstream node, the node identifier of the downstream node, and the label according to the data change request. In step S55, the arc identifier is deleted or added from the upstream arc or the downstream arc in the related item node data 111 or link node data 112, and the process proceeds to step S10.

  If it is determined in step S51 that the change target is not to change the node connection relationship, the process proceeds to step S56 to determine whether the data change request is a node deletion request. If it is a node deletion request, the arc data 113 that is no longer necessary when the node is deleted is deleted (step S57), the node to be deleted is deleted, and the node affected by the deletion is changed (step S57). S58), the process proceeds to step S10.

  If it is determined in step S56 that the node is not deleted, that is, the arc M3 is deleted, the arc data 113 is deleted according to the data change request (step S59), and the node data affected by the deletion of the arc data 113 is determined. The arc identifier is deleted from the upstream arc or downstream arc at (step S60), and the process proceeds to step S10.

  Next, with reference to FIG. 7 to FIG. 18, a specific embodiment in a system that can use a mail / diary / bulletin board service will be described. A system builder who is requested to build a system that can use mail, diary, and bulletin board services uses this information storage and sharing system to create a system framework. Specifically, the data structure for storing the data of the service to be provided, the diary or the bulletin board in the item of the item node data 111 of the item node M1 is determined, and the user terminal device 2 is determined according to the data structure. Create various operation screens, including a reference screen for displaying items on the screen, an input screen for adding or changing the contents of emails, diaries, and bulletin boards for services provided, a login screen, and a screen displayed after login. Further, the screen is associated with the process to determine which data operation request should be transmitted to the server device 1 from various operation screens.

Next, a system administrator who operates the constructed system and newly registers a user prepares an item node M1 having a screen that becomes a home for the user every time the user is registered. FIG. 7 shows a system in which a system builder can use a mail / diary / bulletin board service, and the system administrator registers user A / user B / user C... It is a figure explaining the state from which only mail can be used, but a mail item does not exist yet. FIG. 8 shows an example of the item node data 111, the link node data 112, and the arc data 113 in FIG. FIG. 9 is an example of a screen on which each node is displayed on the user terminal device 2 corresponding to FIG. In the following description, In is the node identifier of the item node M1, Ln is the node identifier of the link node M2, and An is the arc identifier of the arc M3.
The starting point of this system is the item node of I1. The user accesses this I1 from the user terminal device 2. This I1 is linked with the login screen, and the user shared home image that is the item of I1 is displayed (see FIG. 9A). Note that the owner identifier of I1 is SuperUser, which is the user identifier of the system administrator. There is no upstream arc because it is a starting point (hereinafter, $ in the item node data 111, the link node data 112, and the arc data 113 indicates that nothing is stored).

  Now, when the user presses the login button, the user authentication is performed, and the result of the user authentication is distributed to each user via the L1 connected at the A1 of the downstream arc of I1, and used. Home for the user is displayed. FIG. 9B is an example in which the screen immediately after login of the user A (user identifier U0001), that is, I2 is displayed. Similarly, FIG. 9C shows I3 of the user B (user identifier U0002). FIG. 9D is a screen displaying I4 of user C (user identifier U0003). Note that user information such as a user ID and password used for user authentication may be stored in the item I1 together with the user shared home image. Further, when passing through L1, a screen including a list of arc labels may be displayed, and the user may select “user A”, “user B”, “user C”,. . Referring to the item node data in FIG. 8, each user identifier is stored as an owner identifier in I2, I3, and I4 that are homes for the user. The upstream arcs of I2, I3, and I4 store arc identifiers A2, A3, and A4 of arcs having L1 as an upstream node, respectively. In the downstream arc, link nodes L2, L3, and L4 respectively connected by arcs A5, A6, and A7 whose labels are “mail” are prepared so that mail can be used. Next, referring to the link node data, the user identifier of each user, which is the same as the owner identifier, is stored in the management authority, reference authority, and item node sharing authority of the access control information of L2, L3, and L4. The node change authority stores not all individual user identifiers but the same “all” as the user identifiers of all users of the system are specified. If it demonstrates using L2, since L2 can refer only to the user A, the item node (in this case mail item) connected to L2 can refer only to the user A. However, since everyone can add item nodes to L2, any user can send an email to user A.

Here, an example in which mail is transmitted from the user B to the user A will be described with reference to FIGS. FIG. 10 shows changes in the connection state of nodes and arcs added by mail transmission / reception from FIG. 7, and FIG. 11 shows changes in stored data from FIG. FIG. 12 is an example of a screen on which each node is displayed on the user terminal device 2 corresponding to FIG. As operation screens related to mail, an operation screen for “new mail” for creating / sending mail, a screen for referring to sent / received mail, and the like are prepared in advance in association with data operation requests.
For example, the user B clicks “new mail” on the display screen of I3 in FIG. 9C or the display screen of L3 displayed from the “mail” label of I3, and “new” prepared by the system builder in advance. When an email composed of an address, a subject, a body text, and the like is created from the operation screen of “Mail” and a new mail item I10 is created, an arc A10 from L3 to I10 is created. This is a data operation request for creating and adding I10 as a new node by designating L3 as an upstream node, that is, an operation for adding a new node of a data change request. Since user B has management authority and link node change authority for L3, new nodes I10 and A10 are created. The state in which only the arc of A10 is created is a state in which a mail item is saved only because the user B who is the sender has a mail item. Here, when user B actually performs "transmission" to user A, an arc A11 from L2 to I10 is created. This is a data operation request for newly connecting existing nodes in which L2 which is a link node referred to by the user “A” as a destination is designated as an upstream node and I10 is designated as a downstream node, that is, This is an arc addition operation for a data change request. This series of operations is associated with the “new mail” operation screen. Since user B has the authority to change the link node with respect to L2 and has the authority to manage and item node sharing authority with respect to I10 by referring to the access control information of L3 via A10 of the upstream arc, from L2 to I10 Can be created, A11 can be added to the upstream arc of I10, and A11 can be added to the downstream arc of L2.

  Now, instead of referring to the incoming mail and outgoing mail from the same link node (for example, from L2 or L3), if you want to be able to sort by mail type, the system builder prepares a sorting operation screen, It is better to create a new link node downstream by the user and distribute it. For example, when the user B on the transmission side newly creates L5 of the link node connected by the arc A12 having the label of the outgoing mail, and makes a data operation request for creating A13 of the arc connected to I10 from the downstream node of L5. After sending the mail, I10 is distributed to the sent mail. Further, when the user A on the receiving side newly creates L6 of the link node connected by the arc A14 having the label of the received mail, and makes a data operation request for creating A15 of the arc connected to I10 from the downstream node of L6. After receiving the mail, I10 is assigned to the received mail. Also, if the link nodes of L5 and L6 are prepared in advance before user B creates I10, the operation of creating an arc in the order of A10 and A11 and sending / receiving mail is performed in the order of A13 and A15. It can be replaced with an operation of creating an arc and automatically sending and receiving mail by sending it to sent mail and received mail. In addition, only the user identifier U0002 of the user B is stored in the link node change authority of the access control information of L5, and the management authority, the reference authority, and the item node sharing authority are only the user identifier U0002 of the user B. Therefore, although it is possible to refer to L5 and to add a node downstream of L5, only user B can see the other user's outgoing mail or distribute the mail to user B's outgoing mail. Can not.

  FIG. 12 is an example of a screen in which a mail is sent from user B to user A and sorting is performed. FIG. 12A is an example of a screen on which user A displays L2, and the received mail of A14 The label is displayed. FIG. 12B is an example of a screen on which the user B displays L3, and the label of the outgoing mail A12 is displayed. Clicking on a mail item in the figure displays the I10 item on the mail reference screen as a received mail for user A and as a sent mail for user B, and reads the contents of each mail. Can do.

Next, with reference to FIGS. 13 to 15, an example will be described in which the user A is set to be able to use the diary, and the user B and the user C subscribe to the diary created by the user A. FIG. 13 shows changes in the connection state of nodes and arcs added in the diary from FIGS. 7 and 10, and FIG. 14 shows changes in the stored data from FIGS. FIG. 15 is an example of a screen on which each node is displayed on the user terminal device 2 corresponding to FIG.
In order for user A to write a diary, click "new diary" from I2 of user A's home, create L20 (A20) so that the diary can be used from the "new diary" operation screen, Create a new diary article on I20 (A21) with "New Item". That is, the data operation request of the data addition request for adding the new node twice, that is, I2 to L20 and L20 to I20, is executed, and arcs A20 and A21 are added respectively.
The other user refers to the link list of the diary published from the “new diary” of his / her home and designates the L20 of the user A of the existing node as the downstream node, so that the user B is changed from I3 to A22. User C can make A23 from I4. That is, a data operation request for a data change request for connection between existing nodes is executed. At this time, the user B assigns “A's diary” to the A22 label, and the user C assigns “subscription diary” to the A23 label. As described above, even if the arc is directed to the same L20, the user can freely add the meaning to the next reference destination by labeling the arc instead of the link node.
Here, referring to the access control information of L20 in FIG. 14, the reference authority is everyone, the link node change authority is user A, the link node sharing authority is everyone, and user A publishes the diary for other uses. Addition of an arc from the user's node to L20 is permitted. In addition, since there is a reference authority, the user B and the user C can refer to the I20 connected by the A21 of the downstream arc of the L20. However, since the link node change authority of L20 is only user A, only the user A can execute new diary posting. Then, the new diary posting is an operation for adding a new node in which L20 is designated as the upstream node. When it is desired to correct the posted diary connected by the downstream arc of L20, only the user A can execute from the correction screen associated with the data change request not accompanied by the arc connection specifying the item node.

  FIG. 15 is an example of a screen example in which the user B and the user C can refer to the diary created by the user A. FIG. 15A shows an example of screen transition of user A. Clicking on “Diary” labeled A20 from the display screen of user A ’s I2 label displays L20. When the item “article 1” connected at A21 is selected, the display screen of I20 is displayed. Can read the diary created by user A. FIG. 15B shows an example of a screen in which L20 is displayed from I3 where user B is home, and FIG. 15C is L4 from user I4 where user C is home. Even for the same link node of L20, the display content of the screen changes depending on which node has referred to. Further, since the user B and the user C have only reference authority to the L20, the operation screen for the user A to create a new diary “new item” on the screen displaying the L20. There is no button for selecting.

Next, with reference to FIGS. 16 to 17, an example will be described in which a user A is set to use a bulletin board, and a bulletin board prepared by the user A is used by a user B or a user C to make a comment. . 16 shows changes in the connection state of nodes and arcs added on the bulletin board from FIGS. 7, 10 and 13, and FIG. 17 shows changes in the stored data from FIGS. 8, 11 and 14. It is. FIG. 18 is an example of a screen on which each node is displayed on the user terminal device 2 corresponding to FIG.
User A clicks “new bulletin board” from I2 of user A's home to open a bulletin board, and creates a bulletin board from the operation screen of “new bulletin board” (L30, A30). Then, “new item” is clicked, and the topic (topic 1) is provided from the operation screen of “new item” (I30, A31). In addition, a comment on the topic 1 is received (L31, A32). That is, the data operation request of the data addition request for adding the new node three times, that is, I2 to L30 and L30 to I30, is executed, and arcs A30, A31, and A32 are added, respectively.
User B clicks “new bulletin board” of I3, which is his home node, so that the publicly prepared bulletin board prepared by user A can be read from the operation screen of “new bulletin board”. That is, A33 of the label “Mr. A's bulletin board” is generated from I3 to L30 by a data operation request of a data change request for adding a new connection relationship between existing nodes. Similarly, the label “favorite bulletin board” A34 is generated from I4 to L30 so that the user C can read the bulletin board prepared by the user A.
Here, referring to the access control information of L30 in FIG. 17, the management authority is user A, the reference authority / link node change authority / link node sharing authority is all, the item node sharing authority is user A, and the user A publishes the bulletin board, and permits the addition of an arc from another user's node to L30 and the creation of a new node (providing a topic here). Moreover, since there is a reference authority, other users can also refer to the topic 1 of I30 connected by A31 of the downstream arc of L30. Further, referring to the access control information of L31, the management authority is user A, the reference authority / link node change authority is all, the link node sharing authority / item node sharing authority is user A, and user A is topic 1. Can be prepared to accept comments (generate A32), and other users are allowed to create new nodes (in this case, posting comments). Moreover, since there is a reference authority, other users can also refer to the comments connected by the L31 downstream arc.
User B posts comment 1 on topic 1 (L31 to I31, A35). User C also posts comment 2 on topic 1 (L31 to I32, A36). As described above, the user B and the user C can newly provide a topic, post a comment, or change an article or comment posted by the user B or C. These are realized by executing a data operation request for an additional data change request for a new node to L30 or L31, and a data operation request for a data change request for changing an item that has been created by itself. Is done. Since user A has management authority in L30 and L31, he can change all posts as an administrator.

FIG. 18 is an example of a screen example in which the user B and the user C use the bulletin board opened by the user A. FIG. 18A shows an example of screen transition of user A. When the “posted version” of the label of A30 is clicked from the display screen of the user A's I2 home screen, the L30 screen is displayed. Here, when the “topic 1” item connected in the A31 is selected, the I30 is displayed. "Topic 1" which is the topic provided by the user A can be read on the display screen. Further, when the “comment” connected in A32 is selected, the screen of L31 is displayed and a list of posted comments can be viewed. FIG. 18B is an example of screen transition of user B. When the “posted version” of the A33 label is clicked from the display screen of the user B's I3, the L30 screen is displayed. Here, when the “topic 1” item connected in the A31 is selected, the I30 is displayed. "Topic 1" which is the topic provided by the user A can be read on the display screen. Here, when "new comment" is clicked and comment 1 is posted on topic 1 (L31 to I31, A35), the content of comment 1 posted by user B on the generated I31 display screen is read. Can do.

DESCRIPTION OF SYMBOLS 1 ... Server apparatus 11 ... Memory | storage part 111 ... Item node data 112 ... Link node data 113 ... Arc data 12 ... Control part 121 ... Data input / output means 122 ... Data reference means 123 ... Data change means 124 ... Node connection availability determination means 125 ... Authority determination means 13 ... Communication interface (I / F) unit 2 ... User terminal device 3 ... network

Claims (3)

An item node consisting of identifiers of either or both of the upstream arc and downstream arc and item information to be stored, a link node consisting of identifiers of either or both of the upstream arc and downstream arc, and the items upstream and downstream A storage unit storing a data structure composed of nodes or arcs composed of identifiers of the link nodes;
An information storage device using a graph model having a control unit for storing information using the data structure of the storage unit,
The controller is
Input / output means for accepting a data operation request to the item node or the link node and identifying whether the data change request is accompanied by generation of the arc;
If it is a data change request accompanied by the generation of the arc, node connection availability determination means for determining whether both the upstream side and the downstream side of the arc after the change are item nodes;
Changing means for prohibiting the data change if both the upstream side and the downstream side are item nodes, and executing the data change if either or both of the upstream side and the downstream side are not item nodes;
An information storage device characterized by comprising:
The arc in the data structure further includes label information indicating an attribute of the arc,
When the control unit receives a reference request from the input / output unit to the item node or the link node, the control unit outputs result information including label information of an arc connected to the item node or the link node. The information storage device according to claim 1, further comprising:
The link node further includes access control information to the link node and an item node connected by a downstream arc of the link node,
The controller is
Furthermore, it has authority determining means for determining operation authority to the link node and the item node using the access control information,
When a data operation request to the item node or the link node is received from the input / output means, a data operation process is executed according to the determination of the operation authority for the access control information of the item node or the link node. The information storage device according to claim 1 or 2.