ATTORNEY REFERENCE: ZS202-15366 Background

[0001] Users may be inundated with emails texts, voicemails, a nd/or other messages asking the users to perform various tasks (e.g., "call Sally at 9 am on Tuesday," "prepare report," "make reservations at Sal's on Saturday at 8," etc. ). These tasks may be

incorporated into messages in va rious ways such that users may be required to read messages carefully, and possibly re-read some messages, to ensure they fulfill or otherwise handle tasks assigned to them. If users do not create to-do lists, it may be difficult later for users to find tasks assigned to them among myriad messages in various formats (e.g., emails, texts, voicemail, etc.).

Summary

[0002] The present disclosure is generally directed to methods, apparatus a nd computer- reada ble media (transitory and non-transitory) for identifying tasks in messages and performing various responsive actions. In some implementations, a message may undergo natural language processing to generate an annotated message that includes various information, such as a nnotated parts of speech, parsed syntactic relationships, annotated entity references, clusters of references to the same entity, a nd so forth. This annotated message may be analyzed, e.g., pursuant to a grammar having one or more rule paths, to determine whether a portion of the message qualifies for classification as a task, a nd if so, what type of task it should be classified as. In va rious implementations, a suita ble user interface may be identified, and in some cases launched or opened, based on the task type classification, the annotated message output from natural language processing, and other data sources.

[0003] Classifying portions of (or entire) messages as tasks, as well as determining types of tasks, provides various technical advantages. For example, automatically classifying portions of messages as tasks may prevent the user from failing to perform tasks the user may have failed to notice in hastily-read messages, in messages that the user fails to read, and/or in messages that the user failed to comprehend completely (e.g., due to distraction, etc). Additionally, having tasks determined automatically saves users from having to revisit messages later to track down potential tasks. As another example, automatically identifying a user interface associated with fulfillment of a classified task may save the user the trouble of initiating the user interface herself and/or may increase a likelihood that the user will complete the task. Utilization of natural language processing and a grammar to identify tasks may also provide other technical advantages, such as facilitating task identification without compromising confidentiality of electronic communications. Another potential technical advantage is that overall email traffic may be reduced by virtue of less follow up emails (e.g., reminders to complete tasks) being necessary due to tasks automatically being identified.

[0004] In some implementations, a computer implemented method may be provided that includes the steps of: performing, by a computing system, natural language processing on a received message to generate an annotated message; analyzing, by the computing system, the annotated message pursuant to a grammar; and classifying, by the computing system, a portion of the message as a user task entry based on the analysis of the annotated message.

[0005] This method and other implementations of technology disclosed herein may each optionally include one or more of the following features.

[0006] In various implementations, the analyzing comprises analyzing, by the computing system, the annotated message pursuant to a plurality of rule paths of the grammar to generate a plurality of candidate user task entries and associated scores. In various implementations, the classifying comprises selecting, by the computing system, the user task entry from the plurality of candidate user task entries based on the associated scores.

[0007] The method may further include identifying, by the computing system, a user interface associated with fulfillment of the user task entry based on the analysis of the annotated message. In various implementations, performance of the natural language processing comprises identifying, by the computing system, a reference to a task interaction entity of the user task entry in the message. In various implementations, performance of the natural language processing further comprises classifying, by the computing system, the first task interaction entity as a person, location or organization. In various implementations, performance of the natural language processing further comprises identifying, by the computing system, a task action of the user task entry.

[0008] In various implementations, identifying the user interface comprises identifying the user interface based on the task interaction entity and task action. In various implementations, the method further includes automatically populating, by the computing system, one or more data points associated with the user interface with information based on the analysis of the annotated message. In various implementations, the method may further include automatically launching or opening, by the computing system, the user interface. In various implementations, the grammar comprises a context-free grammar.

[0009] Other implementations may include a non-transitory computer readable storage medium storing instructions executable by a processor to perform a method such as one or more of the methods described above. Yet another implementation may include a system including memory and one or more processors operable to execute instructions, stored in the memory, to perform a method such as one or more of the methods described above.

[0010] It should be appreciated that all combinations of the foregoing concepts and additional concepts described in greater detail herein are contemplated as being part of the subject matter disclosed herein. For example, all combinations of claimed subject matter appearing at the end of this disclosure are contemplated as being part of the subject matter disclosed herein.

