WO2010035071A1

WO2010035071A1 - Method and apparatus for retrieval of one or more addresses where the most updated version of a document is present

Info

Publication number: WO2010035071A1
Application number: PCT/IB2008/055553
Authority: WO
Inventors: Marcello Orizi; Daniele Idini
Original assignee: Prossima Isola S.R.L.
Priority date: 2008-09-26
Filing date: 2008-12-29
Publication date: 2010-04-01
Also published as: ITMI20081715A1; IT1391750B1

Abstract

There is described a method for retrieval of one or more addresses where the most updated version of a document is present, comprising steps of bidirectional dialogue, even remote, between electronic stations of system manager, Publisher- type users, and end-client-type users, comprising the steps of: recording Publisher-type users and end-client-type users in the manager station; recording addresses where the versions of the documents are present, comprising the most updated version, by one or more Publisher stations in the manager station, each document identified by a key, each version identified by a key and one or more addresses; sending, by one or more end-client stations, an identifier key of a document of which the most updated version is to be obtained; verifying, in the manager station, whether, for said document of which the most updated version is to be obtained, a most updated version identified in the manager station exists; if said most updated version exists, replying by said manager station with an address at which said end-client station can retrieve said most updated version and the corresponding key.

Description

METHOD AND APPARATUS FOR RETRIEVAL OF ONE OR MORE ADDRESSES WHERE THE MOST UPDATED VERSION OF A DOCUMENT IS PRESENT

FIELD OF APPLICATION OF THE INVENTION The present invention relates to the field of systems for searching for information and documents through the Internet, and more precisely to a method and apparatus for retrieval of one or more addresses where the most updated version of a document is present.

PRIOR ART The current system for searching for information present on the Internet is based on the use of search engines which operate on the basis of the selection made on the complete set of unsorted information, and which makes it necessary to perform subsequent selection of the information retrieved, until the final choice of that which is required. Therefore, new needs arise to integrate services, to certify contents and to facilitate immediate retrieval of the information required and rejection of those perceived by the user as useless, to facilitate the recovery of information that is always updated and credible.

Therefore, transformation of the Internet into a platform on which applications for the sharing of data, contents and services is in progress.

When people read a given document they may ask themselves whether the one at their disposal is the latest version of this document and, if not, where they can retrieve the latest version.

The document may, for example, contain a price list, links to websites, specifications for the implementation of hardware or software products or protocols; whatever it contains, the document must be updated in order to be useful or simply of interest.

The problem is currently tackled and solved in various know ways. These, for example, include asking someone for confirmation or using a search engine on the Internet, (if the document is freely accessible on the Web). Otherwise, searches are not performed, with the hope that the document to hand is the latest version. These operations cause losses of time which, in any case, do not guarantee that the document available is truly the latest version.

Likewise, those holding the copyrights of the document (hereinafter Publisher) wish to inform possible users that an updated version has been drawn up and is available. It is probable that, to communicate the availability of a new version, the Publisher sends an e-mail to all the customers he knows or adds information on his website or on websites relating to the subject of the document. Also from this viewpoint, there is no guarantee that customers have the latest version of the document at their disposal, and moreover that they are sufficiently diligent to verify whether there are new versions of a previously available document.

Knowing where to retrieve a given version of the document can be of use to verify whether the updated version has been made available at the same address, which may, for example, be an Internet URL or a physical address. Usually however, this information is not known; moreover, there is no guarantee that the updated version of the document is found at the same address (a document that at one time was produced by a given Publisher could now be produced by another Publisher, or a file that at one time was accessible via the Internet at a given URL might now be available at another URL). Another aspect to be highlighted is that often in their history, documents can be merged with other documents or can be divided into other documents. A person who has a given version of a document at his disposal may not know whether subsequent documents resulting from mergers or divisions exist and, above all, where to retrieve these documents. SUMMARY OF THE INVENTION

