WO2003021458A1 - Method and system for producing an ordered compilation of information with multiple authors contributing information contemporaneously - Google Patents
Method and system for producing an ordered compilation of information with multiple authors contributing information contemporaneously Download PDFInfo
- Publication number
- WO2003021458A1 WO2003021458A1 PCT/US2002/026937 US0226937W WO03021458A1 WO 2003021458 A1 WO2003021458 A1 WO 2003021458A1 US 0226937 W US0226937 W US 0226937W WO 03021458 A1 WO03021458 A1 WO 03021458A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- document
- author
- computer code
- node
- subscriber
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 50
- 239000012634 fragment Substances 0.000 claims abstract description 30
- 238000004519 manufacturing process Methods 0.000 claims abstract description 4
- 238000004891 communication Methods 0.000 claims description 31
- 230000000644 propagated effect Effects 0.000 claims description 11
- 230000001902 propagating effect Effects 0.000 claims description 10
- 230000003111 delayed effect Effects 0.000 claims description 4
- 238000009826 distribution Methods 0.000 claims description 4
- 230000008859 change Effects 0.000 description 42
- 230000008569 process Effects 0.000 description 32
- 230000006399 behavior Effects 0.000 description 11
- 230000000007 visual effect Effects 0.000 description 10
- 206010019280 Heart failures Diseases 0.000 description 6
- 230000000694 effects Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 6
- 230000009471 action Effects 0.000 description 5
- 230000001427 coherent effect Effects 0.000 description 5
- 238000013461 design Methods 0.000 description 5
- 235000006508 Nelumbo nucifera Nutrition 0.000 description 4
- 240000002853 Nelumbo nucifera Species 0.000 description 4
- 235000006510 Nelumbo pentapetala Nutrition 0.000 description 4
- 238000012508 change request Methods 0.000 description 4
- 230000000295 complement effect Effects 0.000 description 4
- 238000007726 management method Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000013459 approach Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 230000002526 effect on cardiovascular system Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000033001 locomotion Effects 0.000 description 3
- 230000010076 replication Effects 0.000 description 3
- 238000003860 storage Methods 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000015572 biosynthetic process Effects 0.000 description 2
- 230000001934 delay Effects 0.000 description 2
- 201000010099 disease Diseases 0.000 description 2
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 description 2
- 230000012010 growth Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 210000003516 pericardium Anatomy 0.000 description 2
- 230000002688 persistence Effects 0.000 description 2
- 230000002685 pulmonary effect Effects 0.000 description 2
- 230000002123 temporal effect Effects 0.000 description 2
- 208000024172 Cardiovascular disease Diseases 0.000 description 1
- 241000282412 Homo Species 0.000 description 1
- 206010035148 Plague Diseases 0.000 description 1
- 241000607479 Yersinia pestis Species 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 230000004931 aggregating effect Effects 0.000 description 1
- 230000000747 cardiac effect Effects 0.000 description 1
- 238000004040 coloring Methods 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000013497 data interchange Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000009429 distress Effects 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 238000007667 floating Methods 0.000 description 1
- 238000007373 indentation Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002427 irreversible effect Effects 0.000 description 1
- 239000002398 materia medica Substances 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000002107 myocardial effect Effects 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 238000007639 printing Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 208000011580 syndromic disease Diseases 0.000 description 1
- 235000013311 vegetables Nutrition 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/14—Tree-structured documents
- G06F40/143—Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
Definitions
- Another scenario is that the second author is apprised by the system that another user has the file open. This results in denial to the file or the system will prompt the second author with a question of whether they want a "ghost" copy ofthe file or not. If the second author decides to accept a
- US Patent 5,515,491 discloses a collaborative data processing system.
- the collaborative data processing system disclosed in US Patent 5,515,491 operates in a client server environment and attempts to achieve its goal by allowing multiple users to share a common object.
- a particular weakness ofthe system disclosed in US Patent 5,515,491 is that the system lacks a computer tractable emulation of language context and therefore cannot distinguish between language context and content. As such, the disclosed system is reduced to dealing with characters and cursor movements in which the smallest atomic element of change is the character. For example, when the cursor of one user ofthe disclosed system lands at the beginning of a word, the whole word becomes a floating lock area. Since a word is an arbitrary natural language construct and does not contribute directly to document structure, the implementation loses sight ofthe goal of collaborative authoring, which is to simulate the single author environment.
- US Patent 6,047,288 discloses a collaborative data processing system.
- the collaborative data processing system disclosed in US Patent 6,047,288 operates in a client server environment and attempts to achieve its goal by allowing multiple users to share a common object.
- the system disclosed in US Patent 6,047,288 does have a sense of controlling environmental attributes that allows users to check in and check out portions of a shared object.
- the structure ofthe controlling parameters is a constant across documents and consequently does not express the linguistic context ofthe document.
- the system disclosed in US Patent 6,047,288 suggests a 'session' root node with sub- nodes like 'notifyOnStart', 'broadcast', 'title' and so on.
- the root node and sub-node identifiers would be the same ('session', 'notifyOnStart', ...) except their values would be different.
- the value of 'session' might, for example, be 3 instead of 2.
- these sub-nodes be construed as being a grammar in the sense that grammar is being used in the present invention.
- Documentum is a content management system.
- the guiding design goal of content management systems is the any-to-any model plus workflow. This indeed is a kind of document collaboration, but collaboration goes no further than the file.
- Documentum has numerous search facilities for handling content in files of any format, but suffers from the client server model and file based system's weaknesses.
- Lotus Notes synchronizes client files on a periodic basis through an agreed upon server. Lotus Notes is client server and file based and consequently has no concept of distributed linguistic context like the present invention does. Although Lotus Notes collaborates, it collaborates on different entities than the present invention's linguistic representative, the node.
- the Synthesizer Generator is a structured editor tool first released in 1981. Synthesizer Generator deals with computer languages and not with linguistically semantic context free grammars (see 4.1 "semantic context free grammar"). The Synthesizer Generator has no collaborative networking capability.
- Griffon nor Alliance has true peer-to-peer facilities for content changes or for role and privilege storage and application. Griffon and Alliance are generalized structured editors with persistence mechanisms, which always forces centralization, at least in part, ofthe distributed document. Roles and privileges are not tied to the document structure.
- the system comprises multiple fragment editor executables that function cooperatively as one implemented document type declaration (DTD).
- DTD implemented document type declaration
- Each ofthe multiple fragment editor executables is a specific node implementation ofthe DTD.
- the multiple fragment editor executables are distributed among multiple sites ofthe computer network and operate in a peer-to-peer environment without need for a central server.
- the system allows multiple authors to edit the distributed document contemporaneously while allowing each ofthe multiple authors to view edits made by others ofthe multiple authors.
- replicates ofthe complete document reside at the multiple sites ofthe computer network.
- an edit made by any one ofthe multiple authors is propagated among the replicates residing at the multiple sites ofthe computer network. In one embodiment of the system, an edit made by any one ofthe multiple authors is immediately propagated among the replicates residing at the multiple sites ofthe computer network.
- an edit made by any one ofthe multiple authors is delayed before being propagated among the replicates residing at the multiple sites of the computer network.
- an edit made by any one ofthe multiple authors is relayed to intervening personnel, and thus is delayed, before being propagated among the replicates residing at the multiple sites ofthe computer network.
- an edit made by any one ofthe multiple authors is propagated as an atomic transaction among the replicates residing at the multiple sites ofthe computer network.
- the replicates reside in computer memory at the multiple sites ofthe computer network. In one embodiment, the replicates are persisted by writing to computer hard disks at the multiple sites ofthe computer network.
- each author ofthe multiple authors is assigned an entity type having associated therewith corresponding executables that define the role an author can play in creating distributed document.
- the roles that an author may play in creating the distributed document include: root context author, context author, and content author.
- a subscriber can view edits made by one or more ofthe multiple authors.
- the present invention operates in a peer-to-peer environment. Furthermore, the present invention generates grammar-based executables for any DTD (see 4.2 "document type declaration"), which is the basis for cooperative authoring. Moreover, the present invention utilizes a computer tractable emulation of language context to make explicit a common document structure, and therefore can distinguish between language context and content. In addition, since the present invention's smallest element of change is an indivisible semantic context free grammar entity, the present invention knows that multiple changes in a document grammar element are irrelevant before they are committed.
- the present invention ties all activity to the grammar structure, which itself is allowed to evolve throughout the life cycle ofthe document.
- content created using the present invention changes with respect to the current grammar's context nodes.
- Structural cues as implemented by the present invention don't have to be symbolic and may be clear text and are therefore indistinguishable from content text (this is a good thing).
- Roles and privileges as implemented by the present invention are tied to the grammar and occur as further descendent node creation (nodes may be deleted or modified too). This makes every part of a document created using the present invention, by definition, consistent with its inherent grammar structure.
- the present invention has no need for a centralized server nor does it have need for hard disk persistance since populating a document occurs from node relatives instead of from centralized storage.
- the present invention's default mode is total document replication at each site.
- only visual cues differentiate structural portions ofthe document, which lends itself to natural writing behavior.
- a distributed document created using the present invention is really a full set of grammar node implementations each implemented for the express purpose of editing that particular piece of the document as opposed to being many copies of generalized structural editors.
- An advantage ofthe invention is the ability to forward changes accomplished by an author as they occur. Changes are pushed onto the network to all the other document participants when an author signals the change is complete. Content change completion occurs when the author implicitly uses one ofthe user interface stylization cues or actions defined when the user interface was defined (see 5.4.2.2 Design User Interface).
- context and content changes are always pushed immediately to all other document participants making the bandwidth used directly proportional to the amount of change taking place in the distributed document at that moment.
- context and content changes are relayed through intervening personnel, also called workflow, before reaching its destination.
- Propagated context and content changes should not disrupt the recipients when received and are concurrently added to the recipient's executing processes.
- the most severe recipient interruption is replacing the recipient's executable causing a re-population action.
- the invention prescribes that, given implementation alternatives, the least disruptive alternative to users be chosen in order to preserve single document editing appearance. Since change control is hierarchically distributed and content change authority is mutually exclusive and exhaustive, race or deadlock conditions cannot occur across the document instance's network.
- the invention provides an equivalent replica ofthe document at each author node site and at each subscriber site.
- Each node contains a similarly constructed document and therefore each node maintains the full current version ofthe document by default. Since by design document changes by authors cannot cause concurrency issues, change transactions do not need to be causally sequential, and therefore may arrive and be applied in any order at their destinations. In order to maintain the replication invariant, each transaction must, however, be atomic, thus insuring that the document instances in quiescent state at each site are exact replicas. For a change message to be atomic, the recipient's executable must eventually acknowledge that it has received and applied the change request. Although there is no time limit as to when a change request may be applied, the request is not merely a connectionless broadcast message that needs no acknowledgement. A document is only quiescent if the root context author stops all authors from making changes and all change messages have been successfully delivered.
- the goal ofthe present invention is to create a computer environment that facilitates a document being authored cooperatively and simultaneously by multiple authors without losing document integrity.
- This process recapitulates the formation and evolution of natural language.
- This formation and evolution process is one of complementary context and content creation and change.
- the present invention emulates this natural language creation process by organizing computer software and structuring document cooperation along these same lines. Hence, context and content creation are always separate activities. Since natural language creation and change is the real world's multiply authored document, then the computer tractable representation of this process, which is the present invention, is therefore the multiply authored document using computer software.
- the present invention ties document integrity to the atomic semantic node instead of to the file.
- atomic semantic node instead of to the file.
- the overall result is a set of mutually exclusive yet atomic semantic document work areas, whose semantic sum is an entire coherent topic.
- Markup languages allow implicit document structure to become computer processable. But structure and context are supposed to be invisible when producing natural language content. Thus, the tag artifact by its very presence is a hindrance. Current document applications usually show these tags as trees that may be made visible when the author needs orienting. Or sometimes, the current set of legal tags appear as drop-down lists from which the author may choose. The problem is that these computer control artifacts intrude on the authoring process.
- the present invention calls for standard document artifacts to be used as style representatives of unchangeable context, as differentiators of context and content, and as indicators of movement from one semantic node to another by an author.
- An example of downstream requirements intruding on the authoring process is the WYSIWYG (what you see is what you get) technology.
- WYSIWYG what you see is what you get
- Replicate documents at each site means there is no central server that can create a bottleneck. Information flow is entirely dictated by semantic and cooperation needs and requirements.
- the present invention is truly peer-to-peer because there is no need for data concurrency impositions.
- Markup today is used mainly for aggregating and syndication of information that has been tagged with tags that resemble natural language, like ⁇ vegetable>.
- the major deficiency in this approach is that it assumes the data has already been created either by a single author or by a series of single authors.
- the present invention disseminates during the creation process, which is a superset ofthe aggregation-syndication model and covers real and complete document life cycle.
- the reason current markup processes cannot include the authoring process is, there is no functionality in the aggregation syndication model for the cooperation of DTDs (see 4.2 "document type declaration"), which represent the linguistic contexts of that which is being aggregated and syndicated.
- the present invention is not a generalized editor but rather a suite of generated complementary fragment editor executables per document.
- fragment editor executables are created that function cooperatively as one implemented DTD (see 4.2 "document type declaration” and 4.30 "fragment editor executable”). Each fragment editor executable is in effect a streamlined specific node implementation ofthe DTD. The difference in efficiency using any kind of measurement is large.
- the present invention operates peer-to-peer with a replicate of the complete document at each site, the resulting authoring environment for the present invention automatically attains the goal of single author look and feel, which is not possible with the client server model which only presents to the author the node or nodes checked out for the editing task at hand.
- the more nodes checked out in the client server approach the longer other authors will have to wait to make their changes.
- it is possible to use callback to update clients in the client server model it is an extremely intensive programming approach and merely would serve to make further disjoint the activities involved in seamless collaborative authoring.
- the present invention insures that there is a constantly evolving exhaustive and mutually exclusive set of authors that cooperatively own and develop the virtual document. This is only theoretically possible using traditional database privileges. Privileges, ownership and execution behaviors of nodes in the client server document model are separate activities, whereas these characteristics in the present invention are indivisible as is necessary for virtual document integrity.
- the present invention's peer-to-peer model has lead to an efficient collaborative document authoring application without the need for a bottleneck server.
- FIG.l is a graphical representation ofthe generation of root context authors.
- FIG.2 is a hierarchy view ofthe present invention in regards to context author creating two sub-nodes.
- FIG.3 is diagrammatic view of the FIG 2 in running state.
- FIG.4 is a hierarchy view ofthe present invention in regards to a subordinate context author further creating two sub-nodes.
- FIG.5 is diagrammatic view of the FIG 4 in running state.
- FIG.6 is a view of a representative framework dialog for assigning nodes ofthe invention.
- FIG.7 is a screen view of a node's executable of invention in running state.
- FIG.8 is a screen view of FIG.7 exported as a regular SGML instance without presentation.
- Semantic grammars in linguistics are evolving natural language structures, sometimes called paradigms, held alive by practicing members of defining groups of linguistically competent humans.
- Examples of explicit standardized semantic grammars are the transaction sets and messages of EDI (electronic data interchange).
- Another example is the Merck Manual (see 5.6 "Document Evolution Illustration"). This particular semantic grammar is defined presumably by a set of authorized medical doctors, and whose structure can be implemented on a computer using standard computer science parsing techniques.
- the present invention equates a semantic grammar's node with a
- document type declaration refers to ISO 8879 standard's rules for producing document syntaxes. These document syntaxes have the potential of being human readable and therefore able to make natural language sense to the document creator. ISO 8879 insures that the produced document syntaxes are computer tractable thus guaranteeing a tie between natural language and its representation as context in a computer.
- the phrase "ordered compilation of information” refers to written text or animations sequenced in such a way as to impart coherent knowledge to a temporally perceiving literate human attempting to understand the sequence from beginning to end.
- context refers to the a priori environment within which written or spoken natural language content is produced. Although there are many parts to natural language environment context, ISO 8879 highlights the semantic hierarchy is being its most relevant representative. The DTD makes natural language context explicit and therefore computer tractable. Linguistic context is always constant when content is being produced or modified. Thus, in the instance fragment:
- a common syndrome that may be caused by many different etiologies whose clinical manifestations reflect a fundamental abnormality - - a decrease in the myocardial contractile state such that cardiac output (CO) is inadequate for the body ' s needs .
- ⁇ /HeartFailure> pieces are representation of linguistic context set in some semantic hierarchy, where the second pair is semantically subordinate to the first pair.
- the phrase "instance tag” is the computer tractable expression of context and is exemplified by the
- An "instance tag” refers exclusively to an SGML instance of a DTD (see 4.2 "document type declaration”), specifically the start and optionally end tag surrounding content.
- reaction refers to the exercise of a change request message protocol from an author to recipient. This protocol includes making the request, handling acknowledgements and eventually committing the results as irreversible. 4.8 "atomic transaction"
- atomic transaction refers to a transaction in which, if any ofthe protocol parts are not carried out properly and thus leading to inconsistent document replicas at the various sites, then actions are taken to repair the offending recipient.
- Receiving an acknowledgement from a recipient does not necessarily mean the change has been applied, but rather that the recipient application promises to either apply the change eventually or resolve the change otherwise. This allows for any number of workflow scenarios that involve multiple hop delivery of messages.
- subscriber site refers to the computer that is executing a particular subscriber application.
- document section refers to a particular node's visual representation of stylized context and content.
- recordation refers to a particular editor type site's address lists of recipients to which content and administrative change requests are sent when they occur.
- entity type refers to the roles individuals equipped with their corresponding executables can play in creating a multiply authored document.
- the phrase "subscriber type" refers to document participants whose executables allow them to at least view the document.
- root context generator refers to software that can create and deploy initial root context authors.
- the root context generator is the present invention's fragment editor generator (see 4.31 "fragment editor generator executable").
- root context author refers to an editor type executable that represents the upper most node in a document's semantic hierarchy.
- concise author refers to an editor type executable that is semantically subordinate to the root context author and optionally subordinate to other context authors, and who has the capability to change document context as well as content.
- content author refers to an editor type executable that is semantically subordinate to the root context author and optionally other context authors, who has no subordinate child nodes, and who has the capability to change document content.
- subscriber refers to a non-editor type executable that has no semantic node associated with it. Subscriber types can be created by editor types as well as by other subscribers if permitted. 4.20 "node"
- node refers to an SGML element that is a single natural language identifier representing a linguistic semantic category, and also refers to an executable that was created specifically to perform operations that are specific to and consistent with the semantic category it represents. A node is therefore a duality of representation and operation (see 2.6 "Node Based, not File Based; Minimized False Invalidation")
- target node refers to a node executable created by an existing context author or root context author.
- sub-node refers to a node whose semantic content is subordinate to the current node.
- the phrase “descendent node” refers to and is interchangeable with a sub-node.
- replica view node refers to a node that is exactly the same as a semantic node with the same identifier at another site in the same document.
- Each editor type site's executable is an implementation ofthe node it owns, but which also contains replicates ofthe other nodes it doesn't own or can change, which therefore are for viewing.
- context author node refers to the deployed executable owned and used by its context author. 4.26 "content author node”
- content author node refers to the deployed executable owned and used by its content author.
- inventional writing behaviors includes the abilities to indent, outline, summarize, illustrate, partition text into coherent sequential paragraphs, sections and chapters, as well as the abilities to choose and utilize common structural visual cues that signal document structure, such cues including but not limited to visual textual cues such as indenting, numbering, shading, coloring, bold, italics and underline.
- structured editor refers to a word processor that uses a DTD instead ofthe individual character to guide the user in the editing process.
- generalized structured editor refers to a structured editor that has the ability to accept, compile and utilize a large variety of structures, the most popular of which is the ability to use any kind of DTD (see 4.2_"document type declaration").
- the present invention does not employ a commercial generalized structured editor, but rather is a suite of cooperating complementary fragment editors (see 4.30 "fragment editor executable”) per document each fragment of which is generated as needed.
- fragment editor executable refers to the executable for operating on a particular DTD node. 4.31 "fragment editor generator executable"
- fragment editor generator refers to executable code that can create fragment editor executables (see 4.30 "fragment editor executable") for operating on particular DTD nodes.
- Repositories are any kind of database that has a markup language superstructure.
- the reason the industry chose the word repository instead of just database is, the purpose of databases is to guarantee the integrity ofthe internal data.
- repositories are able to signify that markup components and elements have been checked out ofthe database, it cannot guarantee their consistency with respect to the rest ofthe internal database information. Updates in repositories are carried out at the client, whereas, updates in databases are carried out on the server.
- the name repository signifies this difference, which makes its utility more like a software configuration management system.
- a preferred embodiment ofthe present invention is a syntax- directed application comprising a root context generator and a root context author, and optionally comprising one or more selected from the group consisting of a context author, a content author and a subscriber. With all components running in tandem, the application functions as a distributed language-based word processor. The invention allows each author to work on his or her section ofthe document while viewing concurrently the changes of other authors working on the same virtual document.
- SGML is a generic set of keywords, naming syntax, occurrence and connector terms structured in such a way that the document structure designer uses them to express literally any real world set of natural language semantic notions in a notation that computers can process.
- the DTD is the computer-processable coherent expression of such language.
- SGML can produce an infinite number of DTDs.
- multiple authors cooperatively comprise a single SGML DTD.
- This common DTD is not a tangible computer object or shared memory anywhere, but is rather the sum of the effect of the deployed editor type executables.
- the sum of the deployed nodes is equal to the implementation of a single DTD.
- This single DTD defines the context in which each author works. Because a single virtual DTD is cooperatively used, with the exception of styling, the context remains identical at each authoring site. Depending on their ability types, authors cooperatively expand and grow the virtual DTD until the semantic area is deemed exhausted by the authors and privilege grantors. When all context and content creation privileges have been revoked for all nodes, the virtual distributed document is deemed complete.
- the present invention implements the DTD prescription for a group of document writers, enabling each of them to simultaneously produce changes in content on a mutually exclusive and exhaustive basis with respect to the DTD all the while viewing text content and context from the whole document simultaneously.
- the invention connects the underlying grammatical structure invisibly to the author's conventional writing behaviors by tying currently accepted text styles to the grammar at the time when the executable document is created. DTD instance tags are therefore never visible to the author or subscriber, but rather context meaning is redirected through styling cues. This process of context styling is analogous to what occurs for natural language documents.
- a preferred embodiment of present invention comprises five entity types each with differing capabilities.
- the five entity types are (1) root context generator, (2) root context author, (3) context author, and (4) content author and (5) subscriber.
- the types are causally related. Each type has capabilities, privileges and supplementary code behaviors that are predefined at creation time, but that are modifiable at runtime.
- These entity types are further classed into two overall types: editor type and subscriber type.
- the root context author, context authors and content authors are all editor types. All editor types are assigned nodes, and all editor types are capable of editing document content.
- the root context author and context authors are capable of creating and modifying context by creating or changing sub-nodes as well.
- a subscriber type unlike all editor types, is not assigned a particular node and is therefore a non-editor type. Subscribers are considered third parties and thus are only able to witness the evolution ofthe document.
- a section is a node's visual representation of stylized context and content. It is possible with the invention for a node to grant to any and all of its descendent nodes access to none ofthe document or the whole document, or any portion thereof.
- All editor types have the ability to edit content of their node.
- Content refers to text material between SGML instance start and end tags.
- all entity types are supplied with read-only privileges.
- the stylized expression of context always occurs only at node creation time. Consequently, no node recipient may alter the context cues ofthe received node.
- context exists prior to the exercise of producing language content. Only the root context author can set the initial style ofthe context representation portions ofthe document. Subordinate context authors may modify the initial style only within permitted bounds, and their modifications are limited to newly created sub-nodes.
- the Node The node and its semantic relationships to its parent and children represent language context.
- the DTD keeps these relationships straight all the while allowing the representation to be computer tractable.
- a node is the computer address ofthe author and it is a semantic element identifiable in the DTD.
- a node comprises executable code that embodies the abilities with which it was created.
- the root context author and context authors have the capability of creating and assigning new semantically descendent portions ofthe document to new authors.
- Node creation is the atomic act of semantically further differentiating the creator's node, creating the executable code for the new node and forwarding the code to the target author.
- the new author is granted reading and writing privileges for the content of that new node.
- Each creation and assignment results either in the creation of a context author or the creation of a content author.
- context authors can create new semantically subordinate context authors and content authors. Content authors do not have this ability.
- Any author node or subscriber has the innate ability to create another subscriber, although this privilege may be revoked at runtime or the ability simply may not be provided at code creation time.
- a subscriber does not own a particular node.
- An author may own and operate more than one node. He may also administrate directly any sub-node or alternatively grant or revoke privileges for subordinate nodes to carry out some or all of his tasks.
- Any implementation algorithm employing supplementary code may be utilized for effecting authoring control over particular occurrences of multiply occurring content groups ("content groups" is an SGML term) or elements as SGML occurrence indicators may permit, that is, *, + and ?, as long as the algorithm doesn't compromise the node owner's basic ownership rights.
- Selecting a new sub-node is the same process that occurs when selecting a new node using a DTD editor. 5.4.2.2 Design User Interface
- the user interface enables the authors to orient themselves visually with respect to the context ofthe entire document, and it enables authors to enter content edits in the assigned content area ofthe document.
- the user interface's visual structural cues for the new node should complement the rest ofthe document. Creating the user interface involves selection of visual structural cues from within the privileges and parameters inherited from ancestral nodes. This selection process results in executable code in the target source. Other ownership and network connection information is collected.
- user visual cue and action preferences for indicating beginnings and endings of document parts or indicating completion of edit changes to a document part, are extracted from the creator using standard dialog sessions.
- this signaling process is part of the user interface stylization and follows normal document writing cues that indicate the author is leaving or entering a changed area. Since change of context does not occur at run time, there are no actions but only visual cues that serve to orient the user with respect to the document structure.
- New context authors have the ability to design user interfaces for any new sub-nodes they may create. New content authors do not have this ability.
- the node creator may grant any set of privileges or endow it with any capabilities that were inherited at its creation time. This set of privileges and capabilities may be altered or revoked or modified at runtime by its ancestor nodes. New context authors have the ability to set privileges and bequeath behaviors to new sub-nodes they may create. New content authors do not have this ability.
- Node Deployment Context author nodes are able to deploy the new executable code to the new author's computer. Furthermore, subsequently created context author nodes contain the ability to deploy executables that they may create to any new sub-nodes they may create. Content authors do not have this capability.
- the final step is updating the current authors and subscribers with the new section in the document that this node represents. Without acknowledgement that all these steps have successfully taken place, none of the new code will be activated and rollback to the previous document state must take place.
- a newly added node executable includes by default the ability to receive the content changes from any and all other nodes. This applies to all editor types and subscribers.
- a newly created author node includes by default the ability to push content changes to the list of all node authors and subscribers. This applies to editor types.
- a newly created editor node includes by default the ability to accept and add to its distribution list, subsequently added author addresses to which the newly created editor node will send changes. This applies to editor types.
- the present invention embodies two separate but simultaneous growth and change paths, which parallels the way natural language behaves.
- One path is simultaneous context change and the other is simultaneous content change.
- Change in general encompasses creation, modification, deletion, granting and revoking document parts and characteristics.
- Context authors simultaneously create new and alter sub- nodes, and context and content authors create and alter content.
- the first step ofthe invention is to create executable computer code for the root context author.
- a topic is selected for the root node, context stylization is set to default parameters, and an executable is generated and deployed to the target root context author.
- DTD change control is eventually hierarchically distributed to all context authors, or it may be kept centrally at the root context author, or control may be hierarchically distributed to any degree in between.
- the root context author may create any number of semantically and privilege-wise subordinate node executables.
- the root context author modifies the default context stylization and even the root node name if desired. Any privileges and behaviors that are deemed necessary for the authors to successfully write the distributed document are added to the executable. After being configured for a particular sub-node during the sub-node creation process, it is this set of privileges and behaviors that sub-node executables are endowed with when they get created. 5.5.3 Context Author
- the context author may only further configure context stylization, privileges and software behaviors for the sub- nodes that it creates.
- Context authors may create any number of semantically and privilege-wise subordinate node executables.
- Context authors may create or edit content any number of times.
- Content authors may create or edit content any number of times.
- FIG.l is a graphical representation ofthe generation of a root context author at time zero.
- the root context generator (8) generates a root context author to begin the document generation process. (10) points to one of four root context author executables it has generated.
- FIG.2 is a hierarchy view ofthe present invention illustrating time one in this illustration document's life. For generality's sake shapes have been substituted for named nodes. A thick node border denotes a context author node and a thin border a content author node. Since subscribers do not own nodes, they have not been included in order to reduce complexity.
- context node 10a has created content author sub-node 12a and a context author sub-node 14a. Between time zero and time one, two context changes have occurred.
- FIG.3 illustrates FIG.2 in running state with the created nodes deployed as executables 10b, 12b and 14b. Each author executable contains all three nodes. Three content changes have occurred since time one resulting in 6 content messages to the other executables at their sites.
- FIG.4 is a hierarchy view ofthe illustration document at time two. Between time one and time two, context author 14b has further differentiated its node 14a into two content author sub-nodes 16a and 18a.
- FIG.5 illustrates FIG.4 in running state with the created nodes deployed as executables 10b, 12b, 14b, 16b and 18b.
- Each author executable now contains all five nodes.
- Each author has made one content change since time two resulting in 20 content messages to the other executables at their sites.
- FIG.6 is a diagrammatic view ofthe present invention for illustration purposes.
- the root context author MerckManual (30) has already created sub-nodes Cardiovascular (32) and Pulmonary (34).
- PatientApproach (48) and PulmonaryTests (50) nodes were created either by MerckManual (30) or Pulmonary (34).
- Cardiovascular (32) or MerckManual (30) has already created ExerciseHeart (40) and
- dialog box (54) shows three pieces of information being requested.
- (56) asks for the text literal that is to replace the node start tag.
- (58) asks for the author's name and their net address (59) (i.e. IP address, network address).
- FIG.7 is an example of an author's document seen at runtime.
- the node name is Cardiovascular (32) whose literal read-only context representation is "Diseases ofthe Heart and Pericardium” (72) and whose content (66) is read-writable as indicated by the cursor (68).
- Other content areas, (60), (62) and (64) are read-only since they are not owned by this node.
- FIG.8 (80) shows FIG.7 after being exported as a regular SGML instance without tag literals or other presentation artifacts.
- the beginning step of the method is to create executable computer code that has the ability to create root context authors.
- the executable code ofthe root context generator has the ability to create root context editor types, wherein said root context generator has at least the following abilities: (1) the ability to create root node associated executable code for root context authors; and (2) the ability to distribute said executable code through a communication medium to target root context authors.
- This root context author is the uppermost semantic node in the document and is of editor type.
- the executable computer code underlying the root context author includes computer code that has at least the following abilities: (3) the ability to maintain and update a recordation or list of each node added to the document; (4) the ability to generate an initial user interface that can receive and display the context and content changes of a document from all the other current and eventual nodes in the document; (5) the ability to propagate content changes from its own node to all other replicate view nodes in the distributed document; (6) the ability to create executable code for semantically subordinate nodes, wherein the node type is selected from a group consisting of context author and content author; (7) the ability to distribute the resulting executable code through a communication medium to the targeted author; (8) the ability to create executable code for a subscriber; (9) the ability to distribute the resulting subscriber executable code through a communication medium to the targeted subscriber; (l ⁇ )the ability to create, configure and supervise descendent node user interfaces, descendent node privilege
- the executable computer code underlying the context author includes computer code that has at least the following abilities: (12) the ability to maintain and update a recordation or list of each node added to the document; (13) the ability to display a user interface that can receive and display the context and content changes of a document from all the other current and eventual nodes in the document; (14) the ability to propagate content changes from its own node to all other replicate view nodes in the distributed document; (15) the ability to respond to administrative requests; (16) the ability to create executable code for semantically subordinate nodes, wherein the node type is selected from a group consisting of context author and content author; (17) the ability to distribute the resulting executable code through a communication medium to the targeted author;
- Subordinate nodes can inherit those abilities that can be granted and revoked by super-ordinate nodes both at creation time and at execute time.
- the user interface enables the author to enter content edits in an assigned area ofthe document.
- root context author and the context authors share many ofthe same characteristics.
- a document may have multiple context authors, in a preferred embodiment, a document only has one root context author.
- root context authors create their own initial user interfaces and sets of supplementary code while a context author can at most only modify inherited capabilities.
- context authors respond to administrative commands, while root context authors reside at the top ofthe semantic hierarchy, and thus do not respond to such administrative commands.
- creation of a subordinate editor type by a context author or the root context author is the first step in a method to create context change. Once a subordinate editor type has been created, editor type authors can perform all other steps ofthe method to create context change in any order and at any time.
- the executable computer code underlying the content author includes computer code that has at least the following abilities: (22) the ability to maintain and update a recordation or list of each node added to the document; (23) the ability to display a user interface that can receive and display the context and content changes of a document from all the other current and eventual nodes in the document; (24) the ability to propagate content changes from its own node to all other replicate view nodes in the distributed document; (25) the ability to respond to administrative requests; (26)the ability to create executable code for a subscriber; (27) the ability to distribute through a communication medium the resulting subscriber executable code to the targeted subscriber; and (28) the ability to populate the document at startup.
- the user interface enables the author to enter content edits in an assigned area ofthe document.
- Any editor type can perform the step ofthe method to create and propagate content change at any time and in any order.
- Another step in the method ofthe invention is the creating of executable computer code for subscribers. Subscribers are not associated with any node and they do not have the ability to create further subordinate nodes.
- the executable computer code underlying the subscriber includes computer code that has at least the following abilities: (29) the ability to display a user interface that can receive and display the context and content changes of a document from all the other current and eventual nodes in the document; (30) the ability to respond to administrative requests; and (31) the ability to populate the document at startup.
- Any document participant including editor types or subscribers who have the proper privileges, can perform the step ofthe method to create subscribers at any time.
- a quiescent document of this invention is a document all of whose change messages have been delivered.
- the system comprises executable computer code that has the ability to create root context authors.
- the executable code ofthe root context generator has the ability to create root context editor types, wherein said root context generator has at least the following abilities: (1) the ability to create root node associated executable code for root context authors; and (2) the ability to distribute said executable code through a communication medium to target root context authors.
- This root context author is the uppermost semantic node in the document and is of editor type.
- the executable computer code underlying the root context author includes computer code that has at least the following abilities: (3) the ability to maintain and update a recordation or list of each node added to the document; (4) the ability to generate an initial user interface that can receive and display the context and content changes of a document from all the other current and eventual nodes in the document; (5) the ability to propagate content changes from its own node to all other replicate view nodes in the distributed document; (6) the ability to create executable code for semantically subordinate nodes, wherein the node type is selected from a group consisting of context author and content author; (7) the ability to distribute the resulting executable code through a communication medium to the targeted author; (8) the ability to create executable code for a subscriber; (9) the ability to distribute the resulting subscriber executable code through a communication medium to the targeted subscriber; (10) the ability to create, configure and supervise descendent node user interfaces, descendent node privileges and
- Subordinate nodes can inherit said abilities that can be granted and revoked by super-ordinate nodes both at creation time and at execute time.
- the user interface enables the author to enter content edits in an assigned area ofthe document.
- the system further comprises executable code for a context author.
- the executable computer code underlying the context author includes computer code that has at least the following abilities: (12) the ability to maintain and update a recordation or list of each node added to the document; (13) the ability to display a user interface that can receive and display the context and content changes of a document from all the other current and eventual nodes in the document; (14) the ability to propagate content changes from its own node to all other replicate view nodes in the distributed document; (15) the ability to respond to administrative requests; (16) the ability to create executable code for semantically subordinate nodes, wherein the node type is selected from a group consisting of context author and content author; (17) the ability to distribute the resulting executable code through a communication medium to the targeted author; (18) the ability to create executable code for a subscriber; (19) the ability to distribute the resulting subscriber executable code through a communication medium to the targeted subscriber; (20) the ability to create, configure and supervise descendent node user interfaces, descendent node privileges and descendent node supplementary computer code; and (21)
- Subordinate nodes can inherit those abilities that can be granted and revoked by super- ordinate nodes both at creation time and at execute time.
- the user interface enables the author to enter content edits in an assigned area ofthe document.
- the root context author and the context authors share many ofthe same characteristics. However, while a document may have multiple context authors, in a preferred embodiment, a document only has one root context author.
- root context authors create their own initial user interfaces and sets of supplementary code while a context author can at most only modify inherited capabilities.
- context authors respond to administrative commands, while root context authors reside at the top ofthe semantic hierarchy, and thus do not respond to such administrative commands.
- the system creates context change by first creating subordinate editor type by a context author or the root context author. Once a subordinate editor type has been created, editor type authors create context change in any order and at any time.
- the system is capable of creating executable computer code for a content author.
- Content authors are always leaf nodes in the semantic hierarchy because they do not have the ability to create further subordinate nodes. Leaf nodes have no children nodes subordinate to them.
- the executable computer code underlying the content author includes computer code that has at least the following abilities: (22) the ability to maintain and update a recordation or list of each node added to the document; (23) the ability to display a user interface that can receive and display the context and content changes of a document from all the other cu ⁇ ent and eventual nodes in the document; (24) the ability to propagate content changes from its own node to all other replicate view nodes in the distributed document; (25) the ability to respond to administrative requests; (26) the ability to create executable code for a subscriber; (27) the ability to distribute through a communication medium the resulting subscriber executable code to the targeted subscriber; and (28) the ability to populate the document at startup.
- the user interface enables the author to enter content edits in an assigned area ofthe document.
- any editor type can create and propagate content change at any time and in any order.
- the system is capable of creating executable computer code for subscribers. Subscribers are not associated with any node and they do not have the ability to create further subordinate nodes.
- the executable computer code underlying the subscriber includes computer code that has at least the following abilities: (29) the ability to display a user interface that can receive and display the context and content changes of a document from all the other cu ⁇ ent and eventual nodes in the document; (30) the ability to respond to administrative requests; and (31) the ability to populate the document at startup.
- Any document participant including editor types or subscribers who have the proper privileges, can create subscribers at any time.
- populating the document must necessarily be the first act of any site's executable code. After populating a site's document, it is refe ⁇ ed to as being consistent. The only other time a document replica is not consistent is during change transmission times or if supplementary work flow type code deliberately delays or redirects change messages before they reach their destination.
- a quiescent document of this invention is a document all of whose change messages have been delivered.
Abstract
Description
Claims
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2002324778A AU2002324778B2 (en) | 2001-08-31 | 2002-08-26 | Method and system for producing an ordered compilation of information with multiple authors contributing information contemporaneously |
EP02759443A EP1430409B1 (en) | 2001-08-31 | 2002-08-26 | Method and system for producing an ordered compilation of information with multiple authors contributing information contemporaneously |
AT02759443T ATE488819T1 (en) | 2001-08-31 | 2002-08-26 | METHOD AND SYSTEM FOR PRODUCING AN ORDERED COMPETITION OF INFORMATION WITH SEVERAL AUTHORS CONTRIBUTING INFORMATION AT THE SAME TIME |
DE60238337T DE60238337D1 (en) | 2001-08-31 | 2002-08-26 | METHOD AND SYSTEM FOR PRODUCING A SETUP OF INFORMATION WITH MULTIPLE, AUTHORIZED AUTHORS AT THE SAME TIME |
DK02759443.1T DK1430409T3 (en) | 2001-08-31 | 2002-08-26 | Process and system for generating an orderly compilation of information with multiple authors contributing information simultaneously |
CA2458860A CA2458860C (en) | 2001-08-31 | 2002-08-26 | Method and system for producing an ordered compilation of information with multiple authors contributing information contemporaneously |
HK04107219.6A HK1064477A1 (en) | 2001-08-31 | 2004-09-20 | Method and system for producing an ordered compilation of information with multiple authors contributing information contemporaneously |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/944,131 | 2001-08-31 | ||
US09/944,131 US7124362B2 (en) | 2001-08-31 | 2001-08-31 | Method and system for producing an ordered compilation of information with more than one author contributing information contemporaneously |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2003021458A1 true WO2003021458A1 (en) | 2003-03-13 |
Family
ID=25480843
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2002/026937 WO2003021458A1 (en) | 2001-08-31 | 2002-08-26 | Method and system for producing an ordered compilation of information with multiple authors contributing information contemporaneously |
Country Status (11)
Country | Link |
---|---|
US (1) | US7124362B2 (en) |
EP (1) | EP1430409B1 (en) |
CN (1) | CN1547709A (en) |
AT (1) | ATE488819T1 (en) |
AU (1) | AU2002324778B2 (en) |
CA (1) | CA2458860C (en) |
DE (1) | DE60238337D1 (en) |
DK (1) | DK1430409T3 (en) |
ES (1) | ES2356730T3 (en) |
HK (1) | HK1064477A1 (en) |
WO (1) | WO2003021458A1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1854056A1 (en) * | 2005-02-08 | 2007-11-14 | UBQ'S Business, S.A. | Systems and methods for sharing information between a user group and associated document |
EP1946261A2 (en) * | 2005-08-29 | 2008-07-23 | Sony Corporation | Portfolios in disc authoring |
US8213771B2 (en) | 2005-08-29 | 2012-07-03 | Sony Corporation | Templatized commands in disc authoring |
CN107633468A (en) * | 2016-07-18 | 2018-01-26 | 上海颐学网络科技有限公司 | A kind of guidance method and system of shared information point structure |
Families Citing this family (67)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2385686A (en) * | 2002-02-25 | 2003-08-27 | Oracle Corp | Mark-up language conversion |
US7614081B2 (en) * | 2002-04-08 | 2009-11-03 | Sony Corporation | Managing and sharing identities on a network |
US7478126B2 (en) | 2002-04-08 | 2009-01-13 | Sony Corporation | Initializing relationships between devices in a network |
US7987246B2 (en) | 2002-05-23 | 2011-07-26 | Jpmorgan Chase Bank | Method and system for client browser update |
US9940401B2 (en) * | 2002-11-18 | 2018-04-10 | Oath Inc. | Buddy share |
GB2409541A (en) * | 2003-12-23 | 2005-06-29 | Mandorla Technology Ltd | Editable information management system and method |
US7437709B2 (en) * | 2004-02-19 | 2008-10-14 | International Business Machines Corporation | Providing assistance for editing markup document based on inferred grammar |
US20070203589A1 (en) * | 2005-04-08 | 2007-08-30 | Manyworlds, Inc. | Adaptive Recombinant Process Methods |
JP2006260546A (en) * | 2005-03-15 | 2006-09-28 | Oce Technologies Bv | Document management system |
US20070016650A1 (en) * | 2005-04-01 | 2007-01-18 | Gilbert Gary J | System and methods for collaborative development of content over an electronic network |
US7924285B2 (en) * | 2005-04-06 | 2011-04-12 | Microsoft Corporation | Exposing various levels of text granularity for animation and other effects |
US8280882B2 (en) * | 2005-04-21 | 2012-10-02 | Case Western Reserve University | Automatic expert identification, ranking and literature search based on authorship in large document collections |
US8065606B1 (en) * | 2005-09-16 | 2011-11-22 | Jpmorgan Chase Bank, N.A. | System and method for automating document generation |
CN1979466A (en) * | 2005-11-29 | 2007-06-13 | 国际商业机器公司 | Method and device for allowing multi-users to edit a shared electronic file simultaneously |
US20080126385A1 (en) * | 2006-09-19 | 2008-05-29 | Microsoft Corporation | Intelligent batching of electronic data interchange messages |
US20080126386A1 (en) * | 2006-09-20 | 2008-05-29 | Microsoft Corporation | Translation of electronic data interchange messages to extensible markup language representation(s) |
US20080071806A1 (en) * | 2006-09-20 | 2008-03-20 | Microsoft Corporation | Difference analysis for electronic data interchange (edi) data dictionary |
US8108767B2 (en) * | 2006-09-20 | 2012-01-31 | Microsoft Corporation | Electronic data interchange transaction set definition based instance editing |
US8161078B2 (en) * | 2006-09-20 | 2012-04-17 | Microsoft Corporation | Electronic data interchange (EDI) data dictionary management and versioning system |
US20080086463A1 (en) * | 2006-10-10 | 2008-04-10 | Filenet Corporation | Leveraging related content objects in a records management system |
US8688992B2 (en) * | 2006-11-02 | 2014-04-01 | Recombo, Inc. | System and method for generating agreements |
US20080168109A1 (en) * | 2007-01-09 | 2008-07-10 | Microsoft Corporation | Automatic map updating based on schema changes |
US20080168081A1 (en) * | 2007-01-09 | 2008-07-10 | Microsoft Corporation | Extensible schemas and party configurations for edi document generation or validation |
US7937663B2 (en) * | 2007-06-29 | 2011-05-03 | Microsoft Corporation | Integrated collaborative user interface for a document editor program |
US7933952B2 (en) * | 2007-06-29 | 2011-04-26 | Microsoft Corporation | Collaborative document authoring |
US20090049374A1 (en) * | 2007-08-16 | 2009-02-19 | Andrew Echenberg | Online magazine |
US7941399B2 (en) | 2007-11-09 | 2011-05-10 | Microsoft Corporation | Collaborative authoring |
US8825758B2 (en) | 2007-12-14 | 2014-09-02 | Microsoft Corporation | Collaborative authoring modes |
US8301588B2 (en) | 2008-03-07 | 2012-10-30 | Microsoft Corporation | Data storage for file updates |
US8666729B1 (en) * | 2010-02-10 | 2014-03-04 | West Corporation | Processing natural language grammar |
US8352870B2 (en) | 2008-04-28 | 2013-01-08 | Microsoft Corporation | Conflict resolution |
US8429753B2 (en) | 2008-05-08 | 2013-04-23 | Microsoft Corporation | Controlling access to documents using file locks |
US8825594B2 (en) | 2008-05-08 | 2014-09-02 | Microsoft Corporation | Caching infrastructure |
US8417666B2 (en) | 2008-06-25 | 2013-04-09 | Microsoft Corporation | Structured coauthoring |
US8286171B2 (en) | 2008-07-21 | 2012-10-09 | Workshare Technology, Inc. | Methods and systems to fingerprint textual information using word runs |
US7930447B2 (en) | 2008-10-17 | 2011-04-19 | International Business Machines Corporation | Listing windows of active applications of computing devices sharing a keyboard based upon requests for attention |
US8346768B2 (en) | 2009-04-30 | 2013-01-01 | Microsoft Corporation | Fast merge support for legacy documents |
US8370628B2 (en) * | 2009-07-16 | 2013-02-05 | Oracle International Corporation | Document collaboration system with alternative views |
US8515960B2 (en) * | 2009-10-29 | 2013-08-20 | Microsoft Corporation | Aggregating content from multiple content contributors |
US8386239B2 (en) | 2010-01-25 | 2013-02-26 | Holovisions LLC | Multi-stage text morphing |
US10025759B2 (en) | 2010-11-29 | 2018-07-17 | Workshare Technology, Inc. | Methods and systems for monitoring documents exchanged over email applications |
US10783326B2 (en) * | 2013-03-14 | 2020-09-22 | Workshare, Ltd. | System for tracking changes in a collaborative document editing environment |
US10853319B2 (en) | 2010-11-29 | 2020-12-01 | Workshare Ltd. | System and method for display of document comparisons on a remote device |
US9038177B1 (en) | 2010-11-30 | 2015-05-19 | Jpmorgan Chase Bank, N.A. | Method and system for implementing multi-level data fusion |
US9727538B2 (en) * | 2010-12-10 | 2017-08-08 | International Business Machines Corporation | Editing a fragmented document |
US9613340B2 (en) | 2011-06-14 | 2017-04-04 | Workshare Ltd. | Method and system for shared document approval |
US10963584B2 (en) | 2011-06-08 | 2021-03-30 | Workshare Ltd. | Method and system for collaborative editing of a remotely stored document |
US10108928B2 (en) | 2011-10-18 | 2018-10-23 | Dotloop, Llc | Systems, methods and apparatus for form building |
US9158746B2 (en) * | 2012-06-13 | 2015-10-13 | International Business Machines Corporation | Managing concurrent editing in a collaborative editing environment using cursor proximity and a delay |
US10826951B2 (en) * | 2013-02-11 | 2020-11-03 | Dotloop, Llc | Electronic content sharing |
US9575622B1 (en) | 2013-04-02 | 2017-02-21 | Dotloop, Llc | Systems and methods for electronic signature |
US10552525B1 (en) | 2014-02-12 | 2020-02-04 | Dotloop, Llc | Systems, methods and apparatuses for automated form templating |
EP3193261B1 (en) * | 2014-03-18 | 2020-11-04 | smartwork solutions GmbH | Method and system for editing virtual documents |
US9860578B2 (en) * | 2014-06-25 | 2018-01-02 | Google Inc. | Methods, systems, and media for recommending collaborators of media content based on authenticated media content input |
US9779073B2 (en) | 2014-07-29 | 2017-10-03 | Microsoft Technology Licensing, Llc | Digital document change conflict resolution |
US10733364B1 (en) | 2014-09-02 | 2020-08-04 | Dotloop, Llc | Simplified form interface system and method |
US9292482B1 (en) | 2015-04-30 | 2016-03-22 | Workiva Inc. | System and method for convergent document collaboration |
US10325014B2 (en) | 2015-04-30 | 2019-06-18 | Workiva Inc. | System and method for convergent document collaboration |
US10558679B2 (en) * | 2016-02-10 | 2020-02-11 | Fuji Xerox Co., Ltd. | Systems and methods for presenting a topic-centric visualization of collaboration data |
CN108847852B (en) * | 2018-06-08 | 2019-10-01 | 中国人民解放军国防科技大学 | SCA-based domain configuration file parser and use method thereof |
US11755825B2 (en) | 2019-09-12 | 2023-09-12 | Workiva Inc. | Method, system, and computing device for facilitating private drafting |
CN111723557A (en) * | 2020-06-30 | 2020-09-29 | 北京来也网络科技有限公司 | AI-based language fragment editing method, device, equipment and storage medium |
US11443108B2 (en) | 2020-08-17 | 2022-09-13 | Workiva Inc. | System and method for document management using branching |
US11100281B1 (en) | 2020-08-17 | 2021-08-24 | Workiva Inc. | System and method for maintaining links and revisions |
US11100277B1 (en) | 2021-02-15 | 2021-08-24 | Workiva Inc. | Systems, methods, and computer-readable media for flow-through formatting for links |
US11354362B1 (en) | 2021-05-06 | 2022-06-07 | Workiva Inc. | System and method for copying linked documents |
US11640495B1 (en) | 2021-10-15 | 2023-05-02 | Workiva Inc. | Systems and methods for translation comments flowback |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5146552A (en) * | 1990-02-28 | 1992-09-08 | International Business Machines Corporation | Method for associating annotation with electronically published material |
US5245553A (en) | 1989-12-14 | 1993-09-14 | Options Unlimited Research | Full-duplex video communication and document generation system |
US5671428A (en) * | 1991-08-28 | 1997-09-23 | Kabushiki Kaisha Toshiba | Collaborative document processing system with version and comment management |
US5907837A (en) * | 1995-07-17 | 1999-05-25 | Microsoft Corporation | Information retrieval system in an on-line network including separate content and layout of published titles |
US6061697A (en) | 1996-09-11 | 2000-05-09 | Fujitsu Limited | SGML type document managing apparatus and managing method |
US6088702A (en) | 1998-02-25 | 2000-07-11 | Plantz; Scott H. | Group publishing system |
WO2000062220A1 (en) | 1999-04-13 | 2000-10-19 | Ilumin Corporation | Collaborative creation, editing, reviewing, and signing of electronic documents |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4853843A (en) * | 1987-12-18 | 1989-08-01 | Tektronix, Inc. | System for merging virtual partitions of a distributed database |
US5297279A (en) * | 1990-05-30 | 1994-03-22 | Texas Instruments Incorporated | System and method for database management supporting object-oriented programming |
US5307456A (en) * | 1990-12-04 | 1994-04-26 | Sony Electronics, Inc. | Integrated multi-media production and authoring system |
US5339388A (en) * | 1991-12-31 | 1994-08-16 | International Business Machines Corporation | Cursor lock region |
US5337407A (en) * | 1991-12-31 | 1994-08-09 | International Business Machines Corporation | Method and system for identifying users in a collaborative computer-based system |
US5805897A (en) * | 1992-07-31 | 1998-09-08 | International Business Machines Corporation | System and method for remote software configuration and distribution |
US5515491A (en) * | 1992-12-31 | 1996-05-07 | International Business Machines Corporation | Method and system for managing communications within a collaborative data processing system |
US5764731A (en) * | 1994-10-13 | 1998-06-09 | Yablon; Jay R. | Enhanced system for transferring, storing and using signaling information in a switched telephone network |
US6047288A (en) * | 1995-07-20 | 2000-04-04 | Canon Kabushiki Kaisha | Group environment setting method and system thereof to provide an equivalent environment for plural participants |
US5805597A (en) * | 1996-06-04 | 1998-09-08 | National Semiconductor Corporation | Method and apparatus for providing low power basic telephony type service over a twisted pair ethernet physical layer |
WO1998037473A2 (en) * | 1997-02-07 | 1998-08-27 | General Internet, Inc. | Collaborative internet data mining system |
US5966512A (en) * | 1997-06-05 | 1999-10-12 | International Business Machines Corporation | Groupware save operation |
US6519603B1 (en) * | 1999-10-28 | 2003-02-11 | International Business Machine Corporation | Method and system for organizing an annotation structure and for querying data and annotations |
US6563800B1 (en) * | 1999-11-10 | 2003-05-13 | Qualcomm, Inc. | Data center for providing subscriber access to data maintained on an enterprise network |
US7152220B2 (en) * | 1999-12-09 | 2006-12-19 | Sensemaking Technologies Corp. | Collaboration engine: adding collaboration functionality to computer software |
US6802022B1 (en) * | 2000-04-14 | 2004-10-05 | Stratus Technologies Bermuda Ltd. | Maintenance of consistent, redundant mass storage images |
US20020016935A1 (en) * | 2000-04-14 | 2002-02-07 | Bjorn Bergsten | Method and apparatus for scanning records |
US20020152244A1 (en) * | 2000-12-22 | 2002-10-17 | International Business Machines Corporation | Method and apparatus to dynamically create a customized user interface based on a document type definition |
-
2001
- 2001-08-31 US US09/944,131 patent/US7124362B2/en not_active Expired - Lifetime
-
2002
- 2002-08-26 ES ES02759443T patent/ES2356730T3/en not_active Expired - Lifetime
- 2002-08-26 WO PCT/US2002/026937 patent/WO2003021458A1/en not_active Application Discontinuation
- 2002-08-26 AT AT02759443T patent/ATE488819T1/en not_active IP Right Cessation
- 2002-08-26 EP EP02759443A patent/EP1430409B1/en not_active Expired - Lifetime
- 2002-08-26 CA CA2458860A patent/CA2458860C/en not_active Expired - Fee Related
- 2002-08-26 DE DE60238337T patent/DE60238337D1/en not_active Expired - Lifetime
- 2002-08-26 CN CNA028165853A patent/CN1547709A/en active Pending
- 2002-08-26 DK DK02759443.1T patent/DK1430409T3/en active
- 2002-08-26 AU AU2002324778A patent/AU2002324778B2/en not_active Ceased
-
2004
- 2004-09-20 HK HK04107219.6A patent/HK1064477A1/en not_active IP Right Cessation
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5245553A (en) | 1989-12-14 | 1993-09-14 | Options Unlimited Research | Full-duplex video communication and document generation system |
US5146552A (en) * | 1990-02-28 | 1992-09-08 | International Business Machines Corporation | Method for associating annotation with electronically published material |
US5671428A (en) * | 1991-08-28 | 1997-09-23 | Kabushiki Kaisha Toshiba | Collaborative document processing system with version and comment management |
US5907837A (en) * | 1995-07-17 | 1999-05-25 | Microsoft Corporation | Information retrieval system in an on-line network including separate content and layout of published titles |
US6061697A (en) | 1996-09-11 | 2000-05-09 | Fujitsu Limited | SGML type document managing apparatus and managing method |
US6088702A (en) | 1998-02-25 | 2000-07-11 | Plantz; Scott H. | Group publishing system |
WO2000062220A1 (en) | 1999-04-13 | 2000-10-19 | Ilumin Corporation | Collaborative creation, editing, reviewing, and signing of electronic documents |
Non-Patent Citations (1)
Title |
---|
"CCDES - a collaborative compound document editing system", CHIEN-HUNG LIN, COMPUTER COMMUNICATIONS, vol. 19, 1996, pages 590 - 596 |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1854056A1 (en) * | 2005-02-08 | 2007-11-14 | UBQ'S Business, S.A. | Systems and methods for sharing information between a user group and associated document |
EP1946261A2 (en) * | 2005-08-29 | 2008-07-23 | Sony Corporation | Portfolios in disc authoring |
EP1946261A4 (en) * | 2005-08-29 | 2010-06-16 | Sony Corp | Portfolios in disc authoring |
US8213771B2 (en) | 2005-08-29 | 2012-07-03 | Sony Corporation | Templatized commands in disc authoring |
US8229278B2 (en) | 2005-08-29 | 2012-07-24 | Sony Corporation | Portfolios in disc authoring |
CN107633468A (en) * | 2016-07-18 | 2018-01-26 | 上海颐学网络科技有限公司 | A kind of guidance method and system of shared information point structure |
Also Published As
Publication number | Publication date |
---|---|
CA2458860C (en) | 2011-06-14 |
ATE488819T1 (en) | 2010-12-15 |
EP1430409A1 (en) | 2004-06-23 |
CA2458860A1 (en) | 2003-03-13 |
AU2002324778A1 (en) | 2003-03-18 |
EP1430409B1 (en) | 2010-11-17 |
US20030121008A1 (en) | 2003-06-26 |
HK1064477A1 (en) | 2005-01-28 |
DE60238337D1 (en) | 2010-12-30 |
DK1430409T3 (en) | 2011-03-07 |
EP1430409A4 (en) | 2005-11-23 |
AU2002324778B2 (en) | 2008-06-19 |
ES2356730T3 (en) | 2011-04-12 |
CN1547709A (en) | 2004-11-17 |
US7124362B2 (en) | 2006-10-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2458860C (en) | Method and system for producing an ordered compilation of information with multiple authors contributing information contemporaneously | |
Sun et al. | Transparent adaptation of single-user applications for multi-user real-time collaboration | |
US6769095B1 (en) | Hierarchically structured control information editor | |
Stein et al. | A shared view of sharing: the treaty of Orlando | |
US20080301228A1 (en) | Shared state manager and system and method for collaboration | |
Kirschenbaum | Editing the interface: Textual studies and first generation electronic objects | |
JP2002140344A (en) | Method and device for document management | |
Vitali et al. | Using versioning to provide collaboration on the WWW | |
Litt et al. | Peritext: A crdt for collaborative rich text editing | |
English et al. | An extensible, object-oriented system for active documents | |
Farquhar | Ontolingua tutorial | |
Krowne | An architecture for collaborative math and science digital libraries | |
Ravindran | Django Design Patterns and Best Practices: Industry-standard web development techniques and solutions using Python | |
Benson et al. | Cascading tree sheets and recombinant HTML: better encapsulation and retargeting of web content | |
Munson | Proteus: An Adaptable Presentation System for a Software Development and Multimedia Document Environment | |
EP3485390A1 (en) | Flexible multi-media system | |
Ratiu et al. | The reality of libraries | |
EP1208426A2 (en) | Hierarchically structured control information editor | |
Min et al. | MUCH electronic publishing environment: Principles and practices | |
Gaines et al. | Supporting collaboration in digital journal production | |
Tischer | Dynamic Syntax Compiling | |
Ignat | Maintaining consistency in collaboration over hierarchical documents | |
Benini et al. | Virtual communities as narrative processes | |
Bohøj et al. | A framework for interactively helpful web forms | |
Bernstein | Shadows in the cave: hypertext transformations |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BY BZ CA CH CN CO CR CU CZ DE DM DZ EC EE ES FI GB GD GE GH HR HU ID IL IN IS JP KE KG KP KR LC LK LR LS LT LU LV MA MD MG MN MW MX MZ NO NZ OM PH PL PT RU SD SE SG SI SK SL TJ TM TN TR TZ UA UG US UZ VN YU ZA ZM Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LU MC NL PT SE SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ UG ZM ZW AM AZ BY KG KZ RU TJ TM AT BE BG CH CY CZ DK EE ES FI FR GB GR IE IT LU MC PT SE SK TR BF BJ CF CG CI GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2002324778 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 192/DELNP/2004 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1-2004-500256 Country of ref document: PH |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20028165853 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2458860 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2002759443 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2002759443 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: JP |