Brief Description of the Drawings

[0011] Fig. 1 illustrates an example environment in which tasks may be identified in messages.

[0012] Fig. 2 depicts example components of a natural language processing engine.

[0013] Fig. 3 schematically demonstrates an example of how a message may be analyzed using techniques disclosed herein to identify and/or classify a task, and take responsive action.

[0014] Fig. 4 depicts a flow chart illustrating an example method of identifying tasks in messages. [0015] Fig. 5 schematically depicts an exa mple architecture of a computer system.

Detailed Description

[0016] Fig. 1 illustrates an example environment in which tasks may be identified in messages. The example environment includes a client device 106 and a user task entry system 102. User task entry system 102 may be implemented in one or more computers that communicate, for example, through a network (not depicted). User task entry system 102 may be an example of a system in which the systems, components, and techniques described herein may be implemented and/or with which systems, components, and techniques described herein may interface. Although described as being implemented in large part on a "user task entry system" herein, disclosed techniques may actually be performed on systems that serve various other purposes, such as email systems, text messaging systems, social networking systems, voice mail systems, productivity systems, enterprise software, search engines, and so forth.

[0017] A user may interact with user task entry system 102 via client device 106. Other computer devices may communicate with user task entry system 102, including but not limited to additional client devices and/or one or more servers implementing a service for a website that has partnered with the provider of user task entry system 102. For brevity, however, the examples are described in the context of client device 106.

[0018] Client device 106 may be a computer in communication with user task entry system 102 through a network such as a local area network (LAN) or wide a rea network (WAN) such as the Internet (one or more such networks indicated generally at 110). Client device 106 may be, for example, a desktop computing device, a laptop computing device, a ta blet computing device, a mobile phone computing device, a computing device of a vehicle of the user (e.g., an in-vehicle communications system, an in-vehicle entertainment system, an in-vehicle navigation system), or a weara ble a pparatus of the user that includes a computing device (e.g., a watch of the user having a computing device, glasses of the user having a computing device, a weara ble music player). Additiona l and/or alternative client devices may be provided. Client device 106 may execute one or more applications, such as client application 107, that ena ble a user to receive and consume messages, create task lists, and perform various actions related to task fulfillment. As used herein, a "message" may refer to an email, a text message (e.g., SMS, M MS), an instant messenger message, a voicema il, or a ny other incoming communication that is addressed to a user and that is capa ble of undergoing natural la nguage processing.

[0019] In some implementations, client device 106 and user task entry system 102 each include memory for storage of data and software applications, a processor for accessing data and executing applications, and components that facilitate communication over network 110. The operations performed by client device 106 and/or user task entry system 102 may be distributed across multiple computer systems. User task entry system 102 may be implemented as, for example, computer programs running on one or more computers in one or more locations that are coupled to each other through a network.

[0020] In various implementations, user task entry system 102 may include an entity engine 120, a user interface engine 122, a natural language processing (N LP) engine 124, a grammar engine 126, and/or a task classification engine 128. In some implementations one or more of engines 120, 122, 124, 126 and/or 128 may be com bined and/or omitted. In some implementations, one or more of engines 120, 122, 124, 126 and/or 128 may be implemented in a component that is separate from user task entry system 102. In some implementations, one or more of engines 120, 122, 124, 126 and/or 128, or any operative portion thereof, may be implemented in a component that is executed by client device 106.

[0021] Entity engine 120 may maintain an entity data base 125. "Entities" may include but are not limited to people, locations, organizations, actions, objects, and so forth. In various implementations, entity data base 125 may include entity data pertinent to a particular user and/or to users globally. For insta nce, in some implementations, entity data base 125 may include a user's contact list, which often may be maintained as a contact list on the user's sma rt phone and/or on her email. In some such cases, entity data base 125 may be implemented additionally or alternatively on client device 106. In some

implementations, entity database may include a global network of entities that may or may not be pertinent to all users. In various implementations, global entity data may be populated over time from various sources of data, such as search engines (e.g., and their associated web crawlers), users' collective contact lists, social networking systems, a nd so forth. In various implementations, entity data may be stored in entity database 125 in various forms, such as a graph, tree, etc. [0022] User interface engine 122 may maintain an index 127 of user interfaces. As used herein, "user interface" may refer to any visual a nd/or audio interface or prompt with which a user may interact. Some user interfaces may be integral parts of executa ble software applications, which may be programmed using various programming and/or scripting languages, such as C, C#, C++, Pascal, Visual Basic, Perl, and so forth. Other user interfaces may be in the form of markup language documents, such as web pages (e.g., HTM L, XM L) or interactive voice applications (e.g., VXM L).

