WO2012144953A1

WO2012144953A1 - Automated publication system with permission request and verification

Info

Publication number: WO2012144953A1
Application number: PCT/SG2012/000120
Authority: WO
Inventors: Dennis Yar King Him
Original assignee: Dennis Yar King Him
Priority date: 2011-04-20
Filing date: 2012-04-05
Publication date: 2012-10-26
Also published as: SG185154A1

Abstract

This invention will enable the automated seeking and verification of permission for digital network users to automate the publishing of content that he has generated in his emails, forum postings, blogs, blog comments, and in other online medium and websites. Many of his content would include content from one or more Secondary Owners such as a conversation between the Primary User and Secondary Owner in an email. The Secondary Owner would be contacted for permission for his content to be published, and invited to publish his own content.

Description

Automated Publication System with Permission Request and

Verification

BACKGROUND OF THE INVENTION

In this day and age, the Internet, mobile phones, notebooks, email and mobile computing have become synonymous with everyday life. Many of us maintain at least a few email accounts, memberships at online websites like Facebook and Twitter, and accounts at various online forums. Some of us run our own blogs and even publish online articles and ebooks. We have our personal photo albums, and perhaps even professional portfolios, hosted at Flickr with videos of our child's first word at Youtube. And we probably have at least one personal computer at work, and one at home, and one notebook that we carry around.

In addition, many of our online conversations, blogs, forum posts, articles and comments at various online sites contain valuable knowledge and insights which some of us would like to share with the world. There is currently no easy way to bring together all these disparate snippets of information into a single integrated medium from which we can browse and choose to publish if we wish.

SUMMARY OF THE INVENTION

DETAILED DESCRIPTION OF THE INVENTION

Introduction

1. This invention is an Information Publication System with Automated Permission Request and Verification 100.

2. The description below describes a possible implementation of our invention. The

description merely serves to illustrate and aid in the understanding of our invention and is not the only way our invention can or will be implemented. ¹

3. As shown in Figure 1 , the Information Publication System with Automated Permission Request and Verification or Our System 100 comprises the following:

a. A User Management System 200

b. An Information Aggregator System 300

c. An Information Selector System 400 d. An Automated Permission Seeking and Verification System 500

e. An Information Publication System 800

The User Management System 200

4. In Figure 2, the Primary User 205 registers with Our System 100 at 210. The Primary User 205 can access Our System 100 through Our Service 215, which can be a website using our software or a piece of software installed on the Primary User's 205 computer or a hardware device with our software built in.

5. When registering, the Primary User 205 is presented with the Registration Menu 9000 using which he enters his name, email address and other profile information.

6. Once the Primary User 205 has entered all his profile information and Our Service 215 has accepted the Primary User's 205 profile information, his profile information is stored into the Primary User Database 1000 as shown in Figure 8.

7. After registration, the Primary User 205 can login to his account at 220. Upon login at

225, the Primary User 205 is presented with the Account Menu 9001, which gives him an overview of his account, and includes the number of unread messages, the number of items awaiting approval and the number of items published.

The Information Aggregator System 300

8. From the Account Menu 9001, the Primary User 205 can access the Item Menu 9002 where he is presented with a list of Information Resources from which there are informational items that he can publish 305. This list includes but is not limited to common websites like social networking sites, forums, blogging sites, email sites, article directories, ftp servers and other types of sites in which content can be generated and stored, and offline resources like the email client on his computer.

The Primary User 205 can also input his own Information Resources at 310. The Information Resources that he can input includes but is not limited to social networking sites, forums, blogging sites, email sites, article directories, ftp servers and other types of sites in which content can be generated and stored, and offline resources like his email client and computer folders on his computer.

For the list of Information Resources presented and entered, the Primary User 205 enters his user ID, password and the update frequency for each of the Information Resources at 315.

Once the Primary User 205 has entered the required information, we have a pool of customized scrapers to scrape information from the Information Resources at 320.