Thus, the object of the present invention is to solve all the aforesaid problems and to indicate a method and apparatus for retrieval of one or more addresses at which the most updated version of a document is present, such as to: • allow recording of the address/addresses where a given document can be retrieved. • associate a key with each recorded document. This key will allow querying of the document history (address movements, mergers, filiations);

• allow updating, for a given key of a document, of the address/addresses at which the latest version of this document can currently be retrieved;

• return, after any authentication requested by the person who recorded the document, of the address at which it is possible to retrieve the latest version of the document identified by the key provided during recording. Within the present context, the term document is intended as any source of information that carries a meaning, regardless of the medium on which it is recorded. The concept of document is thus one that moves away from being solely something that can be read in the form of written word, but derives from the ability of the searcher to query a material. A material becomes a document when it is capable of arousing the interest of those observing it.

Therefore in the present context it is not assumed that the document is stored on a digital medium: rather, the method and apparatus described herein is completely independent from any medium that is used to record the document and from the form of the address at which this document can be retrieved (URL- Uniform Resource Locator, physical address, etc.).

The present invention relates to a method for retrieving one or more addresses at which the most updated version of a document is present, comprising steps of bidirectional dialogue, even remote, between electronic stations of system manager, Publisher-type users, and end-client-type users, comprising the steps of:

- recording Publisher-type users and end-client-type users in the system-manager station; - recording identifiers of the versions of the documents, comprising the most updated version, by one or more Publisher stations in the manager station, each version being identified by one or more addresses and a key that comprises a coding of the fields: <Publisher, Document, Version>;

- sending, by one or more end-client stations, an identifier key of a document of which the most updated version is to be obtained;

- verifying, in the manager station, whether, for said document of which the most updated version is to be obtained, there exists an identifier of a most updated version;

- if said identifier of the most updated version exists, replying by said manager station with one or more addresses at which said end-client station can retrieve said most updated version and the corresponding key: <Publisher, Document, New Version>.

The present invention relates in particular to a method and an apparatus for retrieval of one or more addresses where the most updated version of a document is present, as better described in the claims, which form an integral part of the present description, BRIEF DESCRIPTION OF THE FIGURES

Further objects and advantages of the present invention will be more apparent from the detailed description below of an embodiment thereof (and its variants) and from the accompanying drawings provided purely by way of non- limiting example, wherein: figure 1 shows a hierarchical structure implemented by the system of the present invention for generation of the keys; figure 2 shows the sequence of steps to update the history of the document when a new version of the document is created, or the address at which it can be retrieved is changed; figures 3a, 3b, 3c show the sequence of steps to update the history of the document in the cases of merging or filiation of subsequent versions of the document; figure 4 shows a operational flow diagram of the method; figures 5 and 6 show flow diagrams of the operations performed respectively by the Publisher and end-client stations.

The same numbers and the same reference letters in the figures identify the same elements or components. DETAILED DESCRIPTION

The invention relates to a method and an apparatus which returns, for each document, the address where the most updated version of a document can be retrieved.

The apparatus is substantially composed of a server manager station, with which two types of client stations dialogue in a bidirectional manner: Publishers, copyright holders of the documents, and end-clients, users of the documents, described hereunder. Dialogues take place through the Internet, therefore in substantially known manner, such as to implement the method of the invention. The method of the invention is described below.

All document versions are recorded by the Publisher on the server by means of identifiers comprising one or more addresses at which the document can be retrieved and a key comprising a coding of the following fields: <Publisher, Document, Version>. An end client, in possession of a document, sends the key to the server. This key can be stored inside the actual document or on a medium supplied together with the document (typically another file).

The server verifies in its database whether, for the document of the Publisher indicated in the request, a new version exists with respect to the one indicated in the key. In the case of this version existing, the server enters in the reply the address or addresses at which the user can retrieve the latest version of the document and the relative key: <Publisher, Document, New Version>.

The key in possession of the end client is updated: in this manner the end client can retrieve the latest version of the document at the address communicated and decide which operations to perform (backup of the previous version, updating of other documents, etc... ).

More in detail, the method substantially entails the following steps: A) Steps of recording users

