§ 5.2 — App identity on properties (#15)

examples/line-item-ctv.yaml

@@ -2,7 +2,14 @@
 line_item_id:   "weather-app-ctv"
 status:         published
 channel:        ctv
-properties:     { available: [{ id: "weather-app" }], included: ["weather-app"] }
+properties:
+  available:
+    - id: "weather-app"
+      apps:
+        - { platform: roku, bundle: "000000",
+            storeurl: "https://channelstore.roku.com/details/000000/weather-app",
+            developer_domain: "weather-app.example" }
+  included: ["weather-app"]
 environments:   { available: ["ctv"], included: ["ctv"] }
 formats:        { available: ["ctv/instream-15s", "ctv/instream-30s"],
                   included: ["ctv/instream-15s"],

spec/CHANGELOG.md

@@ -5,6 +5,10 @@ issue that caused it, so the comment record and the spec history line up.
 
 ## [Unreleased]
 
+- § 5.2 — Properties can carry `apps[]` for app and CTV inventory, keyed as
+  OpenRTB 2.6 `app`, and the Summary Representation lists the app identifier
+  ([#15](https://github.com/IABTechLab/OpenProposal/issues/15)).
+
 ## [3.0-draft-1] — 2026-09-22
 
 Initial draft published for public comment. Ported from the working-group

spec/openproposal-3.0.md

@@ -76,7 +76,8 @@ Every line item has two representations.
 sellers' shelves. A catalog response MAY return it. It MUST contain, per line
 item:
 
-`line_item_id` · `channel` · `content_detail` · property names ·
+`line_item_id` · `channel` · `content_detail` · property names and
+`apps[].platform` / `apps[].bundle` ·
 `formats.included[]` · `pricing.cost_method` · `pricing.gross_rate` ·
 `min_spend` · `addressable_scale` · `committed_metrics[]` ·
 `transaction_mechanism`
@@ -222,10 +223,24 @@ channel.
 
 | Field | Type | Mutability | Description |
 | :--- | :--- | :--- | :--- |
-| `properties` | Object | selectable | `available[]` of `{ id, name, domains, supported_formats }`, `included[]`, `pricing`, `max_select` |
+| `properties` | Object | selectable | `available[]` of `{ id, name, domains, apps, supported_formats }`, `included[]`, `pricing`, `max_select`. Each property MUST carry `domains`, `apps` or both |
 | `content_detail` | Object | seller-set | Shows, series, sections, network verticals |
 | `environments` | Object | selectable | `available[]` from `web_desktop` \| `web_mobile` \| `app_mobile` \| `ctv` \| `dooh` \| `audio_streaming` |
 
+**App identity.** `apps[]` identifies the apps behind a property sold in
+`app_mobile` or `ctv`. Keys follow the OpenRTB 2.6 `app` object where one
+exists.
+
+| Key | Required | Meaning |
+| :--- | :--- | :--- |
+| `platform` | REQUIRED | The app store that issued `bundle`: `ios` (Apple App Store) \| `android` (Google Play) \| `roku` (Roku Channel Store) \| `fire_tv` (Amazon Appstore) \| `samsung_tv` (Samsung Apps TV) and other stores. A `bundle` is unique only within its store. No OpenRTB equivalent |
+| `bundle` | REQUIRED | Store ID. As OpenRTB 2.6 `app.bundle` |
+| `storeurl` | OPTIONAL | Store listing URL. As `app.storeurl` |
+| `developer_domain` | RECOMMENDED | Developer domain from the store listing, against which `app-ads.txt` is checked. No OpenRTB equivalent: not `app.domain`, which is the domain of the app |
+
+Seller authorisation for an app is checked through `app-ads.txt` on its
+developer domain, not through the property's `domains`.
+
 ### 5.3 Audience reach
 
 | Field | Type | Mutability | Description |