TWI566110B - Matter sharing method - Google Patents

Description

Method of sharing elements

The method of the present invention relates to the field of sharing of elements, and in particular to the field of calculation of the propagation relationship parameters of the elements being shared.

Recently, the rapid growth of social networking sites such as Twitter® and Facebook® has created a new trend in Internet usage. In general, social networking sites are often associated with services and tools that help users maintain and expand their circle of friends to expand existing relationships. Since social networking sites are places where many people spend most of their time on the Internet, social networking sites are becoming the main entry point for online activities. At the same time, social networking sites are also the center for sharing information such as website links, multimedia files, music, and more.

When people create fan pages or share information on social networking sites based on business operations, market research, promotion of popularity, or brand image enhancement, they hope to attract more attention and bring individuals or organizations themselves. Various derivative values. The value of derivative value is affected by many indicators. The point-to-point rate of the same platform or different platforms, the specific time interval or the point-to-point rate of a specific location, the propagation path and the key communication communicator are the more important indicators. When a fan's page or shared information is more frequently clicked and shared, the wider the scope and the longer the communication, the more the topics, content and services it covers are closer to the user's preferences, and the derivative value. Also higher.

The person who most wants to get various communication relationship parameters to improve the transmission rate is necessarily the fan page creator or the information sharer itself. However, fans of existing social networking sites The page creator can only know how many people track their fan pages and the number of people tracking in a fixed time interval, and the news sharer can only know the number of times the information provided on a particular platform has been transferred to that particular platform. . Users can't get various communication relationship parameters through existing information, so they can not only know the communication trends and key communicators, but also can't grasp the market heat and direction.

Therefore, how to statistically communicate the relationship parameters has become a hot research topic in the market today. For example, U.S. Patent Publication No. 8190711 discloses a method for statistically communicating the relationship parameters. The method of the statistical communication relationship parameter disclosed by the user first generates a path link information for obtaining the information when the user provides a message on the Internet, and then provides the path link information when the user chooses to share the information. A shared person, and when the shareee opens the path link information to obtain the information, modifies the route link information, and when the shareee chooses to share the information, provides the modified path link information to other Sharers to track and count the dissemination of this information.

However, by the above method, only the total spot rate of the information and the click rate brought by different sharers can be known, and other propagation relationship parameters cannot be counted. Furthermore, when the information is shared to different platforms, such as being shared to Facebook® from Twitter® and then being transferred to Facebook®, the Twitter® server is not aware that the information is being shared by Facebook® users. It is even more difficult to modify the path link information, so that it is impossible to continue tracking and statistics on the dissemination of the information.

In addition, as shown in FIG. 1C of U.S. Patent Publication No. 20140149888, a statistical chart showing the number of people browsing, sharing or clicking on a user's shared information within a specific time interval is disclosed, but the above patent does not. Explain how to count various communication relationship parameters and still be limited to the same social networking site, such as statistics on browsing, sharing, or clicks within Facebook®.

Further, as shown in FIG. 4 of U.S. Patent Publication No. 20,140, 129, 558, which discloses a statistical chart for visualizing the state of propagation of information relating to the same event over a specific time interval, U.S. Patent No. 8,867,937 discloses A user interface for displaying hot events in a specific geographic location, as shown in Figure 1J, but the above patents also fail to disclose how to aggregate various propagation relationship parameters and apply only to the integration and analysis of events within a single or specific server. .

In summary, the existing social network website users lack appropriate methods to obtain various communication relationship parameters, and it is even more difficult to collect various communication relationship parameters across platforms. Therefore, how to provide a method for statistically calculating various propagation relationship parameters across platforms becomes important. Question.

It is an object of the present invention to provide a method for generating a shared element of a propagation relationship parameter by generating a record table.

In a preferred embodiment, the present invention provides a method for sharing an element, comprising: receiving an element via a source message, wherein the source message includes a message for obtaining a first record table corresponding to one of the elements; The destination message transmits the element, wherein the destination message includes a message for obtaining a second record table corresponding to the element; and calculating the element according to at least one of the first record table and the second record table A propagation relationship parameter.

In a preferred embodiment, the source message is a first path link information (URI), and the destination message is a second path link information.

In a preferred embodiment, the first path connection information and the second path connection information comprise a Hypertext Transfer Protocol (HTTP) path link information, a File Transfer Protocol (FTP) path link information, and a local file ( Local file) At least one of the link information.

In a preferred embodiment, the source message includes a message for obtaining a projectable space instance and the first record table, the destination message includes a space entity for obtaining the projectable and The message of the second record table, wherein the projectable spatial entity is used to create a projected workspace.

In a preferred embodiment, the method of sharing elements further includes the step of: interpreting the projectable spatial entity using a projection to execute the projected workspace.

In a preferred embodiment, the projectable spatial real system is an object, an extensible markup language (XML) file, or a structured language or a structured protocol (structured) Protocol) An entity generated by an instance.

In a preferred embodiment, the first record table includes a first identification code corresponding to one of the first record tables, an identification code of a record table associated with the first record table, and a first one corresponding to the element For the number of times of viewing, the second record table includes a second identification code corresponding to one of the second record tables, an identification code of the record table associated with the second record table, and a second number of views corresponding to one of the elements.

In a preferred embodiment, when the source message is turned on, the first number of views is updated, and when the destination message is turned on, the second number of views is updated.

In a preferred embodiment, the first record table further includes a first sharing time corresponding to one of the source messages, and the second record table further includes a second sharing time corresponding to one of the destination messages.

In a preferred embodiment, the method for sharing an element further includes the step of: calculating the element according to at least one of the first sharing time, the first viewing times, the second sharing time, and the second viewing times The rate of clicks in one of the specific time intervals.

In a preferred embodiment, the first record table further includes first location information corresponding to the source message, and the second record table further includes second location information corresponding to one of the destination messages.

In a preferred embodiment, the first record table further includes first location information corresponding to the source message, and the second record table further includes second location information corresponding to one of the destination messages.

In a preferred embodiment, the method for sharing an element further includes the steps of: according to the first sharing time, the first viewing frequency, the first location information, the second sharing time, the second viewing frequency, and the first At least one of the two location information calculates the click rate of the element at a particular location or the propagation path of the element in the particular time interval.

In a preferred embodiment, the first record table includes first sharer data corresponding to one of the first users transmitting the source message, and the second record table includes a second message corresponding to the transfer of the destination message. One of the users' second sharer information.