The system provides a graphic interface through which a generic user can sign on, and subsequently identify himself, as Publisher and/or end user, requesting assignment of a USER-ID and a password. A user signs on to the system in order to: • be able to record documents on the server, and assume the role of

Publisher; • be able to access in reading all the information that Publishers allow to be rendered public only to registered users; • be able to access in reading all the information that a Publisher allows to be rendered public only to registered users indicated by him. B) Steps of interaction of the publisher with the server Recording the document The user signed on correctly as Publisher records on the server, through the graphic interface, the address/addresses at which it is possible to retrieve the latest version of the document he intends to record, thus recording in the system the information that allows access to the document and not the document itself.

For each document recorded by him, the Publisher can enter further information for correct identification of the document, such as an information content that describes the document, or else an information content that describes the version of the document.

For one and the same version of a document, it is possible to record a number of addresses where it is possible to retrieve the latest version of the document.

All the versions of the document whose address/addresses has/have been recorded on the service are identified with the key K = <Publisher, Document, Version>.

The fields Publisher, Document, Version are the identifiers which, considered together, allow the address/addresses required to retrieve a given version of a document recorded by a Publisher to be established at all times, naturally if the

Publisher has recorded on the server the address/addresses where this version can be retrieved.

Each new document recorded by the Publisher is associated with the key Knew = <Publisher, New Document, New Version>.

It is important to note that the system does not store a copy of the document, but only its identifier which allows its retrieval.

Figure 1 shows the hierarchical structure implemented by the system for the generation of keys (a Publisher 1.1 can have a number of documents recorded 1.2, for each document there can be a number of versions recorded 1.3, for each version there can be a number of addresses 1.4 where this version of the

Publisher's document can be retrieved). During the recording step, the Publisher can decide to disclose the address/addresses where a given version of a document recorded by him can be retrieved only:

• to a set of users that have signed onto the service • through the software applications certified by the service

Updating of the document history - new version

With reference to figure 2, when a new version V_N, V_N+_I, V_Z of the document

D| is created, or the address ADR where it is possible to retrieve it is changed, or, in any case, when it has been necessary to change the address/addresses for any other reason, the Publisher can associate to the pair <Publisher P_x, Document D|> the new address/addresses ADR_N where it is possible to retrieve the latest version of the document.

Updating of the addresses entails generation of a new key <Publisher P_x,

Document Di, New Version V_N> During the recording step of the new version, the Publisher can decide to disclose the address/addresses only:

• to a set of users that have signed onto the service

• through the software applications certified by the service

Updating of the document history - merging and/or filiation of documents When a number of documents are merged or the document has created a number of son documents, the Publisher can decide to record this information on the server.

The server links the history of the documents in a father-son type hierarchy. In the case of merging of documents (figure 3a), the resulting document is the son of a number of father documents.

In the case of filiation (figure 3b), a number of son documents have a link with one and the same father document.

There also exists the mixed case of merging and filiation (figure 3c). The server allows recording of the father-son link between two documents.

Each son document continues its history and can generate new versions following the process to record new versions described previously.

The server thus makes it possible to obtain the address/addresses

ADR at which it is possible to retrieve the version/versions of the son documents of the current document, both in the case where a merging of documents has occurred and in the case where a filiation of documents has occurred. The server supplies said addresses together with the corresponding keys K of said son documents.

During the step to record a father-son link between two documents, the

Publisher can decide to disclose the address/addresses only: • to a set of users that have signed onto the service

• through the software applications certified by the service

C) Step of interaction of the end-client with the server and the Publisher

Querying the service

A user in possession of the copy of a given version of a document wishes to verify the existence and address of any updated version of the document and/or any latest versions of the documents resulting from merging and/or filiation that has occurred at any point of the history of the document subsequent to the version currently at his disposal.

To satisfy this need, the client uses a software application of known type, capable of querying the server, by sending the server the fields <Publisher,

Document> contained in the key K of the document.

