DETAILED ACTION
Status of Claims
Claims 1-17 are pending.
Claims 1-17 are rejected.
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 .
Claim Objections
Claim 4 is objected to because of the following informalities:
Claim 4 recites the limitation “different from than a default language” in line 4 of the claim.
Appropriate correction is required.
Claim Rejections - 35 USC § 102
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.
Claims 1-17 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Snitko et al. (US 10,235,363, hereinafter “Snitko”).
In regards to claim 1, Snitko teaches a method comprising:
receiving indication of a desired localization for an application from a user via a first graphical user interface (GUI) element of a first GUI display associated with the application at a client device, wherein the desired localization is different from a reference localization associated with the user (Snitko; col. 7, line 44 – col. 8, line 3);
in response to the indication of the desired localization, retrieving, from a database system over a network, metadata associated with the desired localization for one or more fields of an object associated with an application platform at the database system (Snitko; col. 3, lines 21-48; col. 5, lines 10-37);
retrieving, from the database system, one of more field values for the one or more fields of a data record corresponding to an instance of the object (Snitko; col. 5, lines 38-48; col. 6, lines 18-56; col. 7, line 44 – col. 8, line 3); and
generating, at the client device, a second GUI display associated with the application comprising a graphical representation of the data record at the database system utilizing the metadata associated with the desired localization retrieved from the database system and one or more field values for the one or more fields of the data record (Snitko; col. 5, lines 38-48; col. 7, line 44 – col. 8, line 3).
In regards to claim 2, Snitko teaches the method of claim 1, wherein the indication comprises a uniform resource locator (URL) query parameter appended to a URL address associated with the second GUI display (Snitko; col. 7, lines 44-50).
In regards to claim 3, Snitko teaches the method of claim 2, wherein generating the second GUI display comprises a client application at the client device executing a web component associated with the second GUI display to generate a GUI display component comprising label metadata for a field of the data record and a field value of the one or more field values for the field of the one or more fields of the data record (Snitko; col. 2, lines 53-67; col. 5, lines 38-48; col. 7, line 44 – col. 8, line 3).
In regards to claim 4, Snitko teaches the method of claim 3, further comprising storing the metadata associated with the desired localization in a cache at the client device (Snitko; col. 3, lines 38-48), wherein:
the metadata comprises a second label for a second field of the data record in a language different from than a default language associated with the user (Snitko; col. 4, lines 28-40; col. 7, line 44 – col. 8, line 3); and
generating the second GUI display comprises the client application at the client device executing a second web component associated with the second GUI display to generate a second GUI display component comprising the second label for the second field of the data record and a second field value of the one or more field values for the second field of the one or more fields of the data record, wherein configured web component metadata of the second web component is configurable to reference the cache to obtain the second label for the second field of the data record (Snitko; col. 2, lines 53-67; col. 4, lines 6-27; col. 5, lines 38-39; col. 6, lines 56-60).
In regards to claim 5, Snitko teaches the method of claim 4, further comprising providing the indication of the desired localization to a third web component associated with the second GUI display (Snitko; col. 7, line 44 – col. 8, line 3), wherein the client application at the client device executes the third web component to retrieve the metadata comprising a third label for a third field of the data record in the language different from than the default language associated with the user from the database system (Snitko; col. 3, lines 21-48; col. 7, line 56 – col. 8, line 3) and generate a third GUI display component comprising the third label for the third field of the data record and a third field value of the one or more field values for the third field of the one or more fields of the data record (Snitko; col. 2, lines 53-67; col. 4, lines 6-27; col. 5, lines 38-39).
In regards to claim 6, Snitko teaches the method of claim 1, further comprising storing the metadata associated with the desired localization in a cache at the client device (Snitko; col. 3, lines 38-48), wherein:
the metadata comprises a label for a field of the data record in a different language than a default language associated with the user (Snitko; col. 4, lines 28-40; col. 7, line 44 – col. 8, line 3); and
generating the second GUI display comprises a client application at the client device executing a web component associated with the second GUI display to generate a GUI display component comprising the label for the field of the data record in the different language and a field value of the one or more field values for the field of the one or more fields of the data record, wherein configured web component metadata of the web component is configurable to reference the cache to obtain the label for the field of the data record (Snitko; col. 2, lines 53-67; col. 4, lines 6-27; col. 5, lines 38-39; col. 6, lines 56-60).
In regards to claim 7, Snitko teaches the method of claim 1, further comprising providing the indication of the desired localization to a web component associated with the second GUI display (Snitko; col. 7, line 44 – col. 8, line 3), wherein:
retrieving the metadata comprises a client application at the client device executing the web component to retrieve a label for a field of the data record in a different language than a default language associated with the user (Snitko; col. 3, lines 21-48; col. 7, line 44 – col. 8, line 3); and
generating the second GUI display comprises the client application executing presentation code of the web component to generate a GUI display component on the second GUI display comprising the label for the field of the data record in the different language and a field value of the one or more field values for the field of the one or more fields of the data record (Snitko; col. 2, lines 53-67; col. 4, lines 6-27; col. 5, lines 38-39).
Claims 8-14 are rejected using the same citations as claims 1-7, respectively.
Claims 15-17 are rejected using the same citations as claims 1-3, respectively.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Kavita Stanley whose telephone number is (571)272-8352. The examiner can normally be reached M-F 9:30am-6pm.
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, Cordelia (Dede) Zecher can be reached at 571-272-7771. 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.
/KAVITA STANLEY/Supervisory Patent Examiner, Art Unit 2153
Prosecution Insights