# US 10,455,056 B2 · Cloud-based storage and interchange mechanism for design elements > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,455,056 B2 - Document ID: US10455056B2 - Status: Granted - Kind: B2 - Application number: 14/833,006 - Filed: 2015-08-21 - Published: 2017-02-23 - Granted: 2019-10-22 - Earliest claimed: 2015-08-21 - Assignees: Abobe Inc. - Applicants: Adobe Inc. - Inventors: Michael Smith; Sedat Akkus; Nayoung Kim; Lavanya Raghunath; Cynthia Kaschub; Srinivas Annam; Mark Shepherd; Jacob Surber; Glenn Ruehle; Glade Miller; George Comninos; Gavin Peacock - Web page: https://patentgrep.com/patent/US10455056B2 ## CPC - H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)} - H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes - H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] - H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks - H04L 61/4552: Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Techniques for sharing design elements between different applications and/or devices are provided. A design element is received from a first application as multiple representations, each of the multiple representations corresponding to a complementary storage format for the design element based on a design element type. The design element is stored as the multiple representations in a centrally stored library, the centrally stored library being shared among a plurality of applications. An indication to use the design element in a second application may be received. At least one of the multiple representations may be returned, as determined by the second application. ## Claims ### Claim 1 A method for sharing design elements comprising: receiving a design element from a first application, the design element representing a property or component embedded in a document; determining a design element type for the design element; generating, based on the design element type, multiple representations for the design element, each of the multiple representations corresponding to a storage format for the design element; storing the design element as the multiple representations in a centrally stored library, the centrally stored library being shared among a plurality of applications; receiving an indication to use the design element in a second application; and providing at least one of the stored multiple representations based on a compatibility with the second application. ### Claim 2 (depends on 1) The method of claim 1, further comprising: causing to be displayed, in a local library of the first application, the design element being stored in the centrally stored library; syncing the centrally stored library between the plurality of applications; and causing to be displayed, in a local library of the second application, the design element in the centrally stored library. ### Claim 3 (depends on 2) The method of claim 2, wherein the causing to be displayed, in a local library of the second application, the design element in the centrally stored library is configurable by a user. ### Claim 4 (depends on 2) The method of claim 2, further comprising: when a third application is incompatible with the design element type, preventing from being used, in a local library of the third application, the design element in the centrally stored library. ### Claim 5 (depends on 1) The method of claim 1, wherein the design element type is a style; and the design element stores style information. ### Claim 6 (depends on 1) The method of claim 1, wherein the design element type is a file; and the generating comprises determining the multiple representations based on at least one of mime type, file extension, and file format of file correspond to the design element. ### Claim 7 (depends on 1) The method of claim 1, the returning one of the multiple representations retrieving the multiple representations corresponding to the design element; determining an interoperability of each of the multiple representations with the second application; returning one of the multiple representations, the one of the multiple representations being determined based on the interoperability. ### Claim 8 (depends on 1) The method of claim 1, the returning one of the multiple representations retrieving the multiple representations corresponding to the design causing to be displayed the multiple representations in a ranked order; and returning one of the multiple representations based on a user selection. ### Claim 9 (depends on 8) The method of claim 8, wherein the multiple representations are ordered based on a level of detail. ### Claim 10 (depends on 1) The method of claim 1, further comprising: receiving another indication to change the design element from the first application; and replacing the multiple representations with new multiple representations corresponding to the changed design element. ### Claim 11 A computer-implemented method for storing design elements comprising: receiving a design element from a first application, the design element representing a property or component embedded in a document; determining a primary representation for the design element, the primary representation being a representation with a highest level of detail; and storing the design element as multiple representations in a centrally stored library, the multiple representations corresponding to the primary representation and one or more variations of the primary representation; the design element being available in a local library of a second application. ### Claim 12 (depends on 11) The method of claim 11, wherein the multiple representations of the design element are available as a single library item in the local library of the second application. ### Claim 13 (depends on 11) The method of claim 11, wherein the storing the design element comprises: storing the design element in a manifest file, wherein the manifest file references the multiple representations. ### Claim 14 (depends on 11) The method of claim 11, wherein the primary representation is a style, and the multiple representations comprise style information as key-value pairs. ### Claim 15 (depends on 11) The method of claim 11, wherein the second application uses a representation of the design element, the representation being stored as one of the multiple representations. ### Claim 16 (depends on 11) The method of claim 11, wherein the multiple representations comprise at least one rendition representation that is different from the primary representation. ### Claim 17 A system comprising: a processing device; and a non-transitory computer-readable medium communicatively coupled to the processing device, wherein the processing device is configured for executing instructions stored in the non-transitory computer-readable medium and thereby performing operations comprising: inputting a design element of a document to a first local library of a first application component, the design element representing a property or component embedded in the document; storing the design element as multiple representations to a centrally stored library component, each of the multiple representations corresponding to a storage format for the design element based on a design element type; and providing the design element in a selected representation from the multiple representations to a second local library of a second application component, the selected representation being compatible for use in a second application associated with the second application component. ### Claim 18 (depends on 17) The system of claim 17, wherein the operations further comprise: synchronizing the first local library with the centrally stored library component. ### Claim 19 (depends on 18) The system of claim 18, wherein the synchronizing further comprises: determining a new design element being input to the first local library; and sending the new design element to the centrally stored library component. ### Claim 20 (depends on 17) The system of claim 17, wherein the multiple representations comprise a primary representation and one or more other representations.