The key K can be provided (for example stored and/or printed) inside the actual document or on a medium provided together with the document (for example another file or another paper printout). After receiving the query, the server verifies in its database, for the document of the Publisher indicated in the request, which address/addresses corresponds/correspond to the latest version of the document, including any mergings and/or filiations generated during the history of the document subsequent to the version currently at the client's disposal. In the case in which this information is still recorded on the server, the server enters in the reply the address/addresses ADR of the latest version of the document and the relative key/keys = <Publisher, Document, Versions The reply is provided to the application only if the Publisher has not requested any authentication or if the security conditions requested by him in the step to record the version of the document have been complied with.

The application used by the client updates the key in the possession of the end-client, guides him in retrieval of the latest version of the document at the address/addresses communicated and in the decision of which operations to perform (backup of the previous version, updating of other documents, etc.).

The basic diagram of the method, in the absence of mergings and/or filiations of documents and in the absence of contents of a confidential nature, is represented in figure 4.

The seven steps indicated in fig. 4 respectively represent the initial situation (o), querying of the server (1), the reply given by the server (2), verification of the address (3), retrieval of the updated version of the document (4), updating of the key (5), management operations (6). Step (0): Initial situation: the client C02 has at his disposal the old version of the document D_0Id corresponding to the key K₀I_d = <Publisher, Document, Version_O|_d>;

Step (1): Querying the service: the client C02 queries the server C01 using the key K_0Id, the key is sent by the application used (for example, Web page, operating system, document editor);

Step (2): Reply of the server: the engine C01 queries its database and returns the address/addresses [A_new] at which the latest version of the document is found, together with the new key K_new = <Publisher, Document, Version_new^>- Step (3): Address: the application used by the client C02, or a person, goes to the address/addresses communicated [A_new]- These addresses have the form of a URL, of a physical address or any other type of address that identifies the place C03 in which the updated version of the document is located. This address can once again be the same C03.

Step (4): Retrieval of the updated version of the document: the application used by the client C02, or a person, retrieves the updated version of the document

LJ new

Step (5): Updating of the key: the application used by the client C02 updates the key in possession of the end client from K_0Id to K_new

Step (6): Management operations: the application used by the client C02 decides which operations to perform (backup of the previous version, updating of other documents, etc.). The basic diagram of the method, in the presence of mergings and/or filiations of documents, is once again substantially the one represented in figure 4.

The seven steps indicated in the diagram respectively represent the initial situation (0), query of the server (1), the reply given by the server (2), verification of the address (3), retrieval of the updated version of the document (4), updating of the key (5), the management operations (6).

Step (0): Initial situation: the client C02 has at his disposal the old version of the document D_0Id corresponding to the key K_0Id = <Publisher, Document, Version_O|_d>;

Step (1): Querying the server: the client C02 queries the server C01 using the key K_0Id, the key is sent by the application used (for example, Web page, operating system, document editor);

Step (2): Reply of the server: the engine C01 queries its database and returns the address/addresses [A_new] where the latest version of the document is found, together with the new key K_new = <Publisher, Document, Version_new>- Step (3): Address: application used by the client C02, or a person, goes to the address/addresses communicated [A_new]- These addresses have the form of a URL, of a physical address or any other type of address that identifies the place C03 in which the updated version of the document is located. This address can once again be the same C03. Step (4): Retrieval of the updated version of the document: the application used by the client C02, or a person, retrieves the updated version of the document

[Dnew]

Step (5): Updating of the key: the application used by the client C02 updates the key in possession of the end client from K₀^ to [K_new] Step (6): Management operations: the application used by the client C02 decides which operations to perform (backup of the previous version, updating of other documents, etc.). Figure 5 schematically shows the flow chart of the method of the present patent, for the part concerning a Publisher-type user, relative to the steps of:

• Recording new document; • Recording new version of the document;

• Creation father-son link between documents.

Figure 6 schematizes the flow diagram of the method of the present patent, for the part concerning an end-client-type user, relative to the steps of querying the service. Figures 5 and 6 are self-explanatory and do not require further detailed description, as they provide a graphic representation of the method of the invention already described above.