At 325, the scraped information is then processed by data extractors to extract the informational items relevant to the Primary User 205. The relevant items can be pure text, data, graphics, audio, video, or any number of other formats in which information can be stored.

At 330, the extracted informational items relevant to the Primary User 205 will be stored in the Information Database 4000. The Information Selector System 400

14. At 405, a browser/software component/hardware with a software component enables the Primary User 205 to view all the items stored in the Information Database 4000 sorted by:

a. Date

b. Location

c. Type

d. User

e. Subject

f. And others

15. The Primary User 205 can select any or all of his items for publication at 410.

16. All items selected for publication is checked to make sure that there is no copyright infringement or other issues 415.

17. When the Primary User 205 selects the items that he wants to make public, he can select which group of people he wants to share the items with 420. He can group people in the following way:

a. Email contacts

b. Friends

c. Family

d. Close friends

e. Everybody

f. And others 18. At 425, all items selected for publication will be uploaded to a Pending Publication Database 5000.

The Automatic Permission Seeking and Verification System 500

19. The Automatic Permission Seeking And Verification System 500 comprises the

following 2 systems:

a. The Automated Permission Request and Verification, and Secondary Owner Permission System 600

b. The Permission Verification System 700

The Automated Permission Request and Verification, and Secondary Owner Permission System 600

20. The items that the Primary User 205 selects for publication will not only be content generated by him, but generated in collaboration or along with one or more other owners (also known as Secondary Owners). An example would be a thread in a forum in which many contributed.

1. At 605, the Pending Publication Database 5000 is constantly scanned for items that are awaiting publication.

2. At 610, once an item that is awaiting publication is found, a check is done to see if

permission is needed from one or more Secondary Owners before publication. If no permission is needed 611, the Pending Publication Database 5000 will be updated at 665. At 615, if permission is needed from a Secondary Owner 612, the Secondary Owner Database 2000 is checked to see if this Secondary Owner has been contacted by us before.

If the Secondary Owner has been contacted before 616, a check if done on the history of our communication with the Secondary Owner and his previous responses 620 and at 625, based on the history, a decision is made on whether the Secondary Owner should be contacted.

If it is decided that the Secondary Owner should not be contacted 626, the Pending Publication Database 5000 will be updated at 665.

If it is decided to contact the Secondary Owner 627, the Secondary Owner Database 2000 will be checked to see if there are multiple ways of getting in touch with the Secondary Owner at 630.

If there are a few ways of contacting the Secondary Owner 631, the communication channel that will least inconvenience the Secondary Owner and offers the best chance of a positive response will be chosen at 635.

At 640, a communication using the optimum communication channel is sent to the Secondary Owner.

A communication to the Secondary Owner can be an email 9004, an IM message, a forum post 9005 or a blog post. Each communication will include a link to our website where they can enter their permission 9003. If allowed in the communication channel, the Secondary Owners can also simply reply to give their permission. When the Secondary Owner is asked for permission to publish, he is also able to choose from which groups of people he wants to publish the item to. He can group people in the following way:

a. Email contacts

b. Friends

c. Family

d. Close friends

e. Everybody

f. And others

The Secondary Owners will also be able to change their permission setting at any time. At 645, regular checks are made on the various communication channels for a response from the Secondary Owner.

If there is a response from the Secondary Owner 646, a check will be done to make sure the response is complete 650.

If the response is complete 651, the Secondary Owner Database 2000 will be updated at 655, followed by the Pending Publication Database 5000 at 665.

If the response from the Secondary Owner is incomplete 652, the Secondary Owner Database 2000 is updated accordingly 660.

If, after a certain period of time, no response has been received from the Secondary Owner, it is assumed that there is no response from the Secondary Owner 647 and the Secondary Owner Database is updated accordingly 660. The Permission Verification System 700

37. The Pending Publication Database 5000 is scanned for items that are ready to be

published 705.

38. Items that does not need the permission of any Secondary Owners, or items in which all the Secondary Owners have responded and given their permission is considered ready to be published.

