WO2007012657A1

WO2007012657A1 - System for exchanging specific informational data between two web sites, corresponding method and computer programme

Info

Publication number: WO2007012657A1
Application number: PCT/EP2006/064725
Authority: WO
Inventors: Jérôme Cochet; Frédéric Martin; Vincent Mahe
Original assignee: France Telecom
Priority date: 2005-07-27
Filing date: 2006-07-27
Publication date: 2007-02-01

Abstract

The invention concerns a system for exchanging data between at least one first Web site, hosted on a first server and at least one second Web site, hosted on a second server, said data being carried via a communication network. The invention is characterized in that said data are informational data specific of said at least first and/or of said at least second Web site, such a system comprising: at least one support describing said specific informational data associated with said at least first Web site and/or with said at least second Web site; command processing means for exchanging at least some of said specific informational data, between said at least first and said at least second Web sites, said commands originating from one of said Web sites participating in said system addressed to another Web site participating in said system.

Description

System for the exchange of specific informational data between two web sites, method, server and corresponding computer program.

1. Field of the invention

The field of the invention is that of the exchange of information between web sites. More specifically, the invention relates to the standardization of the exchange of information between websites, allowing the sites to homogenize the information they hold and establish a mutual referencing.

The vast majority of websites, for example the so-called

"Logbooks" ("weblogs", also called "blogs") or personal pages, provide information in the form of dynamically constructed HTML pages from multimedia database contents.

However, these HTML pages vary significantly in terms of presentation of information. The databases containing the information to display are very disparate, both in terms of structure and content, and require means of building very heterogeneous HTML pages.

2. Solutions of the Prior Art 2.1 Prior Art

Several techniques of exchanging information between websites are already known. The information exchanged is however very fragmentary and the exchange formats are disparate.

Thus, the websites (personal pages, "weblogs", commercial sites ...) often have a "favorite sites" section in which the creator of the website indicates the list of websites that he is used to consult or sites that are related to the theme of his own site. This list shows the names of the sites and their URL (Uniform Resource Locator).

For the owner of the website, the addition of another site to its list of "favorite sites" then passes by the addition of a couple {site_name, URL_site}, including the name of the site to add, as well as the URL from which it can be reached. This static addition can be done in two ways: By adding HTML code in the case of using an HTML editor;

By entering a form in the case of using a website creation wizard and saving this couple in a database.

This technique makes it possible to establish referencing between the sites unilaterally at the initiative of the owner of the website who wants to reference another.

In the field of "blogs", the information is made available by the website wishing to be referenced in the form of an RSS feed. This RSS feed is an XML document containing the list of the latest articles published on the website. For the website offering this RSS feed, it is a way to make available to other sites the list of the latest news of the site in a structured format. This technique makes it possible to exchange information between sites unilaterally at the initiative of the owner of the website who wants to be referenced.

Still in the field of "blogs", the Outline Processor Markup Language (OPML) format is a format for exchanging lists of "blogs" between web sites.

This format is implemented as an XML file that serves as an entry point for site aggregators, used to reference multiple

"Blogs". This technique also allows the exchange of information unilaterally.