The present invention can advantageously be implemented through a computer program comprising coding means for implementing one or more steps of the method, when this program is run on a computer. Therefore, the scope of protection also extends to said computer program and moreover to means readable by computer, comprising program coding means for the implementation of one or more steps of the method, when said program is run on a computer.

Variants of the non-limiting example of embodiment described are possible, without however departing from the scope of protection of the present invention, comprising all equivalent embodiments for those skilled in the art.

The advantages deriving from application of the present invention are clear. The method described above can be applied in countless scenarios, some of which are described below. Deliver once - update when you want

Let us consider a CD-ROM containing the catalogue with the products of a company, usually distributed during fairs and/or conventions. Using the method this company can achieve the following results:

• the catalogue can be updated at all times by potential clients, if this catalogue is published on the Internet

• it is no longer necessary to physically deliver a new version of the catalogue. This makes it possible to reduce communication costs (for example, it is no longer necessary to burn other CD-ROMs).

• Through our service, company communication is constantly updated without costs for the company and with extremely rapid times which depend on the needs of the end-client. Authentication is not a problem

End-clients can search for the latest version of a document also when it is necessary to provide authentication on the Publisher's website.

This is possible because the method communicates only the location of the file.

This search cannot be performed on conventional search engines (Google, Yahoo, etc.).

Publishers who wish to retain control of access to their documents can continue to do so, but can also easily communicate the availability of a new version of their document.

Search Engine Optimization With the method it is also possible to index a hidden part of web, i.e. the part composed of addresses recorded in the server and not freely accessible by clients and by search engines.

Web site restyling

Let us consider the case of a Publisher with numerous documents published on his website and who needs to reorganize the structure of his website. If the

Publisher uses the method regularly, he can direct clients to easily retrieve the new addresses at which the documents are located. By doing this, he avoids alienating clients as they:

• are able to retrieve the information searched for without having to waste time in new searches

• experience less of the typical confusion caused by renewal of the structure of the website.

Maintaining Page Rank

Investments made by a Publisher to remain in at the top of the rankings in queries by Internet users on the various search engines are not lost if the website in question has to move to another address. The webmaster of the website can in fact ask the person who references his website in other web pages to reference it through the key obtained during recording on the server described above. In this manner, if the indexed website is moved, all links that reference it are updated from the old address to the new address, consequently maintaining page rank. Bookmarks Bookmarks, both those present in the various browsers (Internet Explorer,

Firefox, Chrome etc.) and those shared between user communities (Digg, Delicious etc.) based on the method described above can store the key of the document in place of its current address. In this manner, the end client would have the certainty that his Bookmarks always send him to the page required, even if the page is moved to different points of a website or from one website to another. Creating communication models

Through the service described above it is possible to create communication models that are always updated. Let us consider the case of e-mails containing links to pages of the company website; these remain valid even if the company decides to change the structure of its website. It would be possible to attach documents that can be updated at any time: a letter sent two months ago, when re-opened by the client, could contain current data if requested by the client. The service allows communication of our data to the client updated at the moment he requests this.

Constantly updated contacts

Through the method described above it is possible create address books of contacts that can be constantly updated from any platform (PC, mobile telephone, handheld computer, etc.). Instead of exchanging telephone number or e-mail address, people can exchange the key that identifies the address/addresses at which a document containing the contact's information can be retrieved. When a person wishes to ensure he has the updated contact of a friend or colleague, he can query the service through the key associated with the contact of this person and retrieve the address/addresses at which the updated contact is found. From the description above those skilled in the art are capable of implementing the object of the invention without introducing further details requiring either the hardware or software aspects.

Claims

C L A I M S

1. Method for retrieval of one or more addresses where the most updated version of a document is present, comprising steps of bidirectional dialogue, even remote, between electronic stations of system manager, Publisher-type users, and end-client-type users, comprising the steps of:

- recording Publisher-type users and end-client-type users in the system-manager station;

