Skip to content

feat: Support location context hint in platform-initiated requests #642

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jingyli wants to merge 3 commits into
base: main
Choose a base branch
from
Open

feat: Support location context hint in platform-initiated requests #642

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c8b13d1
Pulling out the location hint change into a standalone PR.
jingyli Jul 27, 2026
faf7833
Tweak the description of context.location to be more explicit in its …
jingyli Jul 28, 2026
da248be
Merge branch 'main' into location-context
jingyli Jul 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions source/schemas/shopping/types/context.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,10 @@
"type": "object",
"additionalProperties": true,
"properties": {
"location": {
"type": "string",
"description": "Reference to the specific location (e.g., physical store, property, or restaurant) associated with the user. A common example in retail shopping is the default home store selected and saved by the user on their profile when purchasing grocery."
},
"intent": {
"type": "string",
"description": "Background context describing buyer's intent (e.g., 'looking for a gift under $50', 'need something durable for outdoor use'). Informs relevance, recommendations, and personalization."
Comment on lines 13 to 22

@gsmith85 gsmith85 Jul 29, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with @jingyli that cross-referencing capabilities within schema descriptions introduces potential coupling between capabilities, which we want to avoid.

Still, there is an opportunity to create conceptual connectivity across specifications, which seems to be the crux of @jamesandersen's comment. Instead of cross-referencing capabilities in context.location.description.

I suggest we establish Location as a first-class commerce concept in UCP via the Glossary:

   Term     | Acronym | Definition
  ----------|---------|---------------------------------------------------------------------------------------------------
   Location | -       | A physical entity (e.g., retail store, restaurant, pickup locker, warehouse) identified by a
            |         | stable, business-scoped string (id). Referenced across UCP for buyer localization
            |         | (context.location), store pickup fulfillment, and location discovery.
  ──────

This keeps the JSON Schema decoupled while giving implementers a clear, unified definition of what a location identifier represents across all UCP flows.

@jingyli jingyli Jul 30, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A fair callout, I actually think establishing this as a UCP concept should belong to #589 instead of this PR here (as that is where the overarching capability will be introduced). PTAL at 5e3ff05!

Expand Down
Loading