39. At 710, items that are ready to be published will be moved from the Pending Publication Database 5000 to the Publication Database 6000 and published with the most restrictive permission setting of the Primary User 205 and the Secondary Owners.

40. A notification will be sent out to the Primary User 205 and the Secondary Owners about the publication of the item 715.

41. A check is made at 720 on whether there are any Permitted Users to be notified. If there is 721, a notification is sent to them 725.

42. At 730, the Permitted User's response is monitored and stored into the Permitted User Database 3000.

The Information Publication System 800

43. In Figure 7, the User 805, who can be a Primary User 205, or a Secondary Owner, or a Permitted User, or an Internet user, can use Our System 100 through a search browser 815 to search the Publication Database 6000 for items open to him 820. The User can use Our System 100 with or without logging in 810. 44. In addition to searching and browsing the Publication Database 6000, the User 805 can also set an alert for new items pertaining to his needs 825.

45. If the User 805 is not a Primary User 205, he will be invited to join Our System 100 as a Primary User 205 to enjoy the enhanced features of Our System 100. If they agree to join, they will become another Primary User 205.

46. As it is with the first Primary User 205, they will be given a list of Information Resources from which they can choose to publish.

DESCRIPTION OF THE DRAWINGS

The description below describes a possible implementation of our invention. The description merely serves to illustrate and aid in the understanding of our invention and is not the only way our invention can or will be implemented.

Figure 1: Information Publication System with Automated Permission Request and Verification

100 Information Publication System with Automated Permission Request and

Verification. This is the complete system that comprises: a. The User Management System 200 b. The Information Aggregator System 300 c. The Information Selector System 400 d. The Automatic Permission Seeking and Verification System 500 e. Information Publication System 800

200 User Management System. This system manages the registration, logging in and account of the Primary User 205.

300 Information Aggregator System. This system manages the items that the Primary User 205 wants to publish.

400 Information Selector System. This system allows the Primary User 205 to select items to be published and check the items for copyright and other issues.

500 Automatic Permission Seeking and Verification System. This system comprises the following systems: a. The Automated Permission Request and Verification, and Secondary Owner Permission System b. The Permission Verification System

600 The Automated Permission Request and Verification, and Secondary Owner Permission System. This system scans the Pending Publication Database 5000, sends and receives communication from the Secondary Owners and updates the Secondary Owner

Database 2000 and the Pending Publication Database 5000. 700 The Permission Verification System. This system verifies that permission has been given, sends items to the Publication Database 6000 to be published and informs the relevant parties of the publication.

800 Information Publication System. This system lets the User 805 search and browse the Publication Database 6000.

Figure 2: The User Management System

205 Primary User. The Primary User 205 is a person registered with Our System 100, who is entitled to use the publication and other features of Our System 100.

210 User Registration. Performs the registration of the Primary User 205.

215 Our Service: Website or Software or Hardware with software. Our Service 215 is the interface through which Our System 100 interacts with the Primary Users 205, Secondary Owners, Permitted Users, Internet users, computer servers, websites, etc.

220 Log-in. Allows the Primary User 205 to log-in to Our System 100.

225 User shown status of items to be published and published items. The Primary User 205 is shown various details of his account. Figure 3: The Information Aggregator System

305 View locations from which to get items to publish. The Primary User 205 is given a list of locations from which he can get items to publish.

310 Enter locations from which to get items to publish. The Primary User 205 can enter a list of locations from which he can get items to publish.

315 Enter ID, password and update frequency for each location. The Primary User 205 enters his ID, password and the update frequency for each location.

320 Scrape / Use API to scrape information. Various techniques are used to scrape information from the locations that the Primary User 205 wants to get informational items for publication.

325 Use data extractors to extract information. The information scraped is processed for items relevant to the Primary User 205.

330 Store to Information Database. The items scraped are stored to the Information Database 4000. Figure 4: Information Selector System

405 View items ready to be published. The Primary User 205 can view the items stored in the Information Database 4000.

410 Select item to publish. The Primary User 205 will be able to select which items he wants published.