Finally, some websites have means of describing people and the relationships they maintain between them, always in the form of an XML file respecting the format FoaF (Friend of a Friend, for "Friend of a

Friend "). This particular file follows a complex Resource Description Framework (RDF) semantics.

2.2 Disadvantages of the Prior Art

These techniques of the prior art have many disadvantages.

With respect to manually adding a URL of a website to another site, a disadvantage of this prior art technique is the lack of a bilateral relationship between the two websites. Indeed, the website that has added in its list of sites preferred a link to another site did not obtain authorization from the latter. In addition, the link created is static and does not allow the website that references another to be aware of the latest news or latest developments of the referenced site. As for the RSS, OPML or FoaF based exchanges, another disadvantage of these prior art techniques is that these formats only offer a fragmentary view of a dynamic website. The RSS format only offers a view of the latest published articles. The OPML format proposes the provision, in structured form, of the list of preferred sites for an exchange with other sites. The FoaF format makes it possible to carry out a description of the owner of the site and its relations with other people. These exchange standards therefore make it possible to provide only views of a site, and not all of it. In addition, the files using these standards are made available by the website wishing to disseminate information. Therefore, at no time, the site that provides information is informed of the actual use of this information or the form of this use. In the case of sensitive or personal professional information, this lack of visibility is a major drawback of these techniques of the prior art. Indeed, they do not make it possible to certify that the use that is made of the information is in accordance with the wishes of the user.

Another disadvantage of these techniques of the prior art is that these formats are not suitable for specifying the relationship modes existing between two websites. This does not allow users and visitors to linked sites to clearly validate the source of the information presented or verify its veracity. 3. Objectives of the invention

The invention particularly aims to overcome these disadvantages of the prior art.

More specifically, an object of the invention is to provide a technique that introduces a two-way exchange of information between web sites entering a mutual referencing process, particularly suited to dynamic websites.

Another objective of the invention is to propose such a technique of bilateral exchange of information making it possible to ensure the dynamic update of referencing between the websites.

The invention also aims to provide such a technique for the complete description of a website, incorporating all available information about its latest updates, linked sites, stakeholders, etc. Yet another object of the invention is to provide such a technique that can guarantee the control of the dissemination of information made available on a website.

Another object of the invention is to provide such a technique to clarify the relationship between websites. Furthermore, the invention also aims to provide such a technique that allows the structuring and typing of information exchanges between websites.

A final objective of the invention is to propose such a technique that does not induce or increase the complexity of the websites. 4. Summary of the invention

These objectives, as well as others that will appear later, are achieved by means of a data exchange system, between at least one first website, hosted on a first server and at least one second. web site, hosted on a second server, said data being conveyed through a communication network.

According to the invention, said data being informational data specific to said at least first and / or said at least second web site, such a system comprises: at least one descriptive support of said specific information data associated with said at least one first web site and / or audit at less a second website; command processing means for exchanging at least some of said specific information data, between said at least first and at least second web sites, said commands originating from one of said web sites participating in said system to another site web participant in this system.

Thus, the invention is based on a new approach to the exchange of data between web sites, according to which the exchange is governed by order processing means based on information contained in a descriptive medium, for example under the form of an XML document. The data exchanges are performed bilaterally by the processing means, which communicate with each other by exchanging valid data from the descriptive media, without the intervention of users on the content of the exchanges. Thus the exchange of information is standardized and sequenced, in order to guarantee the validity and accuracy of the data exchanged.

Advantageously, said specific information data belong to the group comprising at least: general data relating to said website; specific data relating to the owner of the said website; a list of websites linked to said website also containing types of relationship maintained with said website; a list of persons related to the owner of said website also containing types of relationship maintained with the owner of said website. Thus, the definition of this specific informational data makes it possible to describe the websites, to limit the information exchanged between the websites and to know precisely the types of data exchanged.

Preferably, said types of relationship maintained with said web site belong to the group comprising at least: - preferred website; website to avoid; list of websites known as "logbooks"("bloglist"); friends list.

The definition of these types of relationship clarifies dependencies between the different websites that have relationships. Thus, the nature of the relationship being identified, it is possible to differentiate the behaviors of the websites entering into relationship and to offer possibilities of treatment of the bilaterality of the exchanges.

Preferably, said command processing means are accessible from said web sites of said network.

In this way, communications between websites wishing to exchange specific information is not constrained by obtaining access permissions.

According to a preferred embodiment, said command processing means are in the form of a URL (Uniform Resource Locator) command.

The use of a URL (Uniform Resource Locator) then makes it possible not to have to set up a new complex communication method, and to use the protocols defined by the URLs. This command URL, and more generally the order processing means, may be public, in the case for example where the communication network is the global Internet network. In the case where this network is intranet type, the order URL is accessible to all the websites of the intranet considered. Advantageously, said command URL accepts requests for information requests and / or requests for updating information and provides responses and / or data based on said requests.

The definition of these queries makes it possible to precisely describe the types of exchanges between the websites. Preferably, said requests for information request and said information update requests are composed of: a type of processing to be performed; at least one parameter necessary for accomplishing said type of treatment. Thus, the composition of the requests induces an additional operational security insofar as only the requests respecting this format will be processed by the command URL.

According to a preferred mode of implementation, said types of processing to be carried out belong to the group comprising: adding said first website to a list of preferred sites of said second website;

Deleting said first website from a list of preferred sites of said second website;

Acceptance by said second website of an addition of said second website to a list of preferred websites of said first website;

Refusal by said second website of adding said second website to a list of preferred sites of said first website;

Retrieving an XML information document associated with a website (

Subscribing said first website to at least one notification of adding at least one new information to said second website;

Unsubscribing from said first website to said adding notification;

Recovery by said first web site of at least one information contained in said descriptive medium associated with said second website.

The security of the operation of the system is thus reinforced, since the types of treatment are defined. It is thus impossible to carry out treatments that are not authorized by the URL.

Advantageously, said at least one parameter necessary for the completion of said type of treatment belongs to the group comprising:

An identifier of an owner of said first and / or second website; Said command URL of said first and / or said second website;

One type of notification

At least one notification parameter;

An identifier of the at least one information to be retrieved. Thus, the parameters of the commands complete the capacity of the system to ensure a predictable and secure operation of the exchange of specific informational data.

According to a preferred implementation mode, said responses are responses in HTTP format containing an XML document indicating a failure or a success or said at least one information to be recovered.

Queries in HTTP format are automatically supported by all web hosting platforms. The http protocol for sending and receiving requests is thus a guarantee of interoperability between the systems, guaranteeing the functioning of the system for all the hosts.

The use of XML for the generation of command responses and the transfer of specific informational data ensures maximum interoperability between web sites wishing to exchange specific informational data. Indeed the XML language is accepted by all web hosting platforms. In addition, all these platforms have means for decoding XML documents. XML is also particularly suitable for this type of exchange because it allows you to define documents with a tree structure. Such a structure makes it possible to process the information efficiently and participates in the speed of processing of the exchanged data.

Advantageously, each of said web sites is selectively associated with one of said descriptive media comprising said informational data specific to said corresponding web site.

Thus, each website has its own information that is not shared with other websites of the same type. This guarantees the confidentiality of the information associated with the website owning its descriptive support.

The invention also relates to a method for exchanging data between at least one first web site, hosted on a first server and at least one second web site, hosted on a second server, by means of a communication network.

According to the invention, said data being informational data specific to said at least first and / or said at least second website, such a data exchange method comprises a step of transmitting at least one data exchange command. at least some of said specific informational data, by said at least first website to a command URL of said second website.

As already indicated above in connection with the data exchange system of the invention, in such a method, the specific information data are stored on at least one descriptive medium and belong to the group comprising at least: general data relating to said website; specific data relating to the owner of the said website; a list of websites linked to said website also containing types of relationship maintained with said website; a list of persons related to the owner of said website also containing types of relationship maintained with the owner of said website.

In addition, in the context of this data exchange method, said types of relationship maintained with said web site belong to the group comprising at least: preferred website; website to avoid; list of websites known as "logbooks"("bloglist"); - friends list. Advantageously, in such a data exchange method of the invention, said exchange command is a request for information request and / or a request for updating information. Such requests are preferably composed of: a type of processing to be performed; at least one parameter necessary for accomplishing said type of treatment.

According to an advantageous characteristic of such an exchange method, said transmission step belongs to the group comprising: a step of sending a request to add said first website to a list of preferred sites of said second website ; a step of issuing a request to delete said first website from a list of preferred sites of said second website; a step of issuing a request to add said second website to a list of preferred sites of said first website; a step of issuing a request for recovery by said first website of an information XML document associated with said second website; a step of issuing a subscription request of said first website to at least one notification of adding at least one new information in said second website; a step of issuing a request to unsubscribe from said first website to said adding notification; a step of issuing a request for retrieval of at least one information contained in said descriptive medium associated with said second website.

Preferably, for such a data exchange method of the invention, said at least one parameter necessary for the completion of said type of treatment belongs to the group comprising:

One type of notification

At least one notification parameter;

An identifier of the at least one information to be retrieved. In addition, advantageously, such a method also comprises a step of receiving a response to said command issued by the first website, according to a processing performed by the second website, said response comprising at least some of said specific information data from at least one descriptive medium associated with said second website. Advantageously, such a response is an HTTP format response containing an XML document indicating a failure or a success or said at least one information to retrieve.

The invention also relates to a computer program product for exchanging data, between at least one first web site, hosted on a first server and at least one second web site, hosted on a second server, by means of a communication network, downloadable from a communication network and / or stored on a computer readable medium and / or executable by a microprocessor. According to the invention, such a computer program product includes program code instructions for carrying out the steps of the data exchange method described above.

The invention also relates to a data exchange server in a data exchange system, between at least one first web site, hosted on a first server and at least one second web site, hosted on a second server, by means of a communication network. Such a server comprises means for implementing all the steps of the data exchange method described above.

The invention also relates to a second data exchange method, between at least one first web site, hosted on a first server and at least one second web site, hosted on a second server, by means of a communication network.

he According to the invention, said data being informational data specific to said at least one first and / or said at least one second web site, said second method comprises a step of processing at least one exchange command of at least some said specific information data, received on a command URL of said at least one second website.

As already indicated above in connection with the system and the first data exchange method of the invention, in this second method, the specific information data are stored on at least one descriptive support and belong to the group comprising at least one : general data relating to the said website; specific data relating to the owner of the said website; a list of websites linked to said website also containing types of relationship maintained with said website; a list of persons related to the owner of said website also containing types of relationship maintained with the owner of said website.

In addition, in the context of this second method of data exchange, said types of relationship maintained with said website belong to the group comprising at least: preferred website; website to avoid; list of websites known as "logbooks" ("bloglist"); friends list. Advantageously, according to this second data exchange method of the invention, said command processing step is implemented by access from said network web sites to a command URL.

Advantageously, the second data exchange method of the invention also comprises a step of providing responses and / or data to said first website, according to said commands received. These commands are requests for information requests and / or requests for updating information, and are composed of: a type of processing to be performed; at least one parameter necessary for accomplishing said type of treatment.

Preferably, said responses are responses in the format http containing an XML document indicating a failure or a success or said at least one information to recover.

Advantageously, said step of processing an exchange command implements a type of processing belonging to the group comprising: acceptance by said second website of an addition of said second website to a list of preferred websites of said first website ; refusal by said second website of an addition of said second website to a list of preferred sites of said first website; providing said first website with an XML information document associated with the second website; providing said first website with at least one information contained in said descriptive medium associated with said second website.

Preferably, said second method also comprises a step of updating, as a function of said processing, at least one descriptive support of said informational data of said second website.

Such an updating step consists for example in: adding the first website to a list of preferred sites of the second website; - remove the first website from a list of favorite sites from the second website; add the first website to a list of sites subscribed to at least one notification of adding at least one new information in the second website; - delete the first website from a list of sites subscribed to at least one notification of adding at least new information in the second website; add the first website to a list of sites referencing the second website; - remove the first website from a list of sites referencing the second website.

Advantageously, said processing step uses said at least one parameter necessary for the accomplishment of said type of processing, conveyed by said command, and which belongs to the group comprising: an identifier of an owner of said first and / or said second website ;

Said command URL of said first and / or said second website;

One type of notification

At least one notification parameter; An identifier of said at least one item of information to be retrieved.

The invention also relates to a computer program product for exchanging data, between at least one first web site, hosted on a first server and at least one second web site, hosted on a second server, by means of a communication network, downloadable from a communication network and / or stored on a computer readable medium and / or executable by a microprocessor. According to the invention, such a computer program product comprises program code instructions for implementing the steps of the second data exchange method described above.

The invention also relates to a data exchange server in a data exchange system, between at least one first web site, hosted on a first server and at least one second web site, hosted on a second server, by means of a communication network. Such a server comprises means for implementing all the steps of the second data exchange method described above. Advantageously, the two preceding data exchange methods can be implemented in concert to provide a global process for managing the specific informational data of a website. Thus, it is not necessary to have several processing entities relating to each of the two methods. 5. List of figures

Other features and advantages of the invention will appear more clearly on reading the following description of a preferred embodiment, given as a simple illustrative and nonlimiting example, and the appended drawings, among which: FIG. 1 illustrates the architecture of a system for the exchange of specific information data, according to the invention; Figure 2 schematically illustrates the hardware structure of the server of Figure 1; Figure 3 describes the logical structure of the flow of information and processing leading to the exchange of specific information between two web sites; Figure 4 illustrates a request to add a "weblog" "A" in the list of preferred websites of a "weblog" "B"; Figure 5 illustrates a request to delete a "weblog" "A" in the list of preferred websites of a "weblog" "B"; Figures 6 and 7 illustrate the different states of a "blog" contained in a "bloglist"; Figure 8 shows an exchange for obtaining general information of a "weblog"; - Figure 9 shows the notification mechanism of the addition of the last articles of a "weblog" "A" to a "weblog" "B" via the RSS feed of the

"Blog""A"; Figures 10, 11 and 12 illustrate the mechanism of subscription, unsubscription and the notification of the addition of the last articles of a "weblog""A" to a "weblog""B" via the mail services SMS (Short Message Service), MMS (Multimedia Message)

Service); Figure 13 shows the mechanism for obtaining information about the owner of a "Weblog"; - Figure 14 presents the mechanism for obtaining information on

"Weblogs" preferred from a "weblog"; Figure 15 illustrates obtaining information on "weblogs" referring to a "weblog".

6. Detailed description of the invention 6.1 Recall of the principle of the invention

In the context of the present invention, it is therefore interested in the exchange of specific informational data between web sites, based on a structured support for exchanging informational data and on specific means to make the exchanges concrete. The general principle of the invention is based on the bilateral processing of information data exchange. This informational data is defined in a file specific to the website in question. The exchange of data is done automatically between the websites. Thus, the user does not have to worry about the consistency or the validity of these data. The websites are spread over the entire Internet network and each have a support for informational data and means of processing commands for exchanging informational data.

Figure 1 is a simplified illustration of an exemplary architecture implementing an embodiment of the invention. The web site 101, hosted in a server 10, contains means for processing information exchange commands 102 linked to an information data medium 103 containing information data specific to the web site 101.

The structure of the server 10 is illustrated schematically in FIG. 2. It also comprises a memory M 21, and a processing unit 20 equipped with it. a microprocessor μP, which is controlled by a computer program (or application) Pg 22. The processing unit 20 receives, via a network input interface module E 23, requests and / or customer responses 24, that the microprocessor μP processes, according to the instructions of the program Pg 22, to generate commands and / or responses 26, which are transmitted via a network output interface module S 25.

A particular example of implementation of the system of FIG. 1 can be obtained from the following technical base, which comprises:

An HTTP protocol management server (web server) 10 which can be for example of type IIS, Apache, Netscape, SUN iPlanet (registered trademarks).

It is he who hosts the website 101;

A command URL 102, acting as a means of processing information exchange commands. It can advantageously be based on: - The Java language and be implemented in the form of independent modules ("servlet") or in the form of a dynamic JSP content generator ("Java Server Page"), for example IBM WebSphere, BEA Web Logic, Netscape Enterprise server, Oracle Application Server, SUN Iplanet (registered trademarks), - ASP / COM language (ASP .NET, Microsoft Transaction

Server (registered trademarks)),

An implementation of Web Services or a PHP language; A structured XML file 103, which contains the specific informational data of the website 101. In another embodiment, the specific information data (103) of the website can also be placed in a conventional text file or in a database private website.

Subsequently, the case of an embodiment of the support of specific informational data, in the form of an XML file, in the context of so-called "roadmap" websites ("blogs"), is also presented. called "weblogs"), as well as an embodiment of the means for processing the commands for exchanging this data, in the form of an Internet address (URL) accessible for these sites.