In a preferred embodiment, the first record table includes first channel data corresponding to one of the second users, and the second record table includes second channel data corresponding to one of the third users.

In a preferred embodiment, the element is a unified information unit or a unified tool that is provided to the projected workspace.

In a preferred embodiment, the unified information unit is formed by unifying one of the original information obtained from at least one information source; and/or the unified tool is obtained from at least one information source. One of the original tools is formed by being unified.

In a preferred embodiment, the unified information unit includes a file, a web page, a data base row, a policy, a rule, or any accessibility to a correlation. Information about the machine or a server; and/or the unified tool includes a utility, an interface tool set, an agent, an application, a service, or any An executable element that can be accessed to an associated machine or a server.

In a preferred embodiment, the element is the projected workspace.

In a preferred embodiment, the present invention also provides a method for sharing an element, comprising: transmitting an element via a first path link information (URI), wherein the first path link information includes obtaining a projectable space a projectable space instance and a message corresponding to the first record table of the element, wherein the projectable space entity is used to establish a projected workspace; receiving and opening the first path link information to execute The projected workspace, wherein the first record table is updated when the first path link information is turned on to execute the projected work space; and the element is transmitted via a second path link information, wherein the The second path link information includes a message for obtaining the projectable space entity and a second record table corresponding to the element; receiving and starting the second path link information to execute the projected work space, where The second record table is updated when the second path link information is turned on to execute the projected work space; and one of the element propagation relationship parameters is calculated according to the first record table and the second record table.

In a preferred embodiment, the first path connection information and the second path connection information comprise a Hypertext Transfer Protocol (HTTP) path link information, a File Transfer Protocol (FTP) path link information, and a local file ( Local file) At least one of the link information.

In a preferred embodiment, the method of sharing elements further includes the step of: interpreting the projectable spatial entity using a projection to execute the projected workspace.

In a preferred embodiment, the projectable spatial real system is an object, an extensible markup language (XML) file, or a structured language or a structured protocol (structured) Protocol) An entity generated by an instance.

In a preferred embodiment, the first record table includes a first identification code corresponding to one of the first record tables, an identification code of a record table associated with the first record table, and a first one corresponding to the element For the number of times of viewing, the second record table includes a second identification code corresponding to one of the second record tables, an identification code of the record table associated with the second record table, and a second number of views corresponding to one of the elements.

In a preferred embodiment, when the first path link information is turned on, the first view count is updated, and when the second path link information is turned on, the second view count is updated.

In a preferred embodiment, the first record table further includes a first sharing time corresponding to the first path link information, and the second record table further includes a second share corresponding to the second path link information. time.

In a preferred embodiment, the method for sharing an element further includes the step of: calculating the element according to at least one of the first sharing time, the first viewing times, the second sharing time, and the second viewing times The rate of clicks in one of the specific time intervals.

In a preferred embodiment, the first record table further includes first location information corresponding to the source message, and the second record table further includes second location information corresponding to one of the destination messages.

In a preferred embodiment, the first record table further includes first location information corresponding to the source message, and the second record table further includes second location information corresponding to one of the destination messages.

In a preferred embodiment, the method for sharing an element further includes the steps of: according to the first sharing time, the first viewing frequency, the first location information, the second sharing time, the second viewing frequency, and the first At least one of the two location information calculates a click rate of the element at a particular location or a propagation path of the element in a particular time interval.

In a preferred embodiment, the first record table includes a first sharer data corresponding to one of the first users transmitting the first path link information, and the second record table includes a second path corresponding to the transfer Link one of the second users to the second sharer information.

In a preferred embodiment, the first record table includes first channel data corresponding to one of the second users, and the second record table includes second channel data corresponding to one of the third users.

In a preferred embodiment, the element is provided to one of the projected workspaces, or a unified information unit or a unified tool.

In a preferred embodiment, the unified information unit is formed by unifying one of the original information obtained from at least one information source; and/or the unified tool is obtained from at least one information source. One of the original tools is formed by being unified.

In a preferred embodiment, the unified information unit includes a file, a web page, a data base row, a policy, a rule, or any accessibility to a correlation. Information about the machine or a server; and/or the unified tool includes a utility, an interface tool set, an agent, an application, a service, or any An executable element that can be accessed to an associated machine or a server.

In a preferred embodiment, the element is the projected workspace.

10‧‧‧ first user

11‧‧‧First machine

12‧‧‧projectable space entities

13‧‧‧Projecting means

14‧‧‧ second machine

15‧‧‧Projected workspace

15’‧‧‧Projected workspace

15”‧‧‧Projected workspace

15a‧‧‧Share button

15b‧‧‧Facebook® option

15c‧‧‧Twitter® option

15d‧‧‧ Confirmation button

16‧‧‧First Record Form

17‧‧‧Source message

18‧‧‧ second user

19‧‧‧ third machine

20‧‧‧Projecting means

21‧‧‧ third user

22‧‧‧ second record

23‧‧‧ destination message

24‧‧‧ fourth machine

25‧‧‧Projecting means

26‧‧‧Statistics

971‧‧‧First electronic device

972‧‧‧Second electronic device

973‧‧‧projectable space entity

974‧‧‧Projecting means

975‧‧‧Working environment

976‧‧‧Projected workspace

977‧‧‧Microcore

979‧‧‧Dropbox

980‧‧‧ Unified script

981‧‧‧personal work space

982‧‧‧Dropbox

983‧‧‧Cloud Hard Drive

984‧‧‧Server

985‧‧‧ original information

985’ ‧ ‧ Unified Information Unit

986‧‧‧Original tools

986’‧‧‧First unified tool

987‧‧‧ original tools

987’‧‧‧Second unified tool

989‧‧‧Transformer

991‧‧‧ original elements

992‧‧‧Element converter

993‧‧‧Unified data structure

994‧‧‧ unified elements

9731‧‧‧ Unified script

9761‧‧‧dotted box

9761’‧‧‧Dropbox Input

9762‧‧‧dotted box

9762’‧‧‧ Picture Reader

9791‧‧‧jpg image file

9791’‧‧‧Unified jpg image file

9792‧‧‧jpg image file

9792’‧‧‧Unified jpg image file

9793‧‧‧gif image file

9793’ ‧ ‧ unified gif image file

9881‧‧‧Information input device

9882‧‧‧Information Input

9883‧‧‧Information input device

Figure 1: Schematic diagram of the implementation concept of the unified method in one embodiment.