[0023] In this specification, the term "data base" and "index" will be used broadly to refer to any collection of data. The data of the data base and/or the index does not need to be structured in any particular way and it can be stored on storage devices in one or more geographic locations. Thus, for example, the indices 125 and/or 127 may include multiple collections of data, each of which may be organized and accessed differently.

[0024] As described herein, a user task entry (alternatively referred to simply as a "task") may include an indication of one or more task actions and an indication of one or more task interaction entities. A task action may be an action that a user has interest in completing and/or having completed by one or more other users. For example, a task action may be "buy" and the user may have interest in buying something and/or having another person buy something for the user. A task interaction entity is an entity that is associated with the task action. For example, a task may have a task action of "buy" a nd a task interaction entity of "ba nanas," and the purpose of the task may be for the user to buy bana nas.

[0025] In some implementations, an indication of the task action and/or the task interaction entity in a task entry may include an entity identifier. For example, an indication of the task action "buy" may include an identifier of the entity associated with the action of buying. An entity identifier may be associated with an entity in one or more data bases, such as entity data base 125. In some implementations, an indication of the task action and/or the task interaction entity in a user task entry may additionally or alternatively include one or more terms associated with the task action and/or the task interaction entity. For example, an indication of the task action "buy" may include the terms "buy" and/or "purchase".

[0026] User task entry system 102 may be configured to identify and/or classify user task entries within messages based at least in part on analysis of the messages pursuant to a grammar. However, designing a grammar capable of facilitating such ana lysis may be impracticable. Messages may contain virtually any word of any language in a ny arrangement. Accordingly, N LP engine 124 may be configured to first perform natural language processing on messages to provide what will be referred to herein as an

"annotated message." The annotated message may include various types and levels of annotations for various aspects of the message. These annotations may clarify various aspects of the message, relationships between terms and sections of the message, and so forth, so that designing a grammar suita ble for a nalyzing messages to identify and/or classify tasks may become practica ble. In various implementations, the annotated message may be organized into one or more data structures, including but not limited to trees, graphs, lists (e.g., linked list), arrays, and so forth.

[0027] Annotations that may be provided by N LP engine 124 as part of the annotated message may be best understood with reference to Fig. 2, which depicts components of an example NLP engine 124. N LP engine 124 may include a part of speech tagger 230, which may be configured to annotate, or "tag," words of the message with its grammatical role. For instance, part of speech tagger 230 may tag each word with its part of speech, such as "noun," "verb," "adjective," "pronoun," etc.

[0028] In some implementations, N LP 124 may also include a dependency parser 232. Dependency parser 232 may be configured to determine syntactic relationships between words of the message. For example, dependency parser 232 may determine which words modify which others, su bjects and verbs of sentences, a nd so forth. Dependency parser 232 may then make suita ble annotations of such dependencies.

[0029] In some implementations, N LP 124 may include a mention chunker 234. Mention chunker 234 may be configured to identify and/or annotate references or "mentions" to entities, including task interaction entities, in the message. For example, mention chunker 234 may determine to which person, place, thing, idea, or other entity each nou n or personal pronou n refers, and may annotate, or "tag," them accordingly. As another example, mention chunker 234 may be configured to associate references to times and/or dates to specific times or dates. For instance, assume a message conta ins the sentence, "Can you pick up some milk on your way home tonight?" Mention chunker 234 may associate the word "tonight" with today's date, and with a particular time (e.g., after 5pm). ln some implementations, mention chunker 234 may determine, e.g., from a user's calendar, when the user is leaving work, and may associate that time with the word "tonight." One or more downstream components may use this information to create, or help a user create, an appropriate calendar entry and/or to make sure the user receives a reminder at an appropriate time (e.g., while driving home).

[0030] In some implementations, N LP 124 may include a named entity tagger 236.

Named entity tagger 236 may be configured to annotate, or "tag," entity references in the annotated message as a person, location, organization, and so forth. In some