It is clear, however, that the invention is not limited to this particular application, but can also be implemented in many other fields, and for example in the context of websites defining person-to-person relations and more generally in all cases where the objectives listed below are interesting.

6.2 Support of specific information data. According to the invention, the specific informational data specific to each website are organized within a descriptive medium. These informational data induce a specific structure in the medium. In a particular embodiment of the invention, this support is an XML file. In this embodiment, the information data are as follows: - General information about a website:

The title of the website; The address of the website;

The address of the RSS feed containing the news of the website, when the site has such an address. - Information about the owner of the website:

The full name (name and surname concatenated, for example). It can also be the name of a company or an association; An address: it can be a postal address or an e-mail address for example. - Information on the list of websites linked to this website:

A list of the preferred sites of the website, if the latter has links to favorite sites;

A list of sites referring to this website as a preferred site, if any; - For each website of the two previous lists, the elements following are desirable: Name of the website; Website address;

Access address to the order processing means for the exchange of informational data of the website.

In another particular embodiment of the invention it is also possible to add to the specific information data the following elements:

In the general information on a website: - The theme of the website;

A description of the website;

A date of creation and a date of last modification of the website;

A list of categories to organize the articles published in the website.

In the information about the owner of the website: The first and last names;

A telephone number (for sending messages, for example) or a connection number to an instant messaging service;