Figure 2: A diagram showing a better concept of a unified script as an intermediate language for implementing a personal workspace.

Figure 3 is a schematic diagram of a preferred configuration of the personal workspace shown in Figure 2.

Figure 4 is a schematic diagram showing the initial state of a method of projecting a workspace in a preferred embodiment.

FIG. 5A is a schematic diagram showing the operation of the method of projecting the workspace shown in FIG. 4. FIG.

FIG. 5B is a schematic diagram showing the operation of the method of projecting the workspace shown in FIG. 4. FIG.

Figure 6 is a schematic diagram showing the relative relationship between the projectable spatial entity shown in Figure 4 and the projected workspace shown in Figure 6B.

Figure 7 is a block system diagram of a method for sharing elements of the present invention.

Figure 8 is a flow chart of generating a record table for the present invention.

Figure 9 is a schematic diagram of the first record form of the present invention.

Figure 10 is a schematic diagram of the statistical table of the present invention.

Figure 11 is a schematic diagram of a dot rate chart of the present invention.

Figure 12 is a schematic diagram of a propagation path chart of the present invention.

The invention will be more fully understood from the following description, including the <RTIgt; For the sake of brevity, the publications cited in this specification, including the disclosure of patents, are hereby incorporated by reference.

The following examples of the invention are non-limiting and represent only a variety of aspects and features of the invention. In the most limited technical sense, the term "information source" as used herein refers to a sequence of symbols that can be interpreted as useful information, and such useful information is used to organize and tag data; wherein the source of information may include : Websites (such as Internet services), internal networks, online communities, software, e-books, databases, and other informational media (such as storage media available for non-transitory computers) Body, mobile device storage media). Moreover, the "original information" described herein may include files, web pages, databases, policies, rules, or any data accessible to related machines and servers, and the "original tools" described herein may include utilities. An interface tool set, a smart agent tool, an application, a service tool, or any executable element that can access related machines and servers. However, the source of information, original information and original tools are not limited to the above.

Moreover, "original information" and "original tools" are one embodiment of the "original elements" described herein, and in the implementation of the present invention, multiple "original elements" from the same or different "information sources" Each can be modeled into multiple "unified elements" through a unified method, so that multiple "unified elements" in the same working environment can be compatible with each other to coordinate specific tasks; "Unified tools" and "unified information units" are all examples of "unified elements." Moreover, the "Matterizer" described herein is a component, device or code for unifying the "original elements".

In an embodiment, the unified method may be: reconstructing original information obtained from at least one information source of the plurality of information sources according to a unified data structure, thereby modeling the original information into unified information. Unit, and/or reorganizing the original tool obtained from at least one information source of the plurality of information sources according to another unified data structure, thereby modeling the original tool into a unified tool; wherein the unified data structure and the Another unified data structure may be the same or different, and the above unified method may be implemented by an element converter (Matterizer).

Please refer to FIG. 1 , which is a schematic diagram of the implementation concept of the above unified method in an embodiment. 1 illustrates an element converter 992 reforming an attribute and an associated link of the original element 991 in accordance with the unified material structure 993 to model the original element 991 as a unified element 994, such that the basic attributes of the unified element 994 include The type of the original element and the link that indicates where the original element is located.

In this embodiment, the original element 991 includes at least the original information (not shown) or the original tool (not shown), but is not limited thereto. Secondly, in the above unified method, when the attributes obtainable from the original information correspond to the attributes to be unified in the unified information unit, the unified information unit can be directly generated via the element converter 992; When the attributes obtained by the original information cannot correspond to the attributes that are to be unified in the unified information unit, the original information must be redefined by logically reorganizing the attributes and related links of the original information, so that the original information is Converting to new raw information whose attributes correspond to attributes that are to be unified in the unified information unit, thereby indirectly producing unified information units.

Moreover, when the original tool is compatible with the working environment of the workspace, the unified tool can be directly generated via the element converter 992; and when the original tool is incompatible with the working environment of the workspace, The unified tool is indirectly generated by a software development kit (SDK) driven by an adapter and/or original tool; the adapter is used to provide a workspace compatible interface Interface implementation.

For a specific implementation manner of the unified method described in the embodiment, a specific manner of obtaining the unified element, and a specific operation mode of the element converter, refer to US Patent Application No. 14/324069, entitled " A METHOD OF UNIFYING INFORMATION AND TOOL FROM A PLURALITY OF INFORMATION SOURCES", and the Chinese Patent Application No. 201410768564.X, which is based on the priority of the United States Patent Application No. 14/324,069, entitled "will be from the plural information" The method of unifying the information and tools of the source and the computer program products and devices using the method are not repeated here.

In particular, the above unified method is only one embodiment of the unified method adopted in the present case, and the method for unifying multiple original elements from different information sources is not limited to the above, and those skilled in the art can Make any equal change design based on actual application needs.

The following is an example of a unified method different from the above description. The first unified method is applied to the information unification method in Garmin satellite navigation. The Point of Interest (POI) function of Garmin satellite navigation is the original landmark information input through the information unification method (original Information) to achieve a unified program to obtain the corresponding unified landmark information (unified information unit); the second method is a unified tool for Android (Android) system, Android (Android) system is a Linux The basic open source mobile device operating system, but the applications (original tools) in the Android system are mostly written by Java, so the application (original tool) written by Java can be unified through the tool. It is modeled as a unified application (unified tool) that is compatible with Android, and can be executed in Android.