- recording identifiers of the versions of the documents, comprising the most updated version, by one or more Publisher stations in the manager station, each version being identified by one or more addresses and a key that comprises a coding of the fields: <Publisher, Document, Version>;

- verifying, in the manager station, whether, for said document of which the most updated version is to be obtained, there exists an identifier of a most updated version identified in the manager station;

2 . Method for retrieval of one or more addresses where the most updated version of a document is present according to Claim 1 , wherein said step of recording Publisher-type users and end-client-type users in the manager station envisages a graphic interface through which a user station can sign on, and then identify itself, as Publisher and/or as end client, requesting assignment of a USER-ID and a password, to perform operations of the following types:

- storing the documents in the manager station, and assuming the role of Publisher station;

- accessing in reading all the information that the Publisher station allows to be rendered public only to the registered stations; and - accessing in reading all the information that the Publisher station allows to be rendered public only to the registered user stations indicated by said Publisher station.

3. Method for retrieval of one or more addresses where the most updated version of a document is present according to Claim 1 , wherein said step of recording identifiers of the versions of the documents comprises a further step in which said Publisher station enters further information of correct identification of the document, which can comprise an information content that describes the document, or else an information content that describes the version of the document.

4 . Method for retrieval of one or more addresses where the most updated version of a document is present according to Claim 1 , wherein said step of storing identifiers of the versions of the documents comprises a further step in which said Publisher station, for one and the same version of a document, stores a number of addresses where it is possible to retrieve said document.

5. Method for retrieval of one or more addresses where the most updated version of a document is present according to Claim 1 , wherein said key that comprises a coding of the fields <Publisher, Document, Version> comprises a hierarchical structure such that a Publisher station (1.1) can have a number of stored documents (1.2), for each document there can be a number of stored versions (1.3), and for each version there can be a number of addresses (1.4) where it is possible to retrieve said version of the document.

6. Method for retrieval of one or more addresses where the most updated version of a document is present according to Claim 1 , wherein said step of recording identifiers of the versions of the documents comprises:

- when a new version (V_N, V_N+_I , V_Z) of the document (Di) is created or the address (ADR) where it is possible to retrieve the document is changed, or, in any case, when any other reason may have generated the need to change the address/addresses, the Publisher station associates to the pair <Publisher P_x, Document D|> the new address/addresses (ADR_N) where it is possible to retrieve the last version of the document; updating of the addresses entailing generation of a new key <Publisher P_x, Document Di, New Version V_N>;

- when said new version is stored, the Publisher station can decide to disclose the address/addresses only to a set of end-client stations that have signed onto the service.

7 . Method for retrieval of one or more addresses where the most updated version of a document is present according to Claim 6, wherein said step of updating the history of the document comprises a step of filiation of documents, in which said manager station links the history of the documents in a father-son-type hierarchy, such that, in the case of merging of documents, the resulting document is the son of a number of father documents, whereas in the case of filiation, a number of son documents have a link with one and the same father document, making it possible to obtain the address/addresses (ADR) at which it is possible to retrieve the version/versions of the documents that are daughters of the current document, both in the case where a merging of documents has occurred and in the case where a filiation of documents has occurred, supplying said addresses together with the corresponding keys of said daughter documents.

8. Method for retrieval of one or more addresses where the most updated version of a document is present according to Claim 1 , wherein said step of sending from one or more end-client stations an identifier key of a document of which the most updated version is to be obtained comprises a step of sending by the end-client station to the manager station fields <Publisher, Document> contained in the key K of the document, said key of the document being previously made available.

9. Apparatus for retrieval of one or more addresses where the most updated version of a document is present, said apparatus comprising at least one electronic service-manager station, one or more electronic stations of Publisher- type users and end-client-type users that dialogue with one another in a bidirectional way and are able to implement the method according to any one of the preceding claims.

10. A computer program that comprises program-coding means designed to implement the steps of Claims 1 to 8, when said program is run on a computer.

11. Computer-readable means comprising a stored program, said computer- readable means comprising program-coding means designed to implement steps of Claims 1 to 8, when said program is run on a computer.