415 Does item have copyright or other issues? Before the item selected for publication by the Primary User 205 is sent to the Pending Publication Database 5000, a check is done to make sure that there is no copyright violation or other issues.

416 Yes. The item selected by the Primary User 205 has copyright violation or other issues and cannot be published.

417 No. The item selected by the Primary User 205 does not have copyright violation or other issues.

420 Select who can view. The Primary User 205 can select who is able to view the items that he has selected for publication.

425 Store to Pending Publication Database. The item is stored to the Pending Publication

Database 5000 to be further processed before publication. Figure 5: Automated Permission Request and Verification, and Secondary Owner

Permission System

600 Automated Permission Request and Verification, and Secondary Owner Permission System. This system scans the Pending Publication Database 5000, sends and receives communication from the Secondary Owners and updates the Publication Database 6000.

605 Scan Pending Publication Database for items awaiting publication. The Pending Publication Database 5000 is scanned to check for items awaiting publication.

610 Does item need permission from Secondary Owner? Check if the item awaiting publication needs permission from any Secondary Owners.

61 1 No. The item awaiting publication does not need permission from any Secondary Owners.

612 Yes. The item awaiting publication needs permission from Secondary Owners.

615 Has Secondary Owner been contacted before? The Secondary Owner Database 2000 is checked to see if the Secondary Owner has been contacted by us before.

616 Yes. We have contacted the Secondary Owner before.

617 No. We have not contacted the Secondary Owner before. 620 Check the history of communication with Secondary Owner. Since we have contacted the Secondary Owner before, there will be a history of that communication in the Secondary Owner Database 2000. The history will include the following:

• The number of times he has been contacted.

• The number of times he has responded.

• The number of times he has given a positive response.

• The date of our last communication.

625 Should Secondary Owner be contacted? From the history of the communication with the Secondary Owner, a decision will be made as to whether the Secondary Owner should be contacted again.

626 No. The Secondary Owner should not be contacted again.

627 Yes. The Secondary Owner can be contacted.

630 Are there multiple ways of contacting Secondary Owner? Determine if there are multiple ways that the Secondary Owner can be contacted.

631 Yes. There are multiple ways that the Secondary Owner can be contacted.

632 No. There is only one way to contact the Secondary Owner.

635 Check for the best way to contact Secondary Owner. Check for the best way to contact the Secondary Owner to minimize the inconvenience to the Secondary Owner and to maximize the possibility of a positive response. 640 Send communication to Secondary Owner. A communication will be sent to the Secondary Owner using the best communication channel. Every communication will include a link that the Secondary Owner can click to visit our website for more information and to indicate his permission. If it is possible for the communication channel, the Secondary Owner will also be able to just reply to the communication to give his permission.

645 Has Secondary Owner responded? Frequent checks will be made to see if the

Secondary Owner has responded to our communication whether through our website or through other communication channels. If the Secondary Owner did not respond after a certain period of time, this fact will be updated in the Secondary Owner Database 2000.

646 Yes. The Secondary Owner has responded to our communication.

647 No. The Secondary Owner has not responded to our communication.

650 Is Secondary Owner's response complete? Check if the Secondary Owner's response is complete. If it is not, this fact will be updated in the Secondary Owner Database 2000.

651 Yes. The response of the Secondary Owner is complete. 652. No. The response of the Secondary Owner is incomplete.

655 Update Secondary Owner Database. The Secondary Owner Database 2000 is updated with the details of the latest communication with the Secondary Owner.

660 Update Secondary Owner Database. The Secondary Owner Database 2000 is updated with the details of the latest communication with the Secondary Owner, or his lack of response. 665 Update Pending Publication Database. The Pending Publications Database 5000 is updated with the details of the Secondary Owner's communication.

Figure 6; Permission Verification System

700 The Permission Verification System. This system verifies that permission has been given, sends items to the Publication Database 6000 to be published and informs the relevant parties of the publication.

705 Scan Pending Publication Database for items ready for publication. The Pending Publication Database 5000 is scanned for items that are ready to be published.