Furthermore, the term "workspace" as used herein refers to a workspace that allows at least one element converter and/or at least one tool and/or at least one piece of information to interact to perform a particular task, and at least one information and/or At least one tool can be input into the workspace by at least one element converter, but the manner in which information and/or tools are input into the workspace is not limited thereto; secondly, the information importer (information importer) described below (The information input devices 9881, 9882, 9883 in FIG. 2, the Dropbox input device 9761' in FIG. 6, etc.) are all an embodiment of the element converter. Furthermore, the "unified script" described herein refers to an intermediate language that can be used as a workspace, and at least one element converter and/or at least one information and/or at least one tool can be made through a "unified script". Is provided (such as built-in or plug-in) to the workspace.

In one embodiment, the at least one information is at least one unified information unit formed by the at least one original information obtained from the at least one information source, and the at least one tool is from at least one information. At least one original tool obtained by the source is formed by at least one unified tool formed by being unified; wherein the user can select the required unified information unit and/or the unified tool according to different tasks. The information source is added (such as built-in or plug-in) to the personal workspace, so the "workspace" can be a user-oriented "personal workspace."

Further, please refer to FIG. 2 and FIG. 3 . FIG. 2 is a schematic diagram of a better concept of a unified script as an intermediate language for implementing a personal workspace, and FIG. 3 is a schematic diagram of a preferred configuration of the personal workspace shown in FIG. 2 . . 2 and FIG. 3 illustrate the unified information unit 985' corresponding to the original information 985 in the Dropbox 982, corresponding to the compatible original tool 986 in the cloud hard disk 983 according to the requirements of the task. The first unified tool 986' and the second unified tool 987' corresponding to the incompatible original tool 987 in the server 984 are combined into the personal workspace 981; in detail, the user can edit one for the first time. As a unified script 980 for realizing the intermediate language of the personal workspace 981, the information input device 9881 of the Dropbox 982, the information input device 9882 of the cloud hard disk 983, and the information of the server 984 are configured by the unified script 980. The input device 9883; wherein the information input device 9881 can unify the original information 985 in the Dropbox 982 into the unified information unit 985' and input to the personal workspace 981.

Moreover, FIG. 2 and FIG. 3 also illustrate that the original tool stored in the cloud hard disk 983 is a compatible original tool 986 (that is, the compatible original tool 986 can be used in a personal work space. The component architecture for the unified tool is compatible with the 981, and the first unified tool 986' corresponding to the compatible original tool 986 can be passed through the unified script 980 (using the information input device 9882 therein). Provided directly to the personal workspace 981.

Moreover, Figures 2 and 3 also illustrate that the original tool stored in the server 984 is an incompatible original tool 987 (i.e., the incompatible original tool 987 is used in the personal workspace 981 for the unified tool). The component architecture is incompatible, and the second unification of the incompatible original tool 987 is achieved through the unified script 980 (using the compatible converter 989 and the information input device 9883). Tool 987' is provided to personal workspace 981.

In addition, FIG. 3 also illustrates that the user configures the arrangement (eg, grouping or placing) unified information unit 985', the first unified tool 986', and the second unified tool 987 according to actual application requirements. 'In a specific area of the personal workspace 981; finally, the user can save by using the unified tool in response to the unified tool and the operational relationship between the unified information units (such as click actions or drag actions between the two) Take or control the corresponding unified information unit to perform the required tasks.

Regarding the "unified script as a specific implementation of the intermediate language of the personal workspace" described in the embodiment, "the user unifies the required unified information unit and/or the required unit according to the actual application requirements. A specific implementation of a tool that can be freely combined into a personal workspace to perform a task. Reference is made to US Patent Application No. 14/325,466 entitled "METHOD FOR PERFORMING TASK ON UNIFIED INFORMATION UNITS IN A PERSONAL WORKSPACE" And the Chinese Patent Application No. 201410796528.4, which is based on the priority of the United States Patent Application No. 114/324,069, the entire disclosure of which is incorporated herein by reference. The computer program product and system of the method" will not be repeated here.

In particular, the above personal workspace is only an embodiment of the workspace, and the workspace applied to the present case is not limited to the above; for example, a unified script that implements the intermediate language of the workspace can be edited in advance. Make the workspace a workspace with built-in preset element converters and/or preset information and/or preset tools. Such workspaces are not limited to individual operations, but can also be used for multiple applications. The user operates simultaneously or separately.

Furthermore, the "workspace" described herein can be projected to any computing-capable electronic device via a "projection workspace method" so that any user can operate on any computing-capable electronic device. "Projected workspace".

In an embodiment, the method for projecting a workspace includes: first, obtaining a projectable space instance that is instantiated by a unified script via a path link information (URI); wherein, unified The script is defined to configure at least one of an element converter, information, and tools to build a workspace (as previously explained), and the projectable spatial entity is used to create a projected workspace corresponding to the workspace, Providing an interface for operating at least one of an element converter, information, and a tool to perform a task; then, using a projector to interpret the projectable spatial entity and establishing an element converter, information, and tools At least one of the ones are disposed in the work environment of the projectable spatial entity to thereby perform the projected workspace, whereby at least one user interacts with the projected workspace.

The projection means can be obtained from a remote data station, a projectable space entity or a preloaded application, and loaded into an engine for providing a compatible environment to perform projection means, and the engine can be Including the Javascript engine, the Windows application, or the Linux application, but not limited to the above; in addition, the unified script can be defined by a file type (DTD), an extensibility markup language schema (XML schema), a structured language or a structured protocol, etc., but not limited to the above; and the space entity that can be projected can be an object, an extensibility indicator A language (XML) file, or an instance generated by a structured language or a structured protocol, etc., but not limited to the above.

Further, please refer to FIG. 4, FIG. 5A to FIG. 5B and FIG. 6. FIG. 4 is a schematic diagram of an initial state of the method for projecting the workspace in a preferred embodiment, and FIG. 5A and FIG. Schematic diagram of the operational concept of the spatial method. FIG. 6 is a schematic diagram showing the relative relationship between the projectable spatial entity shown in FIG. 4 and the projected workspace shown in FIG. 5B. In the initial state shown in FIG. 4, there are a first electronic device 971 and a second electronic device 972 that are connectable to each other (eg, connected through a network), and the first electronic device 971 stores a space that can be projected. Entity 973, and A projection means 974 is built in the second electronic device 972.

Moreover, the unified script 9731 is declared by a file type definition (DTD), and is defined to configure at least one information input device (which is an implementation aspect of the element converter) and/or at least one Unifying the information unit and/or at least one unified tool to model a workspace, and the projectable spatial entity 973 is an entity generated by an Extensible Markup Language (XML), as shown in FIG. It is used to build a projected workspace 976 corresponding to the workspace and is allowed to be added to or removed from the information importer and/or unified information unit and/or unified tool.

Moreover, the projection means 974 of the second electronic device 972 establishes a working environment 975 for the projected workspace 976 on the second electronic device 972 and provides a micro core 977 (see FIG. 6) to the operating environment 975. Equiring at least one information input device and/or at least one unified information unit and/or at least one unified tool to be added to the projected workspace 976; wherein, when the second electronic device 972 is connected through a path When the information captures the projectable spatial entity 973 in the first electronic device 971, the projection means 974 in the second electronic device 972 begins to interpret the projectable spatial entity 973, as shown in FIG. 5A; After the projectable spatial entity 973 is interpreted by the projection means 974, the projected workspace 976 is created on the work environment 975 in accordance with the content interpreted by the projectable spatial entity 973, as shown in Figure 5B. The user at the end of the second electronic device 972 can interact with the projected workspace 976 via the second electronic device 972 to perform related tasks.

The relationship between the above-described unified script 9731, the projectable spatial entity 973, and the projected workspace 976 will be further described below using the usage scenarios shown in FIG. 6. The usage scenario shown in FIG. 6 is: creating a workspace that can be projected and can read the jpg image files and gif image files stored in the specified network space for the user to view, and in the context of the use, unified The script 9731 is declared with a file type definition (DTD), and the projectable space entity 973 is generated in an extensibility markup language (XML).

Moreover, a data input device and a unified tool are added to the projectable space entity 973, and the information input device is configured to input at least one unified information unit corresponding to the at least one original information to the projected work. In space 976; in this usage scenario, the information input device is a Dropbox input device (ie, the dashed box 9761 is shown), and the original information is Dropbox. The jpg image file in the 979 information source is 9791, 9792 and the gif image file 9793. The unified information unit is unified for the unified jpg image file 9791', 9792' and the unified gif image file 9793' described later. The tool is a picture reader (i.e., dashed box 9762 is shown) for reading the picture file input into the projected workspace 976.

Moreover, the projected workspace 976 is created after the projectable spatial entity 973 is interpreted by the projection means 974 in the second electronic device 972 such that the projected workspace 976 is provided with a Dropbox input 9761'. (corresponding to the dashed box 9761 shown) and a picture reader 9762' (corresponding to the dashed box 9762 shown), the Dropbox input unit 9761' will then use the jpg picture files 9791 and 9792 in the Dropbox 979 information source. The gif image file 9793 is unified and input to the projected work space 6, so that the unified jpg image files 9791', 9792' and the unified gif image file corresponding to the jpg picture files 9791, 9792 and the gif picture file 9793 respectively. 9793' is presented on the projected workspace 976; then, when the user of the second electronic device 972 is in a unified operation mode, the unified jpg image file 9791', 9792' and the unified gif image file 9793' When one is operating (such as clicking on the unified jpg image file 9791', 9792' and unified gif image file 9793', or will unify jpg image files 9791', 9792' and unified gif pictures File 9793 Any one of them is dragged to the picture reader 9762'), and the picture reader 9762' reads the contents of any of the unified jpg picture files 9791', 9792' and the unified gif picture file 9793'. And make it appear for the user to watch. Further, the above-described Dropbox input device 9761' and picture reader 9762' are equivated by the micro core 977.

Specifically, the path connection information of the projectable space entity 973 may be Hyper File Transfer Protocol (HTTP) path link information or File Transfer Protocol (FTP) path link information, and if the first electronic device 971 and the second electronic device are When the 972 is a common device, the path connection information of the space entity 973 that can be projected may also be linked to the local file, but the type of the path connection information is not limited to the above.

For a specific manner of obtaining a method for projecting a workspace as described in this embodiment, reference is made to US Patent Application No. 14/577,772, entitled "METHOD OF PROJECTING A WORKSPACE AND SYSTEM USING THE SAME", and a US patent can be referred to. Application No., 14/324069, 14/325466, 14/577772, China Patent Application No. 201410814138.5, which is the basis of the international priority, entitled "Method of Projecting Workspace and Application of the Projector" The system of methods of space", so it will not be repeated here.

In particular, the above method of projecting the workspace is only a projection method for projecting the workspace to any computing device, but the projection method of projecting the workspace to any computing device is not To the above, it is well known to those skilled in the art that any equal change design can be made according to actual application requirements. Second, since any workspace can be projected onto any computing-capable electronic device, any workspace can be considered to be delivered to any workspace with computing power.

The method of sharing elements of the present invention is explained below. Please refer to FIG. 9 to FIG. 9. FIG. 7 is a block diagram of a method for sharing elements according to the present invention. FIG. 8 is a flowchart of generating a record table according to the present invention, and FIG. 9 is a schematic diagram of a first record table according to the present invention.

First, the first user 10 takes the projectable spatial entity 12 from the first machine 11, and then interprets the projectable spatial entity 12 by means of the projection means 13 to perform the projected workspace 15 on the second machine 14. The first user 10 can then freely combine a single or multiple element converters, a unified tool or a unified information unit to further configure the projected workspace 15. It is added that the projectable space entity 12 can also be stored in the second machine 14.

When the first user 10 clicks the share button 15a (shown in FIG. 8) in the projected workspace 15 to select a material such as a sharing unified tool, a unified information unit, or a projected workspace 15, A first record table 16 and a source message 17 will be generated.

In this example, the source message 17 is a first path link information, such as http://abc.com/#! /space_id? Propagation_id=”...”, after the source message 17 is obtained, the projection information can be obtained through the identification information (space id) of the projected workspace 15 and the first identification code (propagation id) of the first record table 16. The space entity 12 and the first record table 16. It can be understood that although the first record table 16 is stored in the first machine 11 in FIG. 7, the first record table 16 can be stored in any storage medium having a network connection function, instead of FIG. The limit shown is limited.

Moreover, the first user 10 can use a suitable channel, such as but not limited to a network channel such as Whatsapp®, Line®, Facebook®, Twitter®, or Telecommunication or Fax. Wait for telecommunication (telecom) channels, or note (paper) Note) A physical channel, the source message 17 is transmitted to a single or plural second user 18. For example, as shown in FIG. 8, when the first user 10 clicks the share button 15a and selects at least one of the Facebook® option 15b and the Twitter® option 15c, and then clicks the confirmation button 15d, the source message 17 will be shared to Facebook. ® and / or Twitter® are turned on by the second user 18 in Facebook® and/or Twitter®. After the second user 18 turns on the source message 17 to obtain the projectable spatial entity 12, the projected workspace entity 15 can be interpreted by the projection means 20 on the third machine 19 to perform the projected workspace 15'. It can be understood that although the source message 17 is only transmitted to the single second user 18 in FIG. 7, the first user 10 can simultaneously transmit the source message 17 to the plurality of second users 18 through various channels. Not limited to those shown in Figure 7.

In addition, in this example, the path connection information may be a hypertext transfer protocol (HTTP) path link information, a file transfer protocol (FTP) path link information, or a local file (local file). Link information, but not limited to this.

Next, the first record table 16 of the present invention will be described. The first record table 16 can be an object, an extensible markup language file, or an entity generated in a structured language or a structured protocol, etc., but is not limited thereto. As shown in FIG. 9, in this example, the first record table 16 includes information fields such as propagation_id, propagator_id, propagated_time, propagated_channels, propagated_work, propagated_link, track, network_address, geo_info, viewed_matters, and produced_view_count, which will be further described below.

First, the propagation_id information field is the first identification code of the first record table 16. The propagator_id information field is the user who created the first record table 16 for sharing, in this case the first sharer data of the first user 10.

The propagated_time information field is the generation time of the first record table 16, which is also referred to as the first share time in this example. The propagated_channels information field is the delivery source message 17, that is, the second user 18 receives the first channel data of the source message 17, such as Facebook® or Twitter®. The propagated_work information field is the work space corresponding to the first record table 16, which is the identification information of the projected work space 15 in this example.

The propagated_link information field is the first path link information of the source message 17. It should be noted that the source message 17 shared to different channels in this example may have different The first path links the information, but can be used to obtain the projectable spatial entity 12 and the first record table 16 regardless of how the first path link information changes. For example, the source message 17 that is shared to Facebook® can be http://abc.com/#! /space_id? Propagation_id=”...”&channel=”Facebook”, the source message 17 that is shared to Twitter® can be http://abc.com/#! /space_id? Propagation_id=”...”&channel=”Twitter” to record the transmission channel of the source message 17, but not limited to this.

The track information field is used to record the identification code of the record table associated with the first record table 16. For example, when the user a selects the sharing element to the user b to generate the record table a and the path link information a, and the user b selects to share the same element to the user c to generate the record table b and the path link information b, The track information field in the record table b will record the identification codes of the record table a and the record table b at the same time, so as to share the user b's share sharing on behalf of the sharing of the user a. Similarly, when the user c chooses to share the same element to the user d to generate the record table c and the path link information c, the track information field in the record table c will simultaneously record the record table a, the record table b and the record table. The identification code of c, in order to share the user a, drives the sharing of the user b and the user c. In addition, in another approach, the track information field in the record c only needs to record the identification code of the record table b and the record table c. When the record table c is obtained, the record can also be obtained by the record table b. Table a knows that the element was originally shared by sharer a. Since the first user 10 is the first sharer in this example, the track information field of the first record table 16 will only record the first identification code of the first record table 16.

The network_address information field is a user who selects the first record table 16 to be created, in this case, the first user 10's IP address (Internet Protocol Address). The geo_info information field is a user who selects the first record table 16 to be shared, in this case, the first location information of the first user 10. The viewed_matters information field is the identification information of the unified tool or the unified information unit that the first user 10 has opened in the projected workspace 15 before the sharing. The produced_view_count information field represents the first number of views generated by the sharing. When the second user 18 opens the source message 17 to obtain the projectable space entity 12 and the first record table 16, the first number of views will be updated. And increase.

In addition, in the propagated_link information field of the first record table 16 and the produced_view_count information field, the first path can be individually recorded according to different channels. The information and the number of first readings.

The behavior of sharing the unified tool, the unified information unit, or the projected workspace 15 is similar to that of the first user 10, and the second user 18 can also select the same through the projected workspace 15'. Or different channels share the same unified tool, the same unified information unit or the projected workspace 15' element to a single or plural third user 21. Similarly, when the second user 18 chooses to share to the third user 21, a second record table 22 and a destination message 23 are generated. In this example, the destination message 23 is a second path link information for obtaining the projectable spatial entity 12 and the second record table 22.

The third user 21 can then obtain the projectable spatial entity 12 by means of the destination message 23 and interpret the projectable spatial entity 12 by means of the projection means 25 on the fourth machine 24 to execute the projected workspace 15". It can be understood that although the destination message 23 is only transmitted to the single third user 21 in FIG. 7, the second user 18 can simultaneously transmit the destination message 23 to the plurality of third users 21 through various channels. It is not limited to those shown in Fig. 7. In addition, the projected workspaces 15, 15' and 15" are created after interpreting the same projectable spatial entity 12, so the projected workspaces 15, 15' And 15" is the exact same workspace.

The second record table 22 also includes information fields such as propagation_id, propagator_id, propagated_time, propagated_channels, propagated_work, propagated_link, track, network_address, geo_info, viewed_matters, and produced_view_count, and thus is not presented in another drawing.

In the second record table 22, the propagation_id information field is the second identification code of the second record table 22. The propagator_id information field is the user who selected the second record table 22 to be shared, in this case the second sharer data of the second user 18.

The propagated_time information field is the generation time of the second record table 22, which is also referred to as the second share time in this example. The propagated_channels information field is a delivery destination message 23, that is, the third channel 21 of the destination message 23 transmitted by the third user 21, such as Facebook® or Twitter®. The propagated_work information field is the work space corresponding to the second record table 22, which is the identification information of the projected work space 15' in this example.

The propagated_link information field is the path link information of the destination message 23. It should be noted that the destination message 23 shared to different channels in this example may have a different second path. The path links information, but can be used to obtain the projectable spatial entity 12 and the second record table 22 regardless of the second path link information.

As described above, the track information field is used to record the identification code of the record table associated with the second record table 22, and the second record table 22 is for the second user 18 to receive the source shared by the first user 10. The message 17 is generated after the sharing, so the track information field in the second record table 22 will simultaneously record the first identification code of the first record table 16 generated by the first user 10 when sharing and the second user 18 sharing. The second identification code of the second record table 22 generated at the time is used to drive the sharing of the second user 18 by the sharing of the first user 10.

The network_address information field is the user who has selected the second record table 22 to be shared, in this case the IP address of the second user 18. The geo_info information field is the second location information of the second user 18 in this example, the user who selected the second record table 22 to be selected for sharing. The viewed_matters information field is the identification information of the unified tool or the unified information unit that the second user 18 has opened in the projected workspace 15' before the sharing. The produced_view_count information field represents the second number of views generated by the sharing. When the third user 21 opens the destination message 23 to obtain the projectable space entity 12 and the second record table 22, the second number of views will be updated. And increase.

Furthermore, since the projected workspaces 15, 15' and 15" correspond to the same projectable space entity 12 and are identical workspaces, the propagated_work information fields of the first record table 16 and the second record table 22 are The recorded identification information should also be the same.

As can be seen from the above description, each time a user shares a unified tool, a unified information unit, or a workspace, a meter will be generated as shown in FIG. 9 by integrating all of the same workspaces. The record table, that is, the record table with the same identification information recorded in the propagated_work information field, can obtain various propagation relationship parameters, which will be further explained below.

First, the first machine 11 or a remote server can generate a statistical table based on all the record tables associated with the same workspace, which will be associated with all the same workspaces generated by integrating a time interval. A record sheet was created. Please refer to FIG. 10, which is a schematic diagram of a statistical table of the present invention.

As shown in FIG. 10, the statistical table 26 includes record_id, propagated_wo Information fields such as rk, record_start_date, record_end_date, and day_view_count.

The record_id is the identification information of the statistical table 26. The propagated_work is the workspace corresponding to the statistical table 26, which in this example is the identification information of the workspace created by interpreting the projectable spatial entity 12, so that it will be associated with the first record table 16 and the second record table 22 The identification information recorded in the propagated_work information field is the same.

The record_start_date information field and the record_end_date information field are the start record date and the end record date of the statistical table 26, that is, each record table associated with the projectable space entity 12 recorded in the statistics table 26, and its propagated_time information field. The bit needs to be between the start record date and the end record date.

The day_view_count information field records the cumulative value of the visited_matters information field in the record table associated with the projectable space entity 12, the propagated_time information field is the same_date information field in the statistics table 26 (in the statistics table 26 is the matter_view_count information field) ), and the cumulative value of the produced_view_count information field of all the records generated up to that date (in the statistics table 26, the work_view_count information field).

