KR20070010965A - Apparatus and its method for processing webdav user-defined properties - Google Patents

Abstract

A device and a method for processing webDAV(Distributed Authoring and Versioning) user-defined property are provided to present a protocol for describing an XML(eXtensible Markup Language) type environment setting property and a corresponding processing procedure, and enable a webDAV server to manage the user-defined property. An open repository generator(210) generates an open repository by webDAV mapping according to a client request. An upper collection setting part(220) receives/sets up environment setting information of a client to an upper collection of the open repository. A resource register(230) registers resources to the generated open repository according to a resource registration request of the client. A property setting part(240) sets up the property of the registered resources by using the environment setting information set to the upper collection of the open repository. The collection setting part receives the environment setting information defined in an XML type from the client and sets the received environment setting information to the upper collection.

Description

Apparatus and its method for processing WebDAV user-defined properties}

1 is a configuration diagram of an embodiment of a collaboration support system to which the present invention is applied;

2 is an explanatory diagram for a document registration procedure in a webdev user-defined attribute processing apparatus according to an embodiment of the present invention;

3 is a diagram illustrating an embodiment of a public workplace data model expressed as a collection structure of a Web Dev server;

4 is a diagram illustrating an embodiment of a process of mapping a public workplace data model to a Web Dev server;

5 is a diagram illustrating an embodiment of a process of defining a "Configuration" attribute for a public workplace;

6 is a configuration diagram of a web dev user-defined attribute processing apparatus according to an embodiment of the present invention;

7 is a flowchart illustrating a webdev user-defined attribute processing method according to an embodiment of the present invention.

<Description of Symbols for Major Parts of Drawings>

11: Client 12: Web Dev Server

200: Web Dev custom property processing unit

210: public workplace generation unit 220: parent collection setting unit

230: resource register 240: attribute setting unit

The present invention relates to a webdev user-defined attribute processing apparatus and method, and more particularly, to a webdev user-defined attribute processing apparatus and method for effectively setting and managing the user-defined attributes on the Webdev server side. .

Web services allow users to search for and receive the desired information through a simple and convenient user interface. By using the advantages of the Web, information can be shared among group members that are widely distributed geographically, and group members can interact. To this end, more effective web-based collaborative support systems such as "iPlace" and "BSCW" have been developed.

WebDAV is a standard protocol for building such a web-based collaboration system. Web Dev is an extension of the existing Hypertext Transfer Protocol (HTTP) and provides a standard infrastructure for supporting asynchronous collaborative production of various contents over the Internet.

Various web-based application systems (eg, collaboration support systems, document management systems, groupware, internet portals, communities, Internet repositories, etc.) are being developed to support Web Dev technology.

The main functions of Web Dev are Lock Management, Property Management, Namespace management, and so on.

(1) lock management

Web Dev provides a function that prevents more than one worker from working on a document at the same time. This prevents the loss of an update, in which one author forgets the changes because the other author saves his / her changes on the server without reflecting them in his / her modifications. Web Dev provides exclusive write locks that allow only lock owners to update locked resources, and shared write locks that allow collaboration groups of collaborators on resources. In general, Webdev locks are independent of TCP connections, so you can update your modifications by reconnecting after you have finished working with the lock token disconnected from the network.

(2) property management

Web Dev Property Management refers to managing to create / delete / search information (author, last modified date, etc.) about web resources. Web Dev properties are made up of name / value pairs. Here, the attribute name is a URL, and the attribute value is a well-defined XML (eXtensible Markup Language) document, so it can store a wide range of XML data.

For example, if the title of the document stored in the Web Dev server is "WebDAV Property", it can be expressed as the following triple.