710 Publish items with the most restrictive permission. Items ready to be published are sent to the Publication Database 6000. Each of the items published is published with the most restrictive of the permissions granted by the Primary User 205 and associated Secondary Owners.

715 Notify Primary User and Secondary Owners. The Primary User 205 and Secondary Owners are notified of the publication of the item.

720 Should any Permitted Users be notified? A check is done with the Permitted User Database 3000 to see if there are any Permitted Users that should be notified of the publication of the item.

721 Yes. There are Permitted Users that should be notified.

722 No. There are no Permitted Users that should be notified. 725 Send notification to Permitted Users. Notifications are sent to the Permitted Users.

730 Monitor response from Permitted Users and update Permitted User Database. The response of the Permitted Users, if any, are monitored and updated to the Permitted User Database 3000 for future reference.

Figure 7: Information Publication System

805 User. This User 805 can be a Primary User 205, a Secondary Owner, a Permitted User or simply an Internet surfer.

810 User can search with or without log-in. The User 805 can search the Publication Database 6000 with or without logging in.

815 Search browser. A browser is provided to search and browse the items in the

Publication Database 6000.

820 Search / Browse Publication Database for published items. Using the search browser, the User 805 can search and browse the items open to him in the Publication Database 6000.

825 Set alert for new items. If the User 805 can't find what he is looking for or would like to be updated when new items are published or when published items are updated, he can set an alert so that our system will notify him when new items are published. Figure 8; Primary User Database

1000 Primary User Database. This is the database that stores the profile information of all the Primary Users 205.

1001 Database Fields. The items in this column are the fields of the Primary User Database 1000.

1002 Record 1. The items in this column are an example of what an actual record in the Primary User Database 1000 can look like.

1003 Record2. Similar to Record 1, the items in this column are an example of what an actual record in the Primary User Database 1000 can look like.

1004 First Name. This is the first name of the Primary User 205.

1005 Last Name. This is the last name of the Primary User 205.

1006 Primary Email Address. This is the main email address of the Primary User 205.

1007 Secondary Email Address. This is a secondary or backup email address that can be used to contact the Primary User 205 if he is not contactable through the main or primary email address.

1008 Username. This is the Primary User's 205 user ID that he will use to login to Our System 100.

1009 Password. This is the Primary User's 205 password for accessing Our System 100. 1010 Challenge Question. Our System 100 has 10 predefined challenge questions. This is used in case the Primary User 205 forgets his password. During registration, the Primary User 205 would have selected a challenge question, and this field stores the number of the question he selected.

101 1 Challenge Answer. This is the answer supplied by the Primary User 205 to the challenge question that he selected.

Figure 9: Secondary Owner Database

2000 Secondary Owner Database. This database stores the profile details of the Secondary Owner/s of the information that the Primary Users 205 choose to publish. This database also stores the history of the Secondary Owner/s contacts with us.

2001 Database Fields. The items in this column are the fields of the Secondary Owner Database 2000.

2002 Recordl. The items in this column are an example of what an actual record in the Secondary Owner Database 2000 can look like.

2003 Record2. Similar to Recordl, the items in this column are an example of what an actual record in the Secondary Owner Database 2000 can look like.

2004 Reference No. This is a unique number used to identify a Secondary Owner.

2005 First Name. This is the first name of the Secondary Owner. If his first name is unknown, this field will be left blank. 2006 Last Name. This is the last name of the Secondary Owner. If his last name is unknown, this field will be left blank.

2007 Username. This is the username for the Secondary Owner for the item no listed below. This field will be left blank if his username is unknown or not relevant.

2008 Email Address. This is the email address of the Secondary Owner. If his email address is unknown, this field will be left blank.

2009 Primary User. This is the username of the Primary User 205 who is requesting the publication of the item.

2010 Item No. This is the unique number that identifies the item that the Secondary Owner is to be asked for permission to publish.

201 1 No of Previous Contacts. The number of times we had contacted the Secondary Owner for his permission.

2012 No of Responses. The number of times the Secondary Owner has responded to our contact.