For example, as shown in FIG. 10, the record_start_date information field and the record_end_date information field of the statistical table 26 are 2014-06-01 and 2014-06-30, respectively. And the work_view_count information field of the statistics table 26 records each date in detail, for example, the cumulative value of the produced_view_count information field of all the record tables associated with the projectable space entity 12 up to 2014-06-30. The meter_view_count information field of the statistical table 26 records each date in detail, for example, the cumulative value of the viewed_matters information field of all the records associated with the projectable spatial entity 12 on the date of 2014-06-30.

Therefore, when the user wants to know the point rate of the workspace corresponding to the projectable space entity 12 in any day, any number of days, or the entire month between 2014-06-01 to 2014-06-30 It can obtain the statistical table 26 as shown in FIG. 10 through the identification information of the workspace, and draw the chart shown in FIG. 11 by the work_view_count information field of the statistical table 26, and then learn that any day, any The reading rate of the workspace in a few days or throughout the month.

Furthermore, if the user wants to know that any day, any number of days or the entire month between 2014-06-01 and 2014-06-30, the workspace corresponding to the projectable space entity 12 is turned on. The most unified tools or unified information units can be aggregated and sorted by statistics. Obtained in the material_view_count information field of Table 26.

Moreover, the first machine 11 or a remote server may not generate a statistical table, but according to the propagated_time information field of all the record tables and the geo_info information field, the propagation map as shown in FIG. 12 is drawn, thereby obtaining a space with the projection. The corresponding work space of the entity 12 in a specific time interval. Or, according to the produced_view_count information field of all the record tables and the geo_info information field, the click rate of the workspace corresponding to the projectable space entity 12 at a specific location is obtained.