implementations, named entity tagger 236 may identify one or more task actions of the user task entry. In other implementations, one or more other components depicted in Fig. 2 or elsewhere in the figures may be configured to identify one or more task actions of the user task entry.

[0031] In some implementations, N LP 124 may include a coreference resolver 238. Coreference resolver 238 may be configured to group, or "cluster," references to the same entity based on various contextual cues contained in the message. For example, "Reagan," "the President," and "he" in a message may be grouped together. In some implementations, coreference resolver 238 may use data outside of a body or su bject of a message, e.g., metadata, to cluster references. For instance, an ema il or text may only contain a reference to "you" (e.g., "ca n you pick up milk on the way home tonight"). In such case, coreference resolver 238 (or another component, in different implementations) may resolve the reference to "you" to a person to which the email or text is addressed.

[0032] In some implementations, N LP 124 may also include an entity resolver 240. Entity resolver 240 may be configured to communicate with entity engine 120 to determine whether entities referenced in the message (e.g., by references tagged by mention chunker 234) are entities that are contained in entity data base 125.

[0033] Referring back to Fig. 1, grammar engine 126 may be configured to analyze the annotated message of N LP engine 124 against a grammar to determine whether a message includes a user task entry. In some implementations, grammar engine 126 may ana lyze the annotated message pursuant to a plurality of rule paths of the grammar. Each rule path may be associated with one or more potential types of user task entry. Task classification engine 128 may be configured to analyze output of grammar engine 126, and in particular, output of the plura lity of rule paths of the grammar, to determine a task type. User interface engine 122 may be configured to identify a user interface associated with the task, e.g., based on various data from various other components of Fig. 1.

[0034] Fig. 3 depicts one example process flow for identifying tasks in a message 350. Message 350 may include computer-reada ble characters a nd/or symbols, e.g., of a n email, text message, etc. Additionally or a lternatively, message 350 may include speech-recognized text (e.g., a transcript) of a voicemail or other audio message. Message 350 may be first processed by N LP engine 124 to produce the annotated message. As depicted in Fig. 3, NLP 124 may obta in data from entity engine 120, e.g., by way of entity resolver 240, to perform various analysis. The annotated message output by N LP 124 may be provided as input to a plurality of rule paths, 352a-n (referenced generically by 352), of grammar engine 126. Each rule path 352 may define one or more rules against which the annotated message is compared and judged. In some implementations, the more rules or parameters of a rule path 352 that are satisfied by the annotated message, the higher a score the annotated message will receive from that rule path 352.

[0035] For example, assume rule path 352a tests the annotated message for a task action of "confer," a location (e.g., an address), a date and a time. Assume rule path 352b also tests the annotated message for a task action of "confer," a date and a time, but tests for a telephone number instead of a location. If message 350 includes a task, "Make sure you confer with Judy (555-1234) on Ju ne 2 ^nd at 3pm a bout party plans," first rule path 352a may produce a score of three (because three of the four items sought were matched), and second rule path 352b may produce a score of four.

[0036] Task classification engine 128 may be configured to receive scores from the plurality of grammar rule paths 352a-n and select the most satisfactory score (e.g., highest). For example, in the a bove example, task classification engine 128 would select a type of task associated with rule path 352b. In some implementations, if no score yielded by any rule path 352 satisfies a particular threshold, task classification engine 128 may determine that no user task entries are present in message 350.

[0037] Ul engine 122 may be configured to identify a user interface associated with fulfillment of the user task entry based on various data. For insta nce, Ul engine 122 may be in communication with entity engine 120 such that it is a ble to associate a task interaction entity, e.g., tagged by entity tagger 236, with a pa rticular task. In some implementations an association between a user interface and an entity may be based on presence of one or more attributes of the entity in the user interface. For example, a n association between a user interface and an entity may be based on an importance of one or more aliases of the entity in the user interface. For example, a ppeara nce of an alias of an entity in important fields and/or with great frequency in a user interface may be indicative of association of the entity to the user interface. Also, for example, a n association between a user interface and an entity may be based on presence of additional a nd/or alternative attributes of an entity such as date of birth, place of birth, height, weight, population, geographic location(s), type of entity (e.g., person, actor, location, business, university), etc.