(http://www.webdav.or.kr/props/, title, WebDAV Property)

This is expressed in XML as follows.

<ns: title xmlns: ns = "http://www.webdav.or.kr/props/"> WebDAV Property </ ns: title>

On the other hand, Web Dev properties are largely divided into system-defined properties and user-defined properties. In the Web Dev specification, these attributes are divided into live attributes and dead attributes.

First, user-defined attributes are maintained by the client in grammar, semantics, and consistency, and the server rarely performs data processing. These attributes are set and updated by the client application. For example, in a collaborative workplace of a collaborative support system, a description or annotation of all documents registered in the collaborative workspace becomes a user-defined attribute. If these attributes have a specific format in the application system, the client application must ensure that the specified format is consistent.

In contrast, system-defined attributes allow the server to provide a value for the attribute. An example of a system-defined attribute is Webdev's "getcontentlength" attribute. The value of the "getcontentlength" attribute is a calculation of the length of the resource.

While Web Dev Server does all the work of setting and retrieving system-defined attributes, it does nothing except checking whether it conforms to the XML format. An important role of system-defined attributes is that they contain the necessary information for protocol computation. For example, the lock information of a resource may be supported by each Web Dev server. Therefore, the Webdev client always checks what kind of lock is currently applied (or supported) from the system-defined attributes provided by the server.

Web Dev also provides two methods, "PROPFIND" and "PROPPATCH", for handling attributes.

First, the "PROPFIND" method provides three functions for retrieving attributes defined in the resource: all attribute lookups, attribute lookups with specific names, and attribute name lookups. Among them, all attribute lookups are useful for explorer clients who don't know information about attributes set in the server. In addition, attribute lookups with specific names are useful for applications that use certain user-defined attributes. Finally, attribute name lookup is used to find out what name attribute is defined for a resource.

The "PROPPATCH" method then handles the request to set and remove attributes from the resource. Here, the entire set of requests submitted in connection with one "PROPPATCH" run is performed in order, like a transaction. If a set or remove fails, all attributes affected by the operation are returned to the state at the beginning of the "PROPPATCH" run.

Both the "PROPFIND" and "PROPPATCH" methods can affect a single resource (depth 0), the collection and its children (depth 1), and the collection's child hierarchy ('depth infinity').

(3) namespace management

Namespace management refers to the ability to copy and move Web documents within the server's namespace, to create and display the contents of a collection, the storage space for resources. HTTP only handles direct access to individual resources, but Web Dev provides a means to organize data more efficiently. In other words, resource management through Web Dev includes the collection itself, and the functions of creating, moving, copying, and deleting resources or files in the collection.

For example, if you want to develop a Web Dev-based collaboration support system, you can transform the collaboration model's object model from the collaboration system into the Web Dev namespace structure, and provide key information about the rights and functions of the workplace. Adding process is required.

However, as described above, the management (addition, update, and deletion of user-defined attributes) has all administrative responsibilities on the client side using the Web Dev server. In other words, the client must define the user-defined attribute to be applied for each resource in order to add a new resource to Web Dev, and set the user-defined attribute by using the "PROPPATCH" method. In addition, the client must check the type and setting status of the user-defined attribute set in the resource stored in the Webdev server using the "PROPFIND" method.

Let's look at the process of registering a document in a collaborative support system. For example, when implementing a public workplace of the "iPlace" system as a Web Dev server repository, various properties such as the name of the organization, the author, and the access authority of the public workplace must be set together. Therefore, the user must register (PUT) the document with the workplace server and set properties for the document (PROPPATCH). If the property fails, the registration of the document itself must be canceled.

As such, from the client's point of view, this is a single process of registering the content and attributes of one resource with the Web Dev server, but the process of actually registering it with the Web Dev server is only possible through the two-step request of the "PUT" and "PROPPATCH" methods It is possible. This irrationality is a problem that causes obstacles in utilizing user-defined attributes of Web Dev.

The present invention was devised to solve the above problems, and in the development of a Web Dev-based application system, an XML configuration environment attribute that can effectively set and manage a user-defined attribute managed by a client side, and its The purpose of this paper is to propose a protocol describing the procedure to perform processing, and to provide the management of user-defined attributes on the Web Dev server side.

Other objects and advantages of the invention will be described below and will be appreciated by the embodiments of the invention. Furthermore, the objects and advantages of the present invention can be realized by means and combinations indicated in the claims.

The present invention for achieving the above object, an apparatus for processing a user-defined attribute on the Web Dev server side, public repository generation means for generating a public repository by Web Dev mapping in response to a request from the client, the client Higher collection setting means for receiving environment setting information from the public storage and setting the higher collection of the public storage, and resource registration means for registering a resource in the public storage generated by the public storage generating means in response to a resource registration request from a client; And attribute setting means for setting an attribute of the registered resource by using environment setting information set in a higher collection of the public repository.

In addition, the present invention is a method for processing a user-defined attribute on the Web Dev server side, the Web repository server creating a public repository in response to a request from a client, the Web Dev server environment from the client A higher collection setting step of setting up a higher collection of the created open repository by receiving setting information, a resource registration step of registering a resource at the open repository according to a resource registration request from a client, and the web dev server The attribute setting step of setting a user-defined attribute by using the configuration information defined in the parent collection of the resource.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. Prior to this, terms or words used in the present specification and claims should not be construed as being limited to the common or dictionary meanings, and the inventors should properly explain the concept of terms in order to best explain their own invention. Based on the principle that can be defined, it should be interpreted as meaning and concept corresponding to the technical idea of the present invention.

Therefore, the embodiments described in the specification and the drawings shown in the drawings are only the most preferred embodiments of the present invention and do not represent all of the technical idea of the present invention, various modifications that can be replaced at the time of the present application It should be understood that there may be equivalents and variations.

1 is a configuration diagram of an embodiment of a collaboration support system to which the present invention is applied.

As shown in FIG. 1, the collaboration support system to which the present invention is applied includes a client 11 and a Web Dev server 12.

The client 11 creates an environment setting attribute for a user-defined attribute to be used in an application program in an XML format and sets it on the Web Dev server 12 to which the environment setting attribute created in the XML format is to be applied.

The Web Dev server 12 checks the configuration attribute defined by the client 11 and processes a method (PUT, MKCOL, COPY, MOVE, etc.) for adding or changing a resource. It handles adding and changing user-defined attributes and returns the result of the execution to the client 11. To this end, the web dev server 12 includes a web dev user-defined attribute processing apparatus 200.

In general, in the case of an application system using Web Dev, properties that should be basically set for all resources of the server are predefined. Therefore, the client application program can check the owner, contents, and access rights of the resource using the property value set in the resource.

As shown in FIG. 2, the webdev user-defined attribute processing apparatus 200 defines the information of the user-defined attribute in the parent collection of the webdev server 12 and the parent collection when the resource is registered by the client 11. Set the custom property by referring to the configuration property defined in. To this end, a protocol for defining user-defined attributes of the Web Dev server 12 is used.

The XML DTD definition model for the configuration attribute used in the present invention is as follows.

<! ELEMENT Configuration (Name, Description, Collection ?, Resource?)>

<! ELEMENT Name (#PCDATA)>

<! ELEMENT Description (#PCDATA)>

<! ELEMENT Collection (UserType +)>

<! ELEMENT Resource (UserType)>

<! ELEMENT UserType (Name, Depth ?, Property)>

<! ELEMENT Depth (Depth0 | Depth1)>

<! ELEMENT Depth0 EMPTY>

<! ELEMENT Depth1 EMPTY>

<! ELEMENT Property ANY>

The XML DTD definition model for the configuration attributes as described above has a structure that can specify user-defined attributes to be set for each configuration name and description, collection, and resource.

The "Configuration" element is a user-defined attribute that contains configuration information that applies to the parent collection of the Web Dev server.

The "Name" element defines the name of the parent element, and the "Description" element defines the purpose and description of the parent element. In addition, the "Collection" element defines a user-defined attribute to be set on the collection that is added or changed by request of methods that affect the collection, such as the "MKCOL" method.

In general, collections can create subcollections, so you need to refine the custom properties that need to be applied. Therefore, the user-defined attribute is set to the "UserType" element and the "Depth" element in the "UserType" element is used to determine the user-defined attribute to be applied to the child element. The "Depth" element has a "Depth0" element and a "Depth1" element of type "EMPTY".

If the "Depth0" element exists as a sub-element of the "Depth" element, it means that the user-defined attribute in the "UserType" element is applied to the collection immediately below the "Configuration" element. The "Depth1" element, on the other hand, applies to all collections of the child except the child collection. The option value of the "Depth" element can be further refined as needed, or extended to specify condition settings.

The "Resource" element may have a "UserType" element that defines a user-defined attribute to be set for a resource added by the "PUT" method. In this case, the "UserType" element in the "Resource" element does not need a "Depth" element because all resources are set equally.

The "Property" element defines a custom property to be added to all collections and resources. It is defined as "ANY" because each user can define each custom property.

Hereinafter, an application example of the "Configuration" attribute will be described with reference to FIG. 3.

3 is an explanatory diagram of a public workplace data model of an iPlace system expressed as a collection structure of a Web Dev server.

In the data model shown in FIG. 3, "workspacelist" has a list of currently created public workplaces, and "workspaceuserlist" has information of an administrator who has created a public workplace. And, "objectlist" has information about the resources that are actually stored, and "openws" has information about which public workplaces the data stored in "objectlist" are and information about the data. If the public workplace data model of the iPlace system is mapped to the collection, document, and attribute information of the Web Dev server 12, as shown in FIG.

If a new public place is created through Web Dev mapping of the public place, the user-defined property should be set along with the creation of the top level collection. And even if a folder or file below it is added, the user-defined attribute setting will be necessary. If defined as a "Configuration" attribute for a public workplace as shown in FIG.

Referring to FIG. 5, a process of defining a "Configuration" attribute for a public workplace is described first. The use of a user-defined attribute defined in the "Configuration" attribute is described through the "Name" and "Description" elements. At this time, the public workplace and the work folder created in the public workplace were set as a collection of Web Dev as shown in FIG. The data field of the data model for the public workplace is set as a user-defined attribute.

Here, the user-defined attribute to be set in the collection is a sub-element of the "UserType" element in the "Collection" element. The attribute to be defined in the public workplace and the attribute to be defined in the folder are expressed in XML structure. The user-defined attribute to be applied when a new public workplace is created is a "Property" element in the "UserType" element that has a "Depth0" element as a subelement value of the "Depth" element. In addition, the working folder collection created in the public workplace has a "Depth1" element. As such, each time a new collection is created, the Web Dev server analyzes the parent "Configuration" element and sets the property information in the appropriate "Property" element.

On the other hand, the document registered in the public workplace is set as a resource of the Web Dev as shown in FIG. At this time, the user-defined attribute to be set in the resource is defined as a child element of the "Property" element in the "Resource" element. As with the collection, the client reads the properties registered in the resource and makes use of the "UserType" element named "Document". The "UserType" element defines user-defined attributes such as the object type, document type, size, and owner of the document registered in the public workplace.

Hereinafter, a detailed configuration of the web dev user-defined attribute processing apparatus 200 will be described with reference to FIG. 6.

6 is a block diagram of a web dev user-defined attribute processing apparatus 200 according to an embodiment of the present invention.

As shown in FIG. 6, the webdev user-defined attribute processing apparatus 200 according to an embodiment of the present invention generates a public workplace for generating a public workplace by webdev mapping according to a request from the client 11. Part 210, the resource collection request from the parent collection setting unit 220, the client 11 to receive the configuration information defined in the XML format from the client 11 (PROPPATCH) to the parent collection of the public workplace The resource register unit using the resource collection unit 230 for registering a resource in the public workplace generated by the public workplace generator 210 according to the PUT, and the parent collection environment setting information set by the parent collection setting unit 220. An attribute setting unit 240 for setting an attribute of a resource registered at 230 is included.

The public workplace generation unit 210 generates the public workplace by mapping the data model of the public workplace to the collection structure of the Web Dev server. When the public workplace creation unit 210 creates a new public workplace by Web Dev mapping, the upper collection setting unit 220 sets a user-defined property (environment setting information) together with the highest level collection creation, Makes it available for reference when a folder or file is added.

The property setting unit 240 processes the addition or change of a user-defined attribute required in the process of adding or changing a resource (PUT, MKCOL, COPU, MOVE) by inspecting an environment setting property defined by the parent collection generator 220. Then, the processing result is returned to the client 11.

Hereinafter, the overall operation of the present invention will be described with reference to FIG. 7.

7 is a flowchart illustrating a webdev user-defined attribute processing method according to an embodiment of the present invention.

First, the web dev server 12 generates a public workplace according to a request from the client 11 (S701), receives the configuration information in XML format, and sets a higher collection (S702).

Subsequently, when the webdev server 12 receives a resource registration request from the client 11, the webdev server 12 registers the resource in the corresponding public workplace (S703), and sets a user-defined attribute using the environment setting information defined in the parent collection of the resource ( Add / change) (S704).

As mentioned above, although this invention was demonstrated by the limited embodiment and drawing, this invention is not limited by this, The person of ordinary skill in the art to which this invention belongs, Of course, various modifications and variations are possible within the scope of equivalent claims.

As described above, the present invention effectively sets and manages the user-defined attributes on the Web Dev server side, thereby effectively supporting the development of a Web Dev-based advanced application system to utilize the user-defined attributes on a server level. have.

Claims (10)

Device for processing user-defined attributes on the Webdev server side, Public repository generating means for creating a public repository by Web Dev mapping in response to a request from a client; Higher collection setting means for receiving environment setting information from a client and setting the higher level collection in the public storage; Resource registration means for registering a resource in a corresponding public repository generated by the public repository creating means in accordance with a resource registration request from a client; And Attribute setting means for setting an attribute of the registered resource by using environment setting information set in a higher collection of the public repository Web Dev custom property processing device comprising a. The method of claim 1, The collection setting means, Receives environment setting information defined in XML format from client and sets it in the parent collection of the public repository. Web Dev Custom Property Processing Unit. The method according to claim 1 or 2, The public repository generating means, In response to a request from a client, a public repository is created by mapping a public repository data model to a collection structure of a Web Dev server. Web Dev Custom Property Processing Unit. The method of claim 3, wherein The attribute setting means, Set the custom attribute to the "UserType" element and use the "Depth" element within the "UserType" element to determine which custom attribute to apply to the child element. Web Dev Custom Property Processing Unit. The method of claim 3, wherein The attribute setting means, Processes the addition or change of the user-defined attribute required in the process of adding or changing a resource by inspecting the environment setting attribute defined by the parent collection generating means, and returns the processing result to the client. Web Dev Custom Property Processing Unit. As a method for handling custom attributes on the Webdev server side, A public repository creation step of the webdev server generating a public repository according to a request from a client; A higher collection setting step of receiving, by the Web Dev server, environment setting information from a client, and setting a higher collection of the created public repository; A resource registration step of the webdev server registering a resource in a corresponding public repository according to a resource registration request from a client; And An attribute setting step of setting, by the webdev server, a user-defined attribute using environment setting information defined in a higher collection of the resource Web Dev custom attribute processing method comprising a. The method of claim 1, The collection setting step, Receives environment setting information defined in XML format from client and sets it in the parent collection of the public repository. How to handle Web Dev custom attributes. The method according to claim 6 or 7, The public repository creation step, In response to a request from a client, a public repository is created by mapping a public repository data model to a collection structure of a Web Dev server. How to handle Web Dev custom attributes. The method of claim 8, The attribute setting step, Set the custom attribute to the "UserType" element and use the "Depth" element within the "UserType" element to determine which custom attribute to apply to the child element. How to handle Web Dev custom attributes. The method of claim 8, The attribute setting step, Processes the addition or change of the user-defined attribute required in the process of adding or changing the resource by inspecting the defined environment setting attribute and returns the processing result to the client. How to handle Web Dev custom attributes.

Images