An address of the location of a photo of the owner of the website;

An address of a FoaF document associated with the owner of the website. In this embodiment, for the purpose of implementing the invention within web sites known as "logbooks" ("weblogs"), the DTD (Document Type Definition) describing the XML file of the specific information data would be the following :

<? xml version = "1.0" encoding = "iso-8859-l"?> <! ELEMENT blogml

(embarrassing, owner, bloglist, otherInformation?)><! ELEMENT embarrassing (title, url, theme ?, description ?, dateCreated?, dateModified ?, categories ?, rssFeed)>

<! ELEMENT owner

(name, firstname?, surname?, mobileNumber?, email, phot oUrl?, seeAlso?)>

<! ELEMENT bloglist (in, out)>

<! ELEMENT otherlnformations (information +)>

<! ELEMENT title (#PCDATA)>

<! ELEMENT url (#PCDATA)> <! ELEMENT theme (#PCDATA)>

<! ELEMENT description (#PCDATA)>

<! ELEMENT dateCreated (#PCDATA)>

<! ELEMENT dateModified (#PCDATA)>

<! ELEMENT categories (category +)> <! ELEMENT category (name, description?, Url)>

<! ELEMENT name (#PCDATA)>

<! ELEMENT rssFeed (#PCDATA)>

<! ELEMENT firstname (#PCDATA)>

<! ELEMENT lastname (#PCDATA)> <! ELEMENT mobileNumber (#PCDATA)>

<! ELEMENT email (#PCDATA)>

<! ELEMENT photoUrl (#PCDATA)>

<! ELEMENT seeAlso (#PCDATA)>

<! ELEMENT in (blog *)> <ELEMENT OUt (blog *)>

<! ELEMENT blog (name, url, urlCmd)>

<! ELEMENT urlCmd (#PCDATA)>

<! ELEMENT information (#PCDATA)>

In this case, this description DTD is called "BlogML".

In an alternative embodiment of the invention, this structure for defining specific information data can be described within a database that has the same elements and the same element and attribute definitions as the XML file. .

In yet another embodiment, the structure can also be implemented in a simplified form within a text file. 6.3 Description of the commands of the processing URL for the exchange of specific informational data.

The transfer of information between web sites is defined by the principle of requests made by the website requesting the information. These requests include: commands for identifying the actions to be performed by the data exchange processing URL; parameters necessary to carry out these actions.

We give here a non exhaustive list of the commands that can be implemented within the URL:

Upon receiving these requests, the receiving URL of the command performs the processing requested by the command and provides a response to the website requesting the information. In this embodiment, the response provided to the website requesting the information is an XML document. In another embodiment, it is conceivable that the processing related to the command is not performed by the command URL itself, but by a remote server, present on the Internet for example.

In a particular embodiment of the invention, linked to the exchange of information specific to web sites called "logbooks", a non-exhaustive list of the commands implemented by the URL is presented (it is recalled that by " bloglist "we hear the list of favorite" blog "of a given website):

The previous commands can be largely completed according to the functionalities envisaged for the exchange of data.

6.4 Description of the response format to queries issued by the rURLs for the processing of specific informational data exchanges.

In a specific embodiment of the invention, and excluding particular commands, the commands from the processing URL of the specific informational data exchanges return an "http" response containing an XML document indicating the failure or the success of the application. The DTD of this XML document can then be:

<? xml version = "1.0" encoding = "iso-8859-l"?> <! ELEMENT CmdResp EMPTY> <ATTLIST CmdResp type (ERRORI OK) #REQUIRED CDATA message #IMPLIED>

In another embodiment, the responses could be returned as return codes identifying the good or bad operation of the request.

6.5 Description of a processing URL for specific informational data exchanges

In connection with FIG. 3, an embodiment of a command URL for handling the exchanges of specific informational data between two web sites known as "logbooks"("weblog") is presented. Each "weblog" (respectively 101 and 111) is associated with a single command URL (respectively 102 and 112) that allows to send commands to this "weblog". This URL is available to readers of the "weblog". In a particular embodiment, this command URL may be accessible from the home page of the "weblog", by means of a hypertext link to this URL, for example.

The command URLs 102 and 112 respectively access and update the specific information data contained in the XML files 103 and 113.

When requesting the exchange of information between the "weblog" 101 and the "weblog" 111, the principle of the embodiment of the system is as follows:

Via the server 10, the "weblog" 101 transmits on the communication network

12 an HTTP (HyperText Transfer Protocol) request for "hypertext transfer protocol" 13 to "weblog" 111;

The server 11 receives the request 12 and transmits it (114) to the command URL 112;

The URL 112 executes the processing necessary for the execution of the command by consulting and / or updating (115) the XML file 113;

The URL 112 constructs a response 116 to the command URL 102 of the "weblog" 101;

The response 116 is routed 14 to the server 10 by the communication network 12; The server 10 transmits (104) this response to the command URL 102;

The command URL 102 carries out the processing necessary to take account of the response and / or updates (105) the XML file 103.

In the following descriptions detailed embodiments of adding, deleting, notifying and exchanging data contained in the XML files are detailed. 6.5.1 Add / Remove a "weblog""A" from the "bloglist" (blog list) from a "weblog""B".

6.5.1.1 Adding a "weblog" "A" in the "bloglist" of a "weblog" "B". In connection with FIG. 4, an embodiment of an exchange of specific information data between two web sites known as "logbooks" ("weblog") for adding a "weblog" "A" to the list of favorite sites of a "weblog" "B". In this embodiment, the command URLs (respectively the command URL "A" and the command URL "B") issue and receive the requests and return the responses associated with the received requests. The processing related to the manipulation of the data is governed by server applications (respectively the server application "A" and the server application "B").

The request to add a "blog" "A" 50 to the "bloglist" of a "blog" "B" 40 is composed of the following steps:

The server application "B" of the "blog" "B" (40): adds a node 42 <blog> in the node "<bloglistxin>" of the document blogML "B"; sends an "addblogTobloglist" action 43 to the command URL "A";

The command URL "A" receives and processes (51) the action "addblogTobloglist" by requesting the action "getblogML" 52 to the command URL of the "blog" "B" (40);

The command URL "B" receives and processes (44) the "getblogML" action and sends the blogML "B" document as an answer 45;

The command URL "A" receives the blogML document "B" 53 and verifies 54 the node <blog> corresponding to "A" in the blogML document "B":

If an abnormality is detected (55) during the check 54, the command URL "A" sends a response 56 containing a error notification to the action "addblogTobloglist and the process ends.

If no anomaly is detected (55) during the check 54, the command URL "A" sends a response 56 containing a notification of taking into account the action "addblogTobloglist" and the process continues;

The server application "A" then verifies (57) that the owner "A" is informed of the request to add:

If this is the case, the server application "A" adds a node <blog> in the node "<bloglistxout>" of the blogML document "A" (58);

If the owner "A" is not informed of the request, the server application "A" remains in the waiting state until the owner "A" has been informed;

When the owner "A" has been informed 58 of the request, the server application checks 59 that the owner "A" accepts the request to add from the blog "B".

If so, the server application "A" sets (510) the "state" attribute of the created <blog> node to "accepted" and sends an "acceptblog" action 512 to the command URL " B "; - If the owner "A" does not accept the addition, the server application

"A" sets (511) the "state" attribute of the <blog> node created to "refused" and sends a "refusblog" action to the "B" command URL;

According to the response of the "blog" "A", the server application "B" receives and processes either the "refusblog" action 46 or the action

"acceptblog" 47;

Whatever the action being processed (46 or 47), the server application "B" verifies

48 the node <blog> corresponding to "A" in the blogML document "B" then sends 49 a request "getblogML" to the command URL "A"; Command URL "A" receives and processes 514 the request "getblogML", then sends 515 as a response to this request the blogML "A"document;

The command URL "B" receives 410 the blogML document "A" and verifies the <blog> node corresponding to "A" in the blogML "A" document:

If an anomaly is detected (412) during the check 411, the command URL "B" sends a response 413 containing an error notification to the action "refusblog" or "acceptblog" and the process ends. - If no anomaly is detected (412) during the verification 411, the command URL "B" sends a response 413 containing a notification of taking into account the action "refusblog" or "acceptblog" and the process continues ; The server application "B" verifies 414 the type of action: - In case of refusal ("refusblog" action) the server application

"B" sets 415 the "state" attribute of the <blog> node corresponding to "A" in the blogML "B" document to "refused";

In case of acceptance ("acceptblog" action) the server application "B" sets 416 the "state" attribute of the node

<blog> corresponding to "A" in the blogML document "B" to the value "accepted";

The server application "B" verifies 417 that the owner "B" is informed of the response of the "weblog""A": - If the owner "B" is not informed of the response, the server application "B" Remains in standby 417 until owner "B" has been informed; If the owner "B" is informed, the server application "B": - Removes 418 the node <blog> corresponding to "A" in the blogML document "B", in the case where the response of the command URL "A" is negative ("refusblog"action); Sets 419 the "state" attribute of the <blog> node corresponding to "A" in the blogML document

"B" to the "active" value.

The processing steps of the link establishment request from "blog" "B" to "blog" "A" are then completed.

6.5.1.2 Deletion of a "weblog" "A" from the "bloglist" of a "weblog" "B".

In connection with FIG. 5, an embodiment of an exchange of specific information data between two web sites known as "logbooks" ("weblog") aimed at deleting a "weblog" "A" 51 from the list is presented in relation to FIG. preferred sites of a "weblog" "B" 50. In this embodiment, the command URLs (respectively the command URL "A" and the command URL "B") transmit and receive the requests and return the responses associated with the received requests. The processing related to the manipulation of the data is governed by server applications (respectively the server application "A" and the server application "B"). When the owner "B" wishes to delete 501 the "Blog" "A" 51 from his "bloglist", a "deleteBlogFromBlogList" action 503 is sent to the command URL "A" with the name of the owner "B" as parameter and the command URL "B". The BlogML document "B" is then updated by the server application "B" by deleting the node <blog> corresponding to the "Blog" "A" 51 of the node <in> of the node <bloglist> 502.

When receiving the action "deleteBlogFromBlogList" 511 by the command URL "A", the server application "A" verifies that the "blog""B" 50 has deleted the "blog""A" of the "Bloglist""B". For this, he will consult the BlogML "B" document by sending a "getBlogML" action 512 to the "B" command URL. The server application "B" receives this request 504 and returns 505 the BlogML "B" document. The server application "A" checks 513 that the node <blog> concerning it has been deleted. This check avoids "false deletion requests" sent by a third party.

If ever an anomaly is identified during this check 515, it returns 516 a response of type <CmdResp type = "ERROR" message = "The command failed" />.

Otherwise, it returns 516 a response <CmdResp type = "OK" />, the owner "A" is informed of its removal from the "Bloglist" "B" and the document BlogML "A" is updated 517 by the server application "A" by removing the previously created <blog> node from the <out> node node

<Bloglist>.

6.5.1.3 The different states of a "Blog" of a "bloglist". In relation to FIG. 6, we present the different possible states of the blogs appearing in the <in> node of the BlogML document: When a request for adding 60 of the "blog" "A" to the "bloglist" of the

"Blog" "B":

The state is initially marked as "Waiting" pending the response of the owner "A";

If the owner "A" does not accept the addition 62, then the status is marked 63 as "Refused". This information is transmitted to the "blog" "B" which removes the "blog" "A" from its "bloglist"; If the owner "A" accepts the addition 65, the state is then marked 66 as "Accepted". This information is transmitted to the "blog" "B" 67 for validation. The state then changes to "Active" 68; In relation to Figure 7, we present the different possible states of the blogs appearing in the <out> node of the BlogML document:

When the "blog" refuses to be referenced, the state is "Refused"71; When the "blog" accepts 72 to be referenced, the state is "Accepted" 73. 6.5.2 Obtaining general information from a "weblog". In relation to FIG. 8, an embodiment of FIG. obtaining the general information of a "weblog". In this embodiment, the command URLs (respectively the command URL "A" and command URL "B") issue and receive the requests and return the responses associated with the received requests. The processing related to the manipulation of the data is governed by server applications (respectively the server application "A" and the server application "B").

The obtaining 801 of the general information of a "weblog" "A" 81 by a "weblog" "B" 80 is done by sending 802 of the action "getBlogML" to the command URL "A" which reception 811. This command, through the server application "A", 812 returns an "http" response containing the BlogML document of the "blog" "A". After receiving 803 by the command URL "B", a device with an XML extractor can then extract 804 the general information of the "blog" "A" 81 contained in the <general> node. This information can be: - The title;

The URL of the blog;

The theme ;

The description ;

The date of creation; - the date of last modification;

The list of categories;

The URL of the RSS feed of the blog.

This information is then made available 805 of the server application "B". 6.5.3 Obtaining the latest articles published in a "weblog".

Two embodiments of obtaining by a weblog are described here.

"B" of the last articles published in a "weblog""A". In this embodiment, the command URLs (respectively the command URL "A" and the command URL "B") issue and receive the requests and return the responses associated with the received requests. Treatments related to the manipulation of data are governed by server applications (respectively the server application "A" and the server application "B").

For the owner of the "Blog" "B", at least two methods are then possible to be informed of the latest articles published in a "Blog" "A": via the RSS feed of the "Blog" "A"; via e-mail / SMS ("Short Message Service") / MMS ("Multimedia Message Service") notification when adding articles; 6.5.3.1 via the RSS feed of the "Blog" "A".

FIG. 9 shows an embodiment of obtaining, by a "weblog" "B" 90, the last articles published in a "weblog" "A" 91 by means of an RSS feed.

The obtaining 901 of the URL of the RSS feed of a "weblog" "A" 91 is done by sending 902 of the action "getBlogML" to the command URL "A". After reception

911 by the latter, the command returns a response 912 "http" containing the BlogML document of the "blog" "A" 91. After reception 903 by the command URL "B", a device with an XML extractor can then extract 904 the URL of the RSS feed of the "blog" "A" 91 contained in the <general> node.

The URL of the RSS feed of the "blog" "A" 91 is then made available 905 of the server application "B".

This URL is interpretable by many market tools (news aggregators, RSS feed readers) whose role is to poll periodically (every day, every hour ...) this type of flow to detect the publication new articles.

6.5.3.2 Email / SMS / MMS notification when adding articles. In connection with FIGS. 10, 11 and 12, an embodiment of obtaining the last articles published in a "weblog" by means of an email / SMS / MMS notification is presented. First, we detail the subscription to the notification service. Then we describe the unsubscription. Finally, we detail the actions taken when adding a new article to a "Blog"

Subscription to the notification: To be notified 1001 by mail / SMS / MMS when adding new articles in the "blog" "A" 101, the owner of the "blog" "B" 100 (via its server application "B" ") Can send the action 1003" subscribeToNotification "to the command URL" A ", including the type of notification (mail / SMS / MMS) and its email address or mobile number. The <blog> node corresponding to the "blog" "A" 110 in the document

BlogML "B" is then updated 1002 by the server application "B" by setting the value of the "notification" attribute of the <blog> node to "mail", "sms" or "mms". The XML example below details the structure of this node: <blogml>

<url> URL of "blog" A </ url> <urlCmd> "Command" URL of "blog" A </ urlCmd> </ blog> </ in>

</ bloglist> </ blogml>

When receiving the action "subscribeToNotification" 1011 by the command URL "A", the server application "A" verifies that the "blog""B" 100 is the requester of the subscription to the notification. . For this, he will consult the BlogML document "B" by sending 1012 a "getBlogML" action to the "B" command URL. The "B" command URL receives 1004 this request and returns 1005 its BlogML "B" document in response. After reception 1013 by the command URL "A", the server application "A" checks 1014 that the node <blog> concerning it has its attribute "notification" set to "mail", "sms" or "mms" . This check avoids "false requests for notification" sent by a third party. If an anomaly is identified 1015 during this check, it returns a response 1016 of type <CmdResp type = "ERROR" message = "The command failed"/>.

Otherwise, it returns a response 1016 of type <CmdResp type = "OK" />, and the server application "A" updates 1017 the document BlogML "A" by: setting to "mail", "sms" or " mms "the value of the" notification "attribute of the <blog> node corresponding to the" blog "" B "100; adding the attribute "notifParam" (filled with the email address or the mobile number of the owner "B") of the node <blog> corresponding to the "blog" "B" 100.

The XML example below details the structure of this node: <blogml>

<urlCmd> "Command" URL of the "blog" B </ urlCmd> </ blog> </ out> </ bloglist>

</ BlogML>

Thus, when new articles are added to the "blog" "A" 100, the server application "A" will have in the document BlogML "A" information necessary to notify the owner "B". Unsubscription of the notification;

To be unsubscribed 1101 from the notification, the owner of the "blog" "B" 110 must (via his server application "B") send 1103 the action "unsubscribeToNotification" to the command URL "A".

The node <blog> corresponding to the "blog""A" in the document "BlogML" B is then updated 1102 by the server application "B" by setting to "none" the value of the attribute "notification" of the node <blog>, as described in the following XML document example: <blogml> <bloglist><in><blog state≈ "active" notification = "none">

<name> Name of "blog" A </ name> <url> URL of "blog" A </ url> <urlCmd> "Command" URL of "blog" A </ urlCmd> </ blog> </ in>

</ bloglist> </ blogml>

Upon receiving the "unsubscribeToNotification" action 1111 by the "A" command URL, the "A" server application verifies that the "B" blog

110 is the plaintiff of the unsubscription to the notification. For this, he will consult the BlogML document "B" by sending 1112 an action "getBlogML" to the command URL "B". The command URL "B" receives this request 1104 and returns 1105 its BlogML "B" document in response. After reception 1113 by the command URL "A", the server application "A" verifies 1114 that the node <blog> concerning it has its attribute "notification" set to "none".

This check avoids "false requests" sent by a third party.

If an anomaly is identified 1115 during this check, it returns an answer 1116 of type <CmdResp type = "ERROR" message = "The command failed" />

Otherwise 1115, it returns a response 1116 of type <CmdResp type = "OK" />, and the server application "A" updates 1117 the document BlogML "A" by setting to "none" the value of the attribute "notification" and removing the "notifParam" attribute of the <blog> node corresponding to "blog" "B" 110, as described in the following XML document example: <blogml>

<Out>

<blog state = "accepted" notification = "none"> <name> Name of "blog" B </ name> <url> URL of "blog" B </ url> <urlCmd> URL "Command" of "blog" B </ urlCmd> </ blog>

</ Out> </ bloglist></blogml>

Adding an article:

When the owner "A" adds 1201 an article to his "blog A" 120, the server application "A" will automatically consult 1202 the document

BlogML "A" to identify the "blogs" of the <out> node of the <bloglist> node that have subscribed to the notification. For each "blog" that has requested to be notified, it extracts 1203 the notification method (mail, sms or mms) and the associated parameter (email address or mobile number). Then, it carries out the 1204 mail, sms or mms sending processes in order to inform the blogs to notify of the publication of a new article in the "blog" "A" 120.

Upon receipt of this notification 1211 by the "blog" "B" 121, the new article can be viewed 1212 in the "blog" "B" 121.

6.5.4 Obtain information about the owner of a "weblog". In connection with FIG. 13, an embodiment of obtaining by "weblog" "B" 130 information about the owner of a "weblog" "A" 131 is presented.

1301 obtaining information about the owner of a "weblog"

"A" 131 is done via the send 1302 of the action "getBlogML" to the command URL "A". Once received 1311 by the command URL "A", this command returns 1312 in return an "http" response containing the document

BlogML of the "blog" "A". After receiving 1303 by the command URL "B", a device with an XML extractor can then extract 1304 the owner information of the "blog" "A" 131 contained in the <owner> node. This information can be:

The full name of the owner; The name and / or the first name; The e-mail address; The mobile phone number; - The URL of a photo of the owner;

The FOAF document URL of the owner. This information is then made available 1305 of the server application "B".

6.5.5 Obtaining information about the weblogs of a weblog. In connection with FIG. 14, one embodiment of obtaining by the "weblog" "B" 140 information on the preferred "weblogs" of a "weblog" "A" 141 is presented.

Getting 1401 information about the favorite "weblogs" of a

"Weblog" "A" is done by sending 1402 of the action "getBlogML" to the command URL "A". Once received 1411 by the command URL "A", this command returns 1412 in return an "http" response containing the BlogML document of the "blog" "A" 141. After receipt 1403 by the command URL "B" , a device with an XML extractor can then extract

1404 the "blog" "A" information 141 contained in the <in> node of the <bloglist> node. For each "blog" in this list, the following information may be accessible:

The name of the "blog"; The URL of the "blog";

The command URL of the "blog" (which can give access to all the information of this "blog" via the action "getBlogML").

This information is then made available 1405 of the server application "B".

6.5.6 Obtaining information on "weblogs" referring to a "weblog". In connection with FIG. 15, an embodiment of obtaining by the "weblog" "B" 150 information about "weblogs" referring to a "weblog" "A" 151 is presented.

Obtaining 1501 information on "weblogs" referring to a "weblog""A" is done by sending 1502 of the action "getBlogML" to the command URL "A". Once received 1511 by the command URL "A", this command returns 1512 in return an "http" response containing the BlogML document of the "blog""A" 151. After reception 1503 by the command URL "B", a device equipped with an XML extractor can then retrieve 1504 the information from the "blog""A" 151 contained in the <out> node of the <bloglist> node. For each "blog" in this list, the following information may be accessible:

The name of the "blog";

The URL of the "blog";

This information is then made available 1505 of the server application "B".

It is clear that the invention is not limited to these descriptions of embodiments. The processing carried out by the command URLs, in particular, can be located on other servers and / or be centralized.

In yet another embodiment, it is also possible that the XML files containing the specific information data of the websites are also located on other servers and / or centralized to ensure, for example, the confidentiality of certain data present in these files.

Claims

1. Data exchange system, between at least one first web site, hosted on a first server and at least one second web site, hosted on a second server, said data being conveyed through a network of communication characterized in that said data are informational data specific to said at least first and / or said at least second website, and in that said system comprises: at least one descriptive support of said specific information data associated with said at least one first site web and / or audit at least one second website; command processing means for exchanging at least some of said specific information data, between said at least first and at least second web sites, said commands originating from one of said web sites participating in said system to another site web participant in this system.

2. Data exchange system according to claim 1, characterized in that said specific information data belong to the group comprising at least: general data relating to said website; specific data relating to the owner of the said website; a list of websites linked to said website also containing types of relationship maintained with said website; a list of persons related to the owner of said website also containing types of relationship maintained with the owner of said website.

3. Data exchange system according to claim 2, characterized in that said types of relationship maintained with said website belong to the group comprising at least: - preferred website; website to avoid; list of websites known as "logbooks"("bloglist"); friends list.

4. Data exchange system according to any one of claims 1 to 3, characterized in that said command processing means are accessible from said web sites of said network.

5. Data exchange system according to claim 4, characterized in that said command processing means are in the form of a URL (Uniform Resource Locator) command.

6. Data exchange system according to claim 5, characterized in that said command URL accepts information request requests and / or information update requests and provides responses and / or data in accordance with the present invention. function of said requests.

7. Data exchange system according to claim 6, characterized in that said requests for information request and said information update requests are composed of: a type of processing to be performed; at least one parameter necessary for accomplishing said type of treatment.

8. Data exchange system according to claim 7, characterized in that said types of processing to be carried out belong to the group comprising:

Adding said first website to a list of preferred sites of said second website;

Acceptance by said second website of an addition of said second website to a list of preferred websites of said first website; Refusal by said second website of adding said second website to a list of preferred sites of said first website; - Retrieving an information XML document associated with a website; Subscribing said first website to at least one notification of adding at least one new information to said second website;

Unsubscribing from said first website to said adding notification;

Recovering by said first website of at least one information contained in said descriptive medium associated with said second website;

9. Data exchange system according to any one of claims 7 and 8, characterized in that said at least one parameter necessary for the completion of said type of treatment belongs to the group comprising:

An identifier of an owner of said first and / or second website;

Said command URL of said first and / or said second website;

One type of notification

At least one notification parameter;

An identifier of the at least one information to be retrieved.

10. Data exchange system according to any one of claims 6 to 9, characterized in that said responses are HTTP format responses containing an XML document indicating a failure or success or said at least one information to recover.

11. System according to any one of claims 1 to 10 characterized in that each of said web sites is selectively associated with one of said descriptive media comprising said informational data specific to said corresponding web site.

12. A method for exchanging data, between at least one first web site, hosted on a first server and at least one second web site, hosted on a second server, by means of a communication network, characterized in that the said data being informational data specific to said at least first and / or said at least second web site, said method comprises a step of transmitting at least one command for exchanging at least some of said specific information data, by said at least first website to a command URL of said second website.

13. Server for exchanging data in a data exchange system, between at least one first web site, hosted on a first server and at least one second web site, hosted on a second server, by means of a network communication device, characterized in that said data being informational data specific to said at least first and / or said at least second web site, it hosts means for transmitting commands for exchanging at least some of said specific information data, by said at least one first website to a command URL of said second website.

14. Computer program product for exchanging data, between at least one first web site, hosted on a first server and at least one second web site, hosted on a second server, by means of a communication network, downloadable from a communication network and / or stored on a computer readable medium and / or executable by a microprocessor, characterized in that said data being informational data specific to said at least first and / or said at least second website, said program includes program code instructions for implementing a step of issuing at least one command to exchange at least some of said specific information data, said at least first website to a URL of ordering said second website.

15. A method of exchanging data, between at least one first web site, hosted on a first server and at least one second web site, hosted on a second server, by means of a communication network, characterized in that said data being informational data specific to said at least one first and / or said at least one second web site, said method comprises a step of processing at least one exchange command of at least some of said specific information data, received on a command URL of said at least one second website.

16. Server for exchanging data in a data exchange system, between at least one first web site, hosted on a first server and at least one a second website, hosted on a second server, by means of a communication network, characterized in that said data being informational data specific to said at least one first and / or said at least one second web site, it hosts means for processing at least one exchange command of at least some of said specific information data, received on a command URL of said at least one second website.

17. Computer program product for exchanging data, between at least one first web site, hosted on a first server and at least one second web site, hosted on a second server, by means of a communication network, downloadable from a communication network and / or stored on a computer readable medium and / or executable by a microprocessor, characterized in that said data being informational data specific to said at least one first and / or said at least one second web site said program comprises program code instructions for implementing a step of processing at least one exchange command of at least some of said specific information data, received on a command URL of said at least one second website.