Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
DETAILED ACTION
1. This Office Action is in response to the amendment filed on 08/03/2026.
Claim 1 has been amended.
Claims 2-20 have been canceled.
Claims 21-39 have been added.
Claims 1 and 21-39 are pending.
Response to Arguments
2. Applicant's arguments with respect to claims 37-39 have been considered but are moot in view of the new ground(s) of rejection.
Examiner’s Note
3. The front end of a collaboration system (According to Google): “The front end of a collaboration system is the user interface (UI) and client-facing layer where people interact, communicate, share files, and track projects in real time. Core Elements of a Collaboration Front End: (1) Shared Workspaces: Unified dashboards combining inboxes, chats, and task boards. (2) Real-Time Communication: Instant messaging panels, comment threads, and video integration. (3) Interactive Elements: Live cursors, simultaneous text editing, and @mentions for team alerts. (4) Navigation & Sidebar: Menus to sort open, pending, and completed items or switch between projects. Popular Examples: (1) Slack: Focused on channel-based messaging and app integrations. (2) Front: Combines shared team inboxes with internal discussion threads. (3) Miro: Provides a visual, infinite-canvas front end for brainstorming. “
A graphical user interface (GUI) comprising a content editing frame (According to Google): “A graphical user interface (GUI) comprising a content editing frame is a visual computer application layout specifically designed to let users modify, create, or manipulate data inside a designated, bordered section of the screen. This phrasing is common in software design patents and technical specifications to formally describe an editing software's interface. It generally consists of two main parts: (1) The Content Editing Frame (The Workspace). This is the primary bounded rectangular area (or window) where the actual asset—such as text, images, code, or video—is loaded and modified: (a) What happens inside it: The user can directly select, type, draw, or arrange visual elements within this boundary. (b) Examples: The canvas in Adobe Photoshop, the blank document sheet in Microsoft Word, the code editor pane in VS Code, or the center viewport in a video editing suite. (2) The Surrounding GUI Elements (The Tooling). To make the frame functional, the GUI surrounds it with control widgets that dictate what happens inside the frame. These typically include: (a) Toolbars and Ribbons: Rows of buttons providing quick access to commands like "crop," "bold," "save," or "undo". (b) Menus: Dropdown or hamburger lists organizing broader options (e.g., File, Edit, View). (c) Scrollbars: Vertically or horizontally positioned tracks allowing users to view content that expands past the frame's visible borders. (d) Contextual Panels: Sidebar panels showing layer menus, properties, or asset folders that can be interacted with to alter what is in the main frame.”
A graphical user interface (GUI) endpoint (According to Google): “A graphical user interface (GUI) endpoint is a specific network address (like a URL or IP address) that serves a visual, browser-based or client-rendered interface for users to interact with a system or service. Overview of a GUI Endpoint: (1) Definition: A web address or application access point where a human-readable visual interface is hosted or loaded. (2) Difference from API Endpoint: An API endpoint receives raw code requests (like JSON data) for machine-to-machine communication, whereas a GUI endpoint renders graphical elements—like buttons, menus, and windows—for a human user. (3) Common Uses: Administrative dashboards, router setup pages, software management consoles, and cloud service portals.”
Initiating a query to a platform-specific schema resource (According to Google): “Initiating a query to a platform-specific schema resource means requesting structural information or metadata about how data is organized within a specific database, system, or software platform. Instead of searching for the actual data records (like a customer's name), you are asking the system to describe its own blueprint—such as tables, columns, data types, and relationships. What Does This Mean in Practice?: Platforms format and store their structural metadata differently. When you "initiate a query to a platform-specific schema resource," you use the unique language or tools built into that exact environment. Examples of what this looks like across different ecosystems include: (1) Relational Databases (SQL Server, Snowflake, etc.): Querying the system catalogs or built-in metadata tables. For instance, in Snowflake, you run a standard SQL query against a unique platform view: SELECT * FROM database.information_schema.columns; (2) Enterprise Cloud Platforms (Microsoft Power Platform / Dataverse): Using platform APIs (like OData REST endpoints) to dynamically pull a list of system tables, keys, and many-to-many relationships (EntityDefinitions). (3) Data Streaming Ecosystems (Apache Kafka / Confluent Platform): Requesting structural information from a Confluent Schema Registry to understand the data models and versions governing data payloads. (4) AI & Graph Databases (TypeDB, Adobe Experience Platform): Submitting a structured API command or transaction (such as hitting the /schemas endpoint in Adobe) to check the ingested classes and field groups before running complex federated data lookups.”
A documentation platform (According to Google): “A documentation platform is a centralized software system used to write, organize, host, and maintain guides, technical specs, and internal knowledge bases. What It Does: (1) Single Source of Truth: Combines fragmented notes, user manuals, and developer APIs into one searchable home. (2) Multichannel Publishing: Formats and shares content seamlessly for humans reading online and AI assistants consuming data. (3) Collaborative Workflows: Supports real-time editing, version control, and review histories so teams can keep information current. Common Examples: (1) GitBook: Built for technical and cross-functional teams combining Markdown and visual editors. (2) Mintlify & Document360: End-to-end publishing tools designed for public product guides and developer hubs. (3) Atlassian Confluence: A traditional page-based workspace suited for corporate and internal team records. “
A content editing frame (According to Google): “A content editing frame (often called a content editing framework) is a structured guide or system used to review, shape, and improve written or digital material before it is published. Instead of just checking for spelling errors, a content editing framework looks at the big picture. It ensures that the piece meets its goals, matches the brand's voice, and makes sense to the reader. What a Content Editing Frame Covers: (1) Structure and Flow: Checks if paragraphs, sections, or storylines follow a logical order. (2) Clarity and Purpose: Ensures the main message is clear and answers the target audience's needs. (3) Tone and Style: Confirms the writing style matches brand guidelines or project requirements. (4) Fact-Checking: Validates sources, data, and claims for accuracy.”
Receiving a user selection of a command control in a command selection interface window (According to Google): “Receiving a user selection of a command control in a command selection interface window means capturing the specific action or option a user clicks, taps, or selects from a menu, toolbar, or dialog box to tell the software what to do next. How It Works: (1) The Interface: A window displays interactive elements like buttons, dropdown lists, or command links. (2) The Action: The user picks a specific command control (such as clicking "Save," choosing an item from a list, or checking a radio button). (3) The Reception: The application’s underlying code "receives" or captures this event (an input trigger) to execute the corresponding function. Common Examples: (1) Clicking a toolbar button like Print or Delete in a text editor. (2) Selecting an option from a context menu (right-click menu) to format text. (3) Choosing a setup path using command links in an installation wizard.”
A generative output engine (According to Google): “A generative output engine is an artificial intelligence system that creates new content—such as text, images, code, or audio—based on patterns it learned during training. How It Works: (1) Training data: The system studies huge amounts of existing information like books, art, or code. (2) Prompting: A user gives the engine a text request or instruction (a prompt). (3) Prediction: The engine analyzes the prompt and predicts the most likely pieces of new content to build a custom response. Common Uses: (1) Text: Writing essays, emails, or chat responses. (2) Visuals: Creating unique digital art or photos from text descriptions. (3) Code: Generating and debugging software programming scripts.”
Kadowaki et al, US 20100293447, [Kadowaki: Abstract (“Assistance for document creation in a computer system which allows at least one agent to be registered therein is provided. The computer system causes the at least one agent to monitor input by a user during the document creation, acquire information on the input obtained by the monitoring, retrieve at least one content from multiple contents accumulated in a storage unit based on the acquired information, and transmit the retrieved at least one content to a display unit to display the retrieved content on a screen.”)] [Kodowaki: Paragraphs 23, 25 and 75 (“the present invention provides a document creation assistance system which allows at least one agent to be registered therein. The method comprises application software to receive user input”)] [Kadowaki: Paragraphs 21 and 75 (“the process of the document creation includes document editing, and the acquired information is a whole or a part of a document in process of editing”)] [Kadowaki: Paragraph 25 (“a display section configured to display the retrieved content on a screen.”)].
Chidlowskii et al, US 20040268236, [Chidlovskii: Paragraphs 39 and 48 (“When the user is authoring a document D, the editing process is seen as a sequence of elementary actions on the document structure, D.sub.0, D.sub.1=D.sub.0+action.sub.o . . . . At step j of the authoring process, the user opens/closes tag X and the adviser should propose how to extend the current state of D.sub.j with one most probable tag or most probable pattern of the depth d” ; “assume the user has selected pattern ABB”)] [Chidlovskii: Paragraph 12 (“he method of authoring a structured document makes use of machine learning techniques in order to generate textual suggestions using existing structured documents and/or the current document as training data. These suggestions are based on regularities occurring in a corpus of similar documents. During the authoring step, each time a new tag is inserted in a document, content suggestions (if any) are proposed to the author, who validates one or refuses all of them. The method considers content advising as a categorization problem; it combines machine learning algorithms and document structure in order to predict textual chunks during the authoring step; it uses contextual (structure and content) information for suggestion computation; and computed suggestions are automatically proposed to the author when the appropriate context is detected”)].
Claim Rejections - 35 USC § 102
4. In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
5. The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale or otherwise available to the public before the effective filing date of the claimed invention.
6. Claims 37-39 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Song et al (US 20240310977).
Claim 37:
Song suggests a computer-implemented method for automatic application programming interface ("API") request generation in a collaboration platform [Song: Paragraphs 4, 21, 22, 25, 55 and 77 (“wherein the customized GUI uses an API associated with the first electronic document editing application to allow the second user to manipulate the electronic document of the first electronic document type”)] [Song: Paragraphs 16, 20, 22, 28 and 35 (“The GUI components may be associated with features (e.g., sharing, collaboration, etc.) of an electronic document editing application”)], the method comprising: receiving an indication of a user selection of a command control associated with a proposed action for document creation [Song: Abstract and Paragraphs 5, 16, 20 and 21 (“a user request to create a new electronic document, the script to generate the preloaded version of the customized GUI displaying a first instance of the new electronic document is executed. A user interaction with the preloaded version of the customized GUI is identified” ; “A first user, such as an administrator of the third party platform, may select one or more GUI components to include into the first party GUI to create a customized GUI”)] . Song suggests generating a service query content item including predefined prompt text designating the proposed action and a portion of user-generated content from a content editing frame [Song: Paragraphs 5, 16, 20 and 24 (“The script may be to determine that the user interaction with the blank electronic document adds content to the blank electronic document, and to cause a copy of the content to be sent to the cloud storage system to include in the customized GUI when the customized GUI replaces the presented preloaded version”]. Song suggests providing the service query content item to a generative output engine [Song: Paragraphs 71 and 72 (“the machine learning model may be composed of, e.g., a single level of linear or non-linear operations (e.g., a support vector machine [SVM]) or may be a deep network, i.e., a machine learning model that is composed of multiple levels of non-linear operations. An example of a deep network is a neural network with one or more hidden layers, and such machine learning model may be trained by, for example, adjusting weights of a neural network in accordance with a backpropagation learning algorithm or the like. For convenience, the remainder of this disclosure will refer to the implementation as a neural network, even though some implementations might employ an SVM or other type of learning machine instead of, or in addition to, a neural network. Once the machine learning model is trained using a training engine, the model may be referred to as a trained machine learning model”)]. Song suggests receiving a generative response from the generative output engine including a set of field values [Song: Paragraphs 5 and 18 (“Other features associated with other of the plurality of GUI components that were not selected by the first user to include in the customized GUI of the respective electronic document editing application may not be made available to the second user of the third party platform”)]. Song suggests transmitting a request body including the set of field values to an API endpoint of a documentation platform [Song: Paragraphs 5 and 18 (“Other features associated with other of the plurality of GUI components that were not selected by the first user to include in the customized GUI of the respective electronic document editing application may not be made available to the second user of the third party platform”)]. Song suggests causing display of a new electronic document created in response to the request body [Song: Paragraph 42 (“real-time may refer to the transmission, presentation, or display of changes to a collaborative document to one or more client devices 110 as the changes are being made on different client devices. For example, real-time changes (e.g., edits) to a collaborative document may be displayed on a display of a client device 110A substantially concurrent with a user editing the collaborative document using client device 110Z (at least within the technical limitations of displaying real-time changes, e.g., the user edits to the collaborative document may be displayed within milliseconds of user input and may appear to the receiving user as if in absolute real-time)”)].
Claim 38:
Song suggests a computer-implemented method for automatic application programming interface ("API") request generation in a collaboration platform wherein the proposed action is
selected from a set of content modification actions associated with respective command
controls of a command selection interface window [Song: Abstract and paragraphs 16 20 and 25 (“Responsive to a user request to create a new electronic document, the script to generate the preloaded version of the customized GUI displaying a first instance of the new electronic document is executed. A user interaction with the preloaded version of the customized GUI is identified. Responsive to identifying the user interaction with the preloaded version of the customized GUI, a request to obtain a customized GUI to replace the preloaded version of the customized GUI is sent to a cloud-based storage system”)].
Claim 39:
Song suggests wherein the service query content item further includes a portion of an API endpoint description obtained from a platform- specific schema resource [Song: Abstract and paragraphs 16 20 and 25 (“Responsive to a user request to create a new electronic document, the script to generate the preloaded version of the customized GUI displaying a first instance of the new electronic document is executed. A user interaction with the preloaded version of the customized GUI is identified. Responsive to identifying the user interaction with the preloaded version of the customized GUI, a request to obtain a customized GUI to replace the preloaded version of the customized GUI is sent to a cloud-based storage system”)] [Song: Paragraph 36, 44 and 49 (“For example, a word processing application may allow for editing of an electronic document of a word processing electronic document type. A spreadsheet processing application may allow for editing of an electronic document of a spreadsheet electronic document type, and so forth”)].
Allowable Subject Matter
7. Claims 1 and 21-36 are in conditions for allowance.
Conclusion
8. Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any extension fee pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the date of this final action.
9. Any inquiry concerning this communication or earlier communications from the examiner should be directed to [Hung D. Le], whose telephone number is [571-270-1404]. The examiner can normally be communicated on [Monday to Friday: 9:00 A.M. to 5:00 P.M.].
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Apu Mofiz can be reached on [571-272-4080]. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, contact [800-786-9199 (IN USA OR CANADA) or 571-272-1000].
Hung Le
09/21/2026
/HUNG D LE/Primary Examiner, Art Unit 2161
Prosecution Insights