# US 2023/0274080 A1 · System, method, and apparatus for a unified document surface

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0274080 A1
- Document ID: US20230274080A1
- Status: Published application
- Kind: A1
- Application number: 18/195,109
- Filed: 2023-05-09
- Published: 2023-08-31
- Earliest claimed: 2021-02-23
- Assignees: Grammarly, Inc.
- Applicants: Coda Project, Inc.
- Inventors: Alexander W. DeNeui; Glenn Jaume; Hariharan Sivaramakrishnan; Helena G. Jaramillo; John Z. Li; Jonathan L. Goldman; Martin Charles; W. Michael Varney; Timothy Andrew James; Adam Ginzberg; Nathan Penner; Evan Brooks; Michael Hewitt; Punit Shah; Patrick Barry; Huayang Guo; Jason Peter Stowe; Christopher Leland Eck; Alicia Salvino; Alan Fang; Spencer Chang; Elizabeth Huang; Oleg Vaskevich
- Web page: https://patentgrep.com/patent/US20230274080A1

## CPC

- G06F 40/166: Editing, e.g. inserting or deleting
- G06F 3/0484: for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods for publication and external interfacing for a unified document surface are disclosed. An example system may include a document serving circuit structured to access a document data, the document data comprising data for a unified document surface, and provide at least a portion of the document data to a client serving circuit. The client serving circuit may be structured to implement a unified document surface interface in response to the at least a portion of the document data, implement an extension creation interface, provide a pack implementation value to the document serving circuit in response to user interactions with the extension creation interface, and determine an executable object in response to the pack implementation value.

## Claims

### Claim 1

A system, comprising:
a document serving circuit structured to:
access a document data, the document data comprising data for a unified document surface; and
provide at least a portion of the document data to a client serving circuit; and
the client serving circuit structured to:
implement a unified document surface interface in response to the at least a portion of the document data;
implement an extension creation interface;
provide a pack implementation value to the document serving circuit in response to user interactions with the extension creation interface; and
determine an executable object in response to the pack implementation value.

### Claim 2 (depends on 1)

The system of claim 1, wherein:
the pack implementation value comprises an access authorization value; and
the executable object comprises an access authorization description.

### Claim 3 (depends on 1)

The system of claim 1, wherein the document serving circuit is further structured to expose a pack to a workspace in response to the executable object.

### Claim 4 (depends on 3)

The system of claim 3, further comprising a second client serving circuit structured to:
access the pack;
implement an extension utilization interface; and
incorporate at least a portion of the pack into a second document in response to user interactions with the extension utilization interface, the second document being associated with the workspace.

### Claim 5 (depends on 2)

The system of claim 2, wherein the document serving circuit is further structured to expose a pack to a workspace in response to the executable object.

### Claim 6 (depends on 5)

The system of claim 5, further comprising a second client serving circuit structured to:
access the pack;
implement an extension utilization interface; and
incorporate at least a portion of the pack into a second document in response to user interactions with the extension utilization interface, the second document being associated with the workspace.

### Claim 7 (depends on 6)

The system of claim 6, wherein the document serving circuit is further structured to isolate the access authorization description from the second client serving circuit.

### Claim 8 (depends on 7)

The system of claim 7, wherein:
The pack comprises at least one of: a service or an external data value; and
the access authorization description comprises authorization information for access to the at least one of: the service or the external data value.

### Claim 9 (depends on 1)

The system of claim 1, wherein the executable object comprises at least one of: a button, a unified document surface interface object, a code-based object, a third-party object, or a column object.

### Claim 10 (depends on 1)

The system of claim 1, wherein the extension creation interface comprises a software development kit (SDK) layer.

### Claim 11 (depends on 1)

The system of claim 1, wherein the pack implementation value comprises an arbitrary code component.

### Claim 12 (depends on 11)

The system of claim 11, wherein the document serving circuit is further structured to determine the executable object by isolating operations of the arbitrary code component from at least one of: the client serving circuit or the document serving circuit.

### Claim 13 (depends on 12)

The system of claim 12, wherein the document serving circuit is further structured to determine the pack implementation value by operating a virtual machine to execute the arbitrary code component.

### Claim 14 (depends on 13)

The system of claim 13, wherein the document serving circuit is further structured to determine the executable object by operating the virtual machine on a workflow serving circuit.

### Claim 15 (depends on 14)

The system of claim 14, wherein the document serving circuit is further structured to create a dedicated instance of the virtual machine for the arbitrary code component.

### Claim 16 (depends on 1)

The system of claim 1, wherein the document serving circuit is further structured to perform, in response to determining that an update to the pack implementation value comprises an incompatibility risk, at least one operation among:
providing an incompatibility warning value to a client device;
providing an update option value to a second client serving circuit accessing a document utilizing a pack exposed to a workspace in response to the executable object; or
providing an update delay value to the second client serving circuit accessing the document utilizing the pack exposed to the workspace in response to the executable object.

### Claim 17 (depends on 1)

The system of claim 1, wherein the document serving circuit is further structured to:
implement a sandbox interface as a part of the extension creation interface; and
provide a calculated output value to a client device in response to user interactions with the sandbox interface.

### Claim 18 (depends on 17)

The system of claim 17, wherein the document serving circuit is further structured to operate an external data access authorization in response an access credential supplied by the user to the sandbox interface.

### Claim 19 (depends on 18)

The system of claim 18, wherein the document serving circuit is further structured to store the access credential in a local hidden file of the client device.

### Claim 20 (depends on 5)

The system of claim 5, wherein the access authorization description comprises an authorization type for each one of a service or an external data access of the pack.

### Claim 21 (depends on 20)

The system of claim 20, wherein the document serving circuit is further structured to require authorization information for the service or the external data access from a second user of a second document utilizing the pack in response to the authorization type comprising a user authorization type.

### Claim 22 (depends on 21)

The system of claim 21, wherein the document serving circuit is further structured to access the service or the external data access using separate credentials from the required authorization information.

### Claim 23 (depends on 20)

The system of claim 20, wherein the document serving circuit is further structured to provide access to the service or the external data access to a second user of the second document utilizing the pack in response to the authorization type comprising a system authorization type.

### Claim 24 (depends on 1)

The system of claim 1, wherein the document serving circuit is further structured to:
perform a validation of the executable object; and
create a pack in response to the executable object and the validation.

### Claim 25 (depends on 1)

The system of claim 1, wherein the document serving circuit is further structured to:
perform a validation of the executable object; and
provide a notification to the extension creation interface in response to the validation indicating a pack error.

### Claim 26 (depends on 25)

The system of claim 25, wherein the pack error comprises at least one of: a formula error, an authorization error, or a code operation error.

### Claim 27 (depends on 1)

The system of claim 1, wherein the extension creation interface further comprises an assistance interface.

### Claim 28 (depends on 27)

The system of claim 27, wherein the assistance interface further comprises at least one of:
a tooltip associated with at least one of: a component of the extension creation interface, a formula command, or a text value;
a description value associated with the at least one of: the component of the extension creation interface, the formula command, or the text value; or
a code example associated with the at least one of: the component of the extension creation interface, the formula command, or the text value.

### Claim 29 (depends on 1)

The system of claim 1, wherein the extension creation interface is configured to limit access to an external data access value to a defined external data component of the extension creation interface.