[0038] Take the example described a bove regarding the task, "Make sure you confer with Judy (555-1234) on June 2 ^nd at 3pm a bout party plans." U l engine 122 may identify, and in some cases open or launch, a calendar user interface. In some implementations, Ul engine 122 may populate one or more data points associated with the user interface. Thus, in the same example, U l engine 122 may launch a calendar entry with the date and time already set as described in the task.

[0039] Ul engine 122 may identify, open and/or initiate other types of user interfaces for other types of tasks. For example, assume message 350 includes a task, "Make dinner reservations at Sal's Bistro on Tuesday." As described a bove, the plurality of rule paths 352a-n may be used by grammar engine 126 to analyze the annotated message output by N LP engine 124. The rule path 352 associated with making restaurant reservations may yield the highest score, which may lead to its being selected by task classification engine 128. Additionally, N LP engine 124 may have, e.g., by way of entity tagger 236 sending a query to entity engine 120, identified Sal's Bistro as an entity a nd tagged it accordingly in the annotated message. I n some implementations, other information a bout Sal's Bistro not specified in message 350, such as its address and/or telephone num ber, may also be obtained from various sources once Sal's Bistro is tagged as an entity.

[0040] Using the a bove-described information, Ul engine 122 may identify an appropriate user interface to assist the user in ma king a reservation at the restaurant. Various user interfaces 354a-m are depicted in Fig. 3 as being availa ble for use by the user to make the reservation. A first interface 354a may be an interface to online resta urant reservation application. A second interface 354b may be a URL to a webpage, e.g., a webpage hosted by Sal's Bistro that includes a n interactive interface to ma ke reservations. Another user interface 354m may be a smart phone telephone interface, which in some cases may be initiated with Sal's Bistro's telephone num ber already entered, so that the user only need to press "talk" to initiate a call to Sal's. Of course, other types of interfaces are possible. In various implementations, one or more data points (e.g., interaction entities such as people or organizations, task actions, times, dates, locations, etc.) may be extracted from the annotated message and provided to whichever user interface is selected, so that the user need not provide this information manually.

[0041] Referring now to Fig. 4, an example method 400 of identifying tasks in messages is described. For convenience, the operations of the flow chart are described with reference to a system that performs the operations. This system may include various components of various computer systems. For insta nce, some operations may be performed at the client device 106, while other operations may be performed by one or more components of user task entry system 102, such as entity engine 120, user interface engine 122, N LP engine 124, grammar engine 126, and/or task classification engine 128. Moreover, while operations of method 400 are shown in a particular order, this is not meant to be limiting. One or more operations may be reordered, omitted or added.

[0042] Method 400 may begin ("START") when a message (e.g., 350) is received and/or consumed, e.g., at client device 106 or at user task entry system 102 (e.g., in a manner that is readily accessible to client device 106). At block 402, the system may perform natural language processing on the message to generate the a nnotated message, including performing the operations associated with the various components depicted in Fig. 2 and described a bove.

[0043] At block 404, the system may analyze the annotated message pursuant to a grammar. For example, at block 406, the system may a nalyze the annotated message pursuant to a plurality of rule paths (e.g., 352a-n of Fig. 3) to generate a plurality of candidate user task entries and associated scores. As described a bove, candidates having satisfied more parameters of their respective rule paths than others may have higher scores than others. In various implementations, each rule path of the grammar, or the grammar as a whole, may be various types of grammars, such as a context-free gra mmar. [0044] At block 408, the system may classify a portion of the message {e.g., a sentence, paragraph, selected words, su bject line, etc.) as a user task entry based on analysis of the annotated message provided at block 402. For example, at block 410, the system may select the candidate user task entry with the highest associated score.

[0045] At block 412, the system may select one or more user interfaces associated with the selected user task entry. At block 414, the system may automatically populate one or more data points (e.g., input fields) associated with the selected user interface. For example, if the interface is an interactive webpage, client 107 may transmit a n HTTP request with values to assign to various HTTP server varia bles. At block 416, the system may automatically launch or open the selected user interface. In some implementations, the operations of blocks 414 and 416 may be performed in reverse.

[0046] Fig. 5 is a block diagram of an example computer system 510. Computer system 510 typically includes at least one processor 514 which communicates with a num ber of peripheral devices via bus su bsystem 512. These periphera l devices may include a storage su bsystem 524, including, for example, a memory su bsystem 525 a nd a file storage su bsystem 526, user interface output devices 520, user interface input devices 522, and a network interface su bsystem 516. The input and output devices allow user interaction with computer system 510. Network interface su bsystem 516 provides an interface to outside networks a nd is coupled to corresponding interface devices in other computer systems.