For example, as shown in FIG. 12, when the user selects any time point, for example, the time point T, the first positioning point A, the second positioning point B, and the third positioning point C will be displayed in the figure. The first anchor point A indicates the location of the sharer sharing the unified tool, the unified information unit or the workspace at the time point T, and the second anchor point B indicates that the same unified tool and the unified information unit are shared one day before the time point T. Or the location of the sharer of the workspace, the third anchor point C indicates the location of the sharer sharing the same unified tool, unified information unit or workspace one day after the time point T. In this way, the user can know the propagation path of the same unified tool, unified information unit or workspace in a specific time interval.

It can be understood that the first machine 11 or a remote server may also generate a statistical table, and calculate the number of readings of the workspace corresponding to the projectable space entity 12 according to the produced_view_count information field of all the records. The channel to view the most times.

In addition, the first machine 11 or a remote server can still know the key communicator according to the propagator_id information field, the track information field, and the produced_view_count information field.

For example, by counting all the records having the same workspace identification information and having the identification code of the record table a in the track information field, the number of shares shared by the record table a can be known. According to the sharer information recorded in the information field of the propagator_id in the record a, the number of shares transferred by the specific user can be known, and then the key communicator can be found.

Or, by finding all the plural record tables having the same workspace identification information, the produced_view_count information field has a record table with the largest value, and according to the sharer information recorded in the propagator_id information field in the record table, Can know the specific user The number of visits can also be found in key communicators.

