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
This Office Action corresponds to application 19/246,296 which was filed on 6/23/2025 and is a CON of 18/622,390 filed 3/29/2024 which is a CON of 14/980,939 filed 12/28/2015. Claims 1-20 are currently pending.
Claim Rejections - 35 USC § 102
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 (i.e., changing from AIA to pre-AIA ) 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.
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.
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claim(s) 1-20 is/are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Savage et al. (US2014/0258972), hereinafter Savage.
Regarding Claim 1:
Savage teaches:
A method comprising:
sending to a content management system, a request for an embed code, wherein the embed code allows a user account associated with the content management system to publish a content item associated with the content management system on a web page hosted on a third-party server distinct from the content management system (Savage, figure 7, [0015, 0033, 0037, 0082], note receiving a request identifying a target content and generating code which corresponds to a software widget that enables access to, e.g., publishes, the target content, which is interpreted as a request for an embed code; note web pages on third-party servers may use the embedded widget code);
receiving, from the content management system, the embed code (Savage, figures 5A-5B and 7, [0033, 0037, 0058-0067], note receiving a request identifying a target content, generating code which corresponds to a software widget, and receiving/embedding code into a third party webpage);
providing for display a preview of the content item based on the embed code (Savage, figures 5A-5C and 7, [0027, 0037, 0058-0067, 0072-0076], note option to preview the software widget; note the widget may allow user to preview the content item);
receiving an indication of a selected option associated with the content item, wherein the selected option includes at least updating access permissions associated with the content item (Savage, figure 4 and 5A-5C, [0028, 0037, 0044, 0058-0067, 0072-0076], note setting permissions for content items; note permission may be set for the workspace or individually on a per item basis; note permission control module in the widget generation engine; note customization of the widget include adjusting permission levels);
creating an updated embed code by dynamically updating the embed code to reflect the selected option (Savage, figure 4 and 5A-5C, [0028, 0037, 0044, 0058-0067, 0072-0076], note setting permissions for content items; note permission may be set for the workspace or individually on a per item basis; note permission control module in the widget generation engine; note customization of the widget include adjusting permission levels; note generating the embedded code after customizing the widget);
receiving, from the content management system, an updated embed code, wherein the updated embed code is updated to reflect the selected option (Savage, figure 4 and 5A-5C, [0037, 0044, 0058-0067, 0072-0076], note setting permissions for content items; note permission may be set for the workspace or individually on a per item basis; note permission control module in the widget generation engine; note customization of the widget include adjusting permission levels; note generating the embedded code after customizing the widget; note the user may receive the updated code after customization, e.g., copying code to clipboard); and
providing for display of the updated embed code (Savage, figure 4 and 5A-5C, [0037, 0044, 0058-0067, 0072-0076], note generating and providing the updated embed code; note displaying the code and the updated widget).
Regarding Claim 2:
Savage shows the method as disclosed above;
Savage further teaches:
wherein the selected option also includes allowing a second user account to access the content item (Savage, figure 4 and 5A-5C, [0028, 0037, 0044, 0058-0067, 0072-0076], note setting permissions for content items; note permission may be set for the workspace or individually on a per item basis; note permission control module in the widget generation engine; note customization of the widget include adjusting permission levels; note permission levels allow access for other users; note allow sharing option would also allow a second user to access the content item).
Regarding Claim 3:
Savage shows the method as disclosed above;
Savage further teaches:
receiving an indication that the user account copied the updated embed code (Savage, figure 4 and 5A-5C, [0037, 0044, 0058-0067, 0072-0076], note customization of the widget include adjusting permission levels; note generating the embedded code after customizing the widget; note the user may receive the updated code after customization, e.g., copying code to clipboard; note the prompt with an option to “copy to clipboard” for the updated embedded code, when the user selects the “copy to clipboard” option it is interpreted as an indication that the user account copied the updated code); and
inserting the updated embed code into the web page (Savage, figure 4 and 5A-5C, [0037, 0044, 0058-0067, 0072-0076], note customization of the widget include adjusting permission levels; note generating the embedded code after customizing the widget; note the user may receive the updated code after customization, e.g., copying code to clipboard, and insert it into the web page).
Regarding Claim 4:
Savage shows the method as disclosed above;
Savage further teaches:
generating an updated preview based on the updated embed code (Savage, figure 4 and 5A-5C, [0037, 0044, 0058-0067, 0072-0076], note option to preview the widget which generates and displays an updated preview based on the updated embedded code); and
providing for display of the updated preview (Savage, figure 4 and 5A-5C, [0037, 0044, 0058-0067, 0072-0076], note option to preview the widget which generates and displays an updated preview based on the updated embedded code).
Regarding Claim 5:
Savage shows the method as disclosed above;
Savage further teaches:
receiving an indication of a selected second option associated with the content item (Savage, figure 4 and 5A-5C, [0028, 0037, 0044, 0058-0067, 0072-0076], note customizing the widget include selecting options associated with the content item, such as allowing downloading, color, widget size, etc.); and
creating a second updated embed code by dynamically updating the updated embed code to reflect the selected second option (Savage, figure 4 and 5A-5C, [0028, 0037, 0044, 0058-0067, 0072-0076], note customizing the widget include selecting options associated with the content item, such as allowing downloading, color, widget size, etc.; note generating the embedded code after customizing the widget, which would be a second updated code when done after a first customization).
Regarding Claim 6:
Savage shows the method as disclosed above;
Savage further teaches:
wherein the access permissions prevent a first user account from modifying the content item (Savage, figure 4 and 5A-5C, [0028, 0037, 0044, 0058-0067, 0072-0076], note setting permissions for content items; note permission may be set for the workspace or individually on a per item basis; note permission control module in the widget generation engine; note customization of the widget include adjusting permission levels; note controlling users’ ability to edit/modify the item by controlling widget tool functionalities like editing the file).
Regarding Claim 7:
Savage shows the method as disclosed above;
Savage further teaches:
rendering a graphical element for selecting the selected option associated with the content item (Savage, figure 4 and 5A-5C, [0028, 0037, 0044, 0058-0067, 0072-0076], note user interfaces for selecting the options associated with the content item).
Claim 8 discloses substantially the same limitations as claim 1 respectively, except claim 8 is directed to a non-transitory computer readable medium with memory and a processor (Savage, figure 8, note processor and memory) while claim 1 is directed to a method. Therefore claim 8 is rejected under the same rationale set forth for claim 1.
Claim 9 discloses substantially the same limitations as claim 2 respectively, except claim 9 is directed to a non-transitory computer readable medium with memory and a processor (Savage, figure 8, note processor and memory) while claim 2 is directed to a method. Therefore claim 9 is rejected under the same rationale set forth for claim 2.
Claim 10 discloses substantially the same limitations as claim 7 respectively, except claim 10 is directed to a non-transitory computer readable medium with memory and a processor (Savage, figure 8, note processor and memory) while claim 7 is directed to a method. Therefore claim 10 is rejected under the same rationale set forth for claim 7.
Claim 11 discloses substantially the same limitations as claim 4 respectively, except claim 11 is directed to a non-transitory computer readable medium with memory and a processor (Savage, figure 8, note processor and memory) while claim 4 is directed to a method. Therefore claim 11 is rejected under the same rationale set forth for claim 4.
Claim 12 discloses substantially the same limitations as claim 5 respectively, except claim 12 is directed to a non-transitory computer readable medium with memory and a processor (Savage, figure 8, note processor and memory) while claim 5 is directed to a method. Therefore claim 12 is rejected under the same rationale set forth for claim 5.
Claim 13 discloses substantially the same limitations as claim 6 respectively, except claim 13 is directed to a non-transitory computer readable medium with memory and a processor (Savage, figure 8, note processor and memory) while claim 6 is directed to a method. Therefore claim 13 is rejected under the same rationale set forth for claim 6.
Claim 14 discloses substantially the same limitations as claim 7 respectively, except claim 14 is directed to a non-transitory computer readable medium with memory and a processor (Savage, figure 8, note processor and memory) while claim 7 is directed to a method. Therefore claim 14 is rejected under the same rationale set forth for claim 7.
Claim 15 discloses substantially the same limitations as claim 1 respectively, except claim 15 is directed to a system with memory and a processor (Savage, figure 8, note processor and memory) while claim 1 is directed to a method. Therefore claim 15 is rejected under the same rationale set forth for claim 1.
Claim 16 discloses substantially the same limitations as claim 2 respectively, except claim 16 is directed to a system with memory and a processor (Savage, figure 8, note processor and memory) while claim 2 is directed to a method. Therefore claim 16 is rejected under the same rationale set forth for claim 2.
Claim 17 discloses substantially the same limitations as claim 3 respectively, except claim 17 is directed to a system with memory and a processor (Savage, figure 8, note processor and memory) while claim 3 is directed to a method. Therefore claim 17 is rejected under the same rationale set forth for claim 3.
Claim 18 discloses substantially the same limitations as claims 5 and 3 respectively, except claim 18 is directed to a system with memory and a processor (Savage, figure 8, note processor and memory) while claims 5 and 3 is directed to a method. Therefore claim 18 is rejected under the same rationale set forth for claims 5 and 3.
Claim 19 discloses substantially the same limitations as claim 6 respectively, except claim 19 is directed to a system with memory and a processor (Savage, figure 8, note processor and memory) while claim 6 is directed to a method. Therefore claim 19 is rejected under the same rationale set forth for claim 6.
Claim 20 discloses substantially the same limitations as claim 4 respectively, except claim 20 is directed to a system with memory and a processor (Savage, figure 8, note processor and memory) while claim 4 is directed to a method. Therefore claim 20 is rejected under the same rationale set forth for claim 4.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Zhang et al. (US10102388) teaches generation of webpage widgets;
Any inquiry concerning this communication or earlier communications from the examiner should be directed to JOHN J MORRIS whose telephone number is (571)272-3314. The examiner can normally be reached M-F 6:00-2:00 PM EST.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, James Trujillo can be reached at 571-272-3677. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/JOHN J MORRIS/Examiner, Art Unit 2151 6/10/2026
/James Trujillo/Supervisory Patent Examiner, Art Unit 2151
Prosecution Insights