[0047] User interface input devices 522 may include a keyboard, pointing devices such as a mouse, trackball, touchpad, or graphics ta blet, a scanner, a touchscreen incorporated into the display, audio input devices such as voice recognition systems, microphones, a nd/or other types of input devices. In general, use of the term "input device" is intended to include all possible types of devices and ways to input information into computer system 510 or onto a communication network.

[0048] User interface output devices 520 may include a display su bsystem, a printer, a fax machine, or non-visual displays such as audio output devices. The display su bsystem may include a cathode ray tu be (CRT), a flat-panel device such as a liquid crystal display (LCD), a projection device, or some other mechanism for creating a visible image. The display su bsystem may also provide non-visual display such as via audio output devices. In general, use of the term "output device" is intended to include all possible types of devices and ways to output information from computer system 510 to the user or to another machine or computer system.

[0049] Storage su bsystem 524 stores programming and data constructs that provide the functionality of some or all of the modules described herein. For example, the storage subsystem 524 may include the logic to perform selected aspects of method 400 and/or to implement one or more of entity engine 120, user interface engine 122, NLP engine 124, grammar engine 126, and/or task classification engine 128.

[0050] These software modules are generally executed by processor 514 alone or in combination with other processors. Memory 525 used in the storage subsystem can include a number of memories including a main random access memory (RAM) 530 for storage of instructions and data during program execution and a read only memory (ROM) 532 in which fixed instructions are stored. A file storage subsystem 524 can provide persistent storage for program and data files, and may include a hard disk drive, a floppy disk drive along with associated removable media, a CD-ROM drive, an optical drive, or removable media cartridges. The modules implementing the functionality of certain implementations may be stored by file storage subsystem 524 in the storage subsystem 524, or in other machines accessible by the processor(s) 514.

[0051] Bus su bsystem 512 provides a mechanism for letting the various components and subsystems of computer system 510 communicate with each other as intended. Although bus subsystem 512 is shown schematically as a single bus, alternative implementations of the bus subsystem may use multiple busses.

[0052] Computer system 510 can be of varying types including a workstation, server, computing cluster, blade server, server farm, or any other data processing system or computing device. Due to the ever-changing nature of computers and networks, the description of computer system 510 depicted in Fig. 5 is intended only as a specific example for purposes of illustrating some implementations. Many other configurations of computer system 510 are possible having more or fewer components than the computer system depicted in Fig. 5.

[0053] In situations in which the systems described herein collect personal information about users, or may make use of personal information, the users may be provided with an opportunity to control whether programs or features collect user information {e.g., information about a user's social network, social actions or activities, profession, a user's preferences, or a user's current geographic location), or to control whether and/or how to receive content from the content server that may be more relevant to the user. Also, certain data may be treated in one or more ways before it is stored or used, so that personal identifiable information is removed. For example, a user's identity may be treated so that no personal identifiable information can be determined for the user, or a user's geographic location may be generalized where geographic location information is obtained (such as to a city, ZIP code, or state level), so that a particular geographic location of a user cannot be determined. Thus, the user may have control over how information is collected about the user and/or used.

[0054] While several implementations have been described and illustrated herein, a variety of other means and/or structures for performing the function and/or obtaining the results and/or one or more of the advantages described herein may be utilized, and each of such variations and/or modifications is deemed to be within the scope of the

implementations described herein. More generally, all parameters, dimensions, materials, and configurations described herein are meant to be exemplary and that the actual parameters, dimensions, materials, and/or configurations will depend upon the specific application or applications for which the teachings is/are used. Those skilled in the art will recognize, or be able to ascertain using no more than routine experimentation, many equivalents to the specific implementations described herein. It is, therefore, to be understood that the foregoing implementations are presented by way of example only and that, within the scope of the appended claims and equivalents thereto, implementations may be practiced otherwise than as specifically described and claimed. Implementations of the present disclosure are directed to each individual feature, system, article, material, kit, and/or method described herein. In addition, any combination of two or more such features, systems, articles, materials, kits, and/or methods, if such features, systems, articles, materials, kits, and/or methods are not mutually inconsistent, is included within the scope of the present disclosure.