As can be seen from the above description, the present invention provides a method for sharing elements by generating a record table with information such as the number of times of viewing, sharing time, location, etc., each time an element is shared, and by integrating all records related to the same element. The table obtains various propagation relationship parameters of the element, thereby solving the problems of the prior art.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the scope of the patent application of the present invention. Therefore, any equivalent changes or modifications made without departing from the spirit of the present invention should be included in the present case. Within the scope of the patent application.

10‧‧‧ first user

11‧‧‧First machine

12‧‧‧projectable space entities

13‧‧‧Projecting means

14‧‧‧ second machine

15‧‧‧Projected workspace

15’‧‧‧Projected workspace

15”‧‧‧Projected workspace

16‧‧‧First Record Form

17‧‧‧Source message

18‧‧‧ second user

19‧‧‧ third machine

20‧‧‧Projecting means

21‧‧‧ third user

22‧‧‧ second record

23‧‧‧ destination message

24‧‧‧ fourth machine

25‧‧‧Projecting means

Claims (36)

A method for sharing an element, comprising: receiving an element via a source message, wherein the source message includes a message for obtaining a first record table corresponding to one of the elements; and transmitting the element via a destination message, wherein the destination message includes And a message for obtaining a second record table corresponding to one of the elements; and calculating a propagation relationship parameter of the element according to at least one of the first record table and the second record table. The method for sharing elements as described in claim 1, wherein the source message is a first path link information (URI), and the destination message is a second path link information. The method for sharing elements according to claim 2, wherein the first path link information and the second path link information comprise a Hyper File Transfer Protocol (HTTP) path link information and a file transfer protocol (FTP) path. Link information and at least one of a local file link information. The method for sharing an element as described in claim 1, wherein the source message includes a message for obtaining a projectable space instance and the first record table, wherein the destination message includes The projectable spatial entity and the message of the second record table, wherein the projectable spatial entity is used to create a projected workspace. The method for sharing elements as described in claim 4, further comprising the step of: interpreting the projectable spatial entity using a projection to execute the projected workspace. A method of sharing elements as described in claim 4, wherein the projectable space is The system is an object, an extensibility markup language (XML) file, or an instance generated in a structured language or a structured protocol. The method for sharing an element as described in claim 1, wherein the first record table includes a first identification code corresponding to one of the first record tables, an identification code of a record table associated with the first record table, and Corresponding to the first viewing frequency of one of the elements, the second record table includes a second identification code corresponding to one of the second record tables, an identification code of the record table associated with the second record table, and an element corresponding to the element The number of second readings. The method for sharing an element as described in claim 7, wherein the first number of views is updated when the source message is opened, and the second number of views is updated when the destination message is turned on. The method for sharing elements according to claim 7 , wherein the first record table further includes a first sharing time corresponding to one of the source messages, and the second record table further includes one of the messages corresponding to the destination. Second sharing time. The method for sharing elements according to claim 9 further includes the following steps: calculating, according to at least one of the first sharing time, the first viewing times, the second sharing time, and the second viewing times The element is clicked at one of a specific time interval. The method for sharing elements according to claim 7 , wherein the first record table further includes first location information corresponding to one of the source messages, and the second record table further includes one of the messages corresponding to the destination message. Two location information. The method for sharing elements according to claim 9 , wherein the first record table further includes first position information corresponding to one of the source messages, and the second record table further includes one of the messages corresponding to the destination Two location information. The method for sharing elements according to claim 12, further comprising the steps of: according to the first sharing time, the first viewing times, the first location information, the second sharing time, and the second viewing times And at least one of the second location information calculates the click rate of the element at a specific location or a propagation path of the element in the specific time interval. The method for sharing an element as described in claim 1, wherein the first record table includes a first sharer data corresponding to one of the first users transmitting the source message, the second record table including Transmitting one of the second users of the second user of the destination message. The method for sharing elements according to claim 14, wherein the first record table includes first channel data corresponding to one of the second users, and the second record table includes corresponding to the third user A second channel data. A method of sharing an element as described in claim 4, wherein the element is provided to one of a unified information unit or a unified tool of the projected workspace. The method for sharing elements as described in claim 16 wherein the unified information unit is formed by unifying one of the original information obtained from at least one information source; and/or the unified tool system One of the original tools obtained from at least one information source is formed by being unified. The method for sharing elements as described in claim 16 wherein the unified information unit comprises a file, a web page, a data base row, a policy, a rule or Any material that can be accessed to a related machine or a server; and/or the unified tool includes a utility, an interface tool set, an agent, an application, A service or any executable element that can be accessed by an associated machine or a server. A method of sharing an element as described in claim 4, wherein the element is the projected workspace. A method for sharing an element, comprising: transmitting an element via a first path link information (URI), wherein the first path link information includes obtaining a projectable space instance and corresponding to the element a first record table message, wherein the projectable spatial entity is used to establish a projected workspace; receiving and opening the first path link information to execute the projected workspace, wherein The first record table is updated when a path link information is opened to execute the projected work space; the element is transmitted via a second path link information, wherein the second path link information includes the projectable information a spatial entity and a message corresponding to the second record table of the element; receiving and opening the second path link information to execute the projected workspace, wherein the second path link information is turned on to perform the projected The second record table is updated in the workspace; and one of the elements is calculated based on the first record table and the second record table Sowing relationship parameters. The method for sharing elements according to claim 20, wherein the first path link information and the second path link information comprise a Hyper File Transfer Protocol (HTTP) path link information and a file transfer protocol (FTP) path. Link information and at least one of a local file link information. The method for sharing elements as described in claim 20, further comprising the step of: interpreting the projectable spatial entity using a projection to execute the projected workspace. A method of sharing elements as described in claim 20, wherein the projectable space A real system is an object, an extensible markup language (XML) file, or an instance generated by a structured language or a structured protocol. The method for sharing elements according to claim 20, wherein the first record table includes a first identification code corresponding to one of the first record tables, an identification code of a record table associated with the first record table, and Corresponding to the first viewing frequency of one of the elements, the second record table includes a second identification code corresponding to one of the second record tables, an identification code of the record table associated with the second record table, and an element corresponding to the element The number of second readings. The method for sharing an element as described in claim 24, wherein the first viewing number is updated when the first path linking information is turned on, and the second viewing is when the second path linking information is turned on The number of times is updated. The method for sharing elements according to claim 24, wherein the first record table further includes a first sharing time corresponding to the first path link information, and the second record table further includes a second record table. One of the path link information sharing time. The method for sharing elements according to claim 26, further comprising the step of: calculating according to at least one of the first sharing time, the first viewing times, the second sharing time, and the second viewing times The element is clicked at one of a specific time interval. The method for sharing elements according to claim 24, wherein the first record table further includes first position information corresponding to one of the source messages, and the second record table further includes one of the messages corresponding to the destination. Two location information. The method for sharing elements according to claim 26, wherein the first record table further includes first position information corresponding to one of the source messages, and the second record table further includes one of the messages corresponding to the purpose. Two location information. The method for sharing elements according to claim 29, further comprising the steps of: according to the first sharing time, the first viewing times, the first location information, the second sharing time, and the second viewing times And at least one of the second location information calculates a click rate of the element at a specific location or a propagation path of the element in a specific time interval. The method for sharing elements according to claim 20, wherein the first record table includes a first sharer data corresponding to one of the first users transmitting the first path link information, the second record table And including a second sharer data corresponding to one of the second users transmitting the second path link information. The method for sharing elements according to claim 31, wherein the first record table includes first channel data corresponding to one of the second users, and the second record table includes corresponding to the third user A second channel data. A method of sharing an element as described in claim 20, wherein the element is provided to one of a unified information unit or a unified tool of the projected workspace. The method for sharing elements as described in claim 33, wherein the unified information unit is formed by unifying one of original information obtained from at least one information source; and/or the unified tool system One of the original tools obtained from at least one information source is formed by being unified. The method for sharing elements as described in claim 33, wherein the unified information unit comprises a file, a web page, a data base row, a policy, a rule or Any material that can be accessed to a related machine or a server; and/or the unified tool includes a utility, an interface tool set, an agent, an application, a service or any access to a related machine Or an executable component of a server. A method of sharing an element as described in claim 20, wherein the element is the projected workspace.