2013 No of Positive Responses. The number of times the Secondary Owner has given his permission to publish.

2014 Date of Last Contact. This is the date that we have last contacted him.

Fieure 10: Permitted User Database 3000 Permitted User Database. This database is a database of users who have been permitted by the Primary User 205 and Secondary Owners access to items that are published.

3001 Database Fields. The items in this column are the fields of the Permitted User Database 3000.

3002 Recordl. The items in this column are an example of what an actual record in the Permitted User Database 3000 can look like.

3003 Record2. Similar to Recordl, the items in this column are an example of what an actual record in the Permitted User Database 3000 can look like.

3004 Permitted User No. This is a unique number identifying the Permitted User.

3005 First Name. This is the first name of the Permitted User.

3006 Last Name. This is the last name of the Permitted User.

3007 Email Address. This is the email address of the Permitted User.

3008 Date of Last Contact. This is the date of the last time we contacted the Permitted User.

3009 Status. This field stores the status of the Permitted User, such as whether the Permitted User has asked not to be contacted again.

Figure 11: Information Database

4000 Information Database. This database stores the extracted informational items for the

Primary User 205. Each Primary User 205 can have a dedicated Information Database 4000. 4001 Database Fields. The items in this column are the fields of the Information Database 4000.

4002 Recordl. The items in this column are an example of what an actual record in the Information Database 4000 can look like.

4003 Record2. Similar to Recordl, the items in this column are an example of what an actual record in the Information Database 4000 can look like.

4004 Item No. This is a unique number that identifies the item.

4005 Location of Item. This field identifies where the item is located.

4006 Filename. This is the filename of the item.

4007 Source Location. This is the source from which the item is copied from. Note that this can be a web location, an email client, or even a computer folder.

4008 Source Location Info 1. Additional information needed to identify the item at the source location. If this is not needed, this field is left blank.

4009 Source Location Info 2. Additional information needed to identify the item at the source location. If this is not needed, this field is left blank.

4010 Pub Status. This is the publication status of the item.

Figure 12: Pending Publication Database 5000 Pending Publication Database. This database stores the details of items marked for publication but have not yet been published.

5001 Database Fields. The items in this column are the fields of the Pending Publication Database 5000.

5002 Recordl. The items in this column are an example of what an actual record in the Pending Publication Database 5000 can look like.

5003 Record2. Similar to Recordl, the items in this column are an example of what an actual record in the Pending Publication Database 5000 can look like.

5004 Item No. This is a unique number that identifies the item.

5005 Root Location of Item. This is the root folder for the item.

5006 Location of Item. This is the location at which the item can be found.

5007 Filename. This is the filename for the item.

5008 Secondary Owners. This is a list of Secondary Owners whose permission is needed before the item can be published.

Figure 13: Publication Database

6000 Publication Database. This database stores the details of items that are published.

6001 Database Fields. The items in this column are the fields of the Publication Database 6000. 6002 Recordl. The items in this column are an example of what an actual record in the Publication Database 6000 can look like.

6003 Record2. Similar to Recordl, the items in this column are an example of what an actual record in the Publication Database 6000 can look like.

6004 Item No. This is a unique number that identifies the item.

6005 Root Location of Item. This is the root folder for the item.

6006 Location of Item. This is the location at which the item can be found.

6007 Filename. This is the filename for the item.

6008 Permission. This field lists who is allowed to view the item.

Figure 14: Registration Menu

9000 Registration Menu. This is the menu with which a Primary User 205 registers.

Figure 15: Account Menu

9001 Account Menu. This menu presents the Primary User 205 with the details of his account.

Figure 16: Item Menu 9002 Item Menu. The Primary User 205 specifies from which locations he wants to get items to be published, and his user ID, password and update frequency for each location.

Figure 17: Secondary Owner Approval

9003 Secondary Owner Approval. The Secondary Owner can give his permission to publish from here.

Figure 18: Email Communication to Secondary Owner

9004 Email Communication to Secondary Owner. An example of an email asking the Secondary Owner for permission to publish.

Figure 19: Forum Communication to Secondary Owner

9005 Forum Communication to Secondary Owner. An example of a forum post asking the Secondary Owner for permission to publish.

Claims

A system and method of publishing one or multiple pieces of information wherein each information is collected from one or multiple information sources; and each information can be optionally displayed; and each information can be selected for publication; and verify if all owners of the information selected has granted permission for publication; and if all owners have not granted permission, contact owners whose permission is needed for their permission; and monitor one or multiple information sources for the response from owners; and publish information if all owners have granted permission

The system of claim 1 wherein the system can be implemented as one or multiple software programs running on one or multiple computers.

The system of claim 1 wherein the system can be implemented as one or multiple dedicated hardware devices.

The method of claim 1 wherein the identification of information sources to be collected from can be indicated by user action or can be automated.

5. The method of claim 1 wherein the collection of information includes one or multiple scrapers for collecting the information.

6. The method of claim 1 wherein the source of the information can include email clients, web based email, ftp, websites, social networking sites, blogs and forums.

7. The method of claim 1 wherein the information collected can be stored in a

backup location.

8. The method of claim 7 wherein the information stored can be updated to a more recent version from the original information source.

9. The method of claim 8 wherein the period of updating of information can be indicated by user action or automated.

10. The method of claim 1 wherein the selection of information to be published can be indicated by user action or automated.

11. The method of claim 1 wherein owners can be contacted for their permission through a forum post.

12. The method of claim 1 wherein owners can be contacted for their permission through a comment in a blog.

13. The method of claim 1 wherein owners can be contacted for their permission through an email.

14. The method of claim 1 wherein owners can be contacted for their permission through a website private message.

15. The method of claim 1 1, 12, 13 and 14 wherein the other owners can be contacted individually or collectively.

16. The method of claim 1 wherein the response from owners can be a reply to a forum post.

17. The method of claim 1 wherein the response from owners can be a reply to a blog comment.

18. The method of claim 1 wherein the response from owners can be a reply to an email.

19. The method of claim 1 wherein the response from owners can be a reply to a private message on a website.

20. The method of claim 1 wherein the permission can be for part of the message.

21. The method of claim 1 wherein the owners can add personal remarks or

comments.

22. The method of claim 1 wherein the permission granted by owners can be limited to a select group of users.

23. The method of claim 1 wherein the information published may be accessible by a limited group of users.

24. A system and method of publishing one or multiple pieces of information wherein each information can be optionally displayed; and each information can be selected for publication; and verify if all owners of the information selected has granted permission for publication; and if all owners have not granted permission, contact owners whose permission is needed for their permission; and monitor one or multiple information sources for the response from owners; and publish information if all owners have granted permission

25. The system of claim 24 wherein the system can be implemented as one or

multiple software programs running on one or multiple computers.

26. The system of claim 24 wherein the system can be implemented as one or

multiple dedicated hardware devices.

27. The method of claim 24 wherein the selection of information to be published can be indicated by user action or automated.

28. The method of claim 24 wherein owners can be contacted for their permission through a forum post.

29. The method of claim 24 wherein owners can be contacted for their permission through a comment in a blog.

30. The method of claim 24 wherein owners can be contacted for their permission through an email.

31. The method of claim 24 wherein owners can be contacted for their permission through a website private message.

32. The method of claim 28, 29, 30 and 31 wherein the other owners can be contacted individually or collectively.

33. The method of claim 24 wherein the response from owners can be a reply to a forum post.

34. The method of claim 24 wherein the response from owners can be a reply to a blog comment.

35. The method of claim 24 wherein the response from owners can be a reply to an email.

36. The method of claim 24 wherein the response from owners can be a reply to a" private message on a website.

37. The method of claim 24 wherein the permission can be for part of the message.

38. The method of claim 24 wherein the owners can add personal remarks or

comments.

39. The method of claim 24 wherein the permission granted by owners can be limited to a select group of users.

40. The method of claim 24 wherein the information published may be accessible by a limited group of users.