Issue#364 - Video Analytics additions for ExperienceEvent - June 29th Milestone #417

cdegroot-adobe · 2018-06-20T18:27:15Z

Issue #364
What are the schemas that are affected by the issue
/context/experienceevent.schema.json

What are examples of products that are impacted by the issue
Video Analytics
Video Ads
Media marketing in Target

* no metric definitions

…VideoAnalytics/xdm-schemas into media-analytics-schemas

sdk->playerSDK removed vhl to put it in a different branch/PR as a vendor extension.

Schema count is now 208

cdegroot-adobe · 2018-06-20T19:12:22Z

@kstreeter @fmeschbe - Please note that we are targeting these schemas for use in the next few weeks, so need to make every attempt to get them in the June 29th milestone.

kstreeter

Hey @cdegroot-adobe, I did a first pass on this. The primary thing I think we need to work through is the nomenclature around "media", "asset", and in some places "content". Clearly "asset" already means something in XDM, and we should avoid using that word for anything that doesn't align with its pre-existing usage.

I would suggest we try to organize our terminology around something like this:

Asset - technical information about the video/image/etc. like size, encoding, etc. Note this probably does not include its location, since the location used for delivery (ie the CDN) is independent of where it might be stored in a CMS or repository.
Title - title information like series titles, episode information, etc. This may also include external identifiers for 3rd-party title registrars (like GraceNote, EIDR)
Media Playback - details about the playback session, like where it was actually delivered from, how long, etc. This would probably also include the CMS ID (lets call it CMS ID, not "Content ID"!)

kstreeter · 2018-06-21T23:36:54Z

schemas/context/advertising-break.schema.json

+  "definitions": {
+    "adBreak": {
+      "properties": {
+        "@id": {


This should be format URI, or else be an xdm:id

Resolved, thanks, also updated examples.

kstreeter · 2018-06-21T23:37:35Z

schemas/context/advertising-break.schema.json

+        },
+        "xdm:podOffset": {
+          "title": "Ad Break Offset",
+          "type": "integer",


can we double check that this can't be a fractional second, and thus a number?

I can confirm this is always a whole number.

Ok, checked. Resolved.

kstreeter · 2018-06-21T23:49:26Z

schemas/context/media-timed-asset-reference.schema.json

+          "type": "string",
+          "description": "Program/Series Name."
+        },
+        "xdm:assetID": {


We need to reconcile the terminology between "asset ID" and "content ID" in this schema. In our content repository model, the items have an "assetID". But here we seem to be saying that the CMS ID is called a "Content ID".

@cosminci @gabebarcelos-adobe do we want to move to use s/content/asset/ in the schema names and identity here?

For Media Analytics, the assetID is reported through custom metadata, and will not be available in the majority of timed media experience events.
We could update the properties (name / title / description) to be more consistent with the existing schemas.

@cdegroot-adobe @kstreeter - I'm not sure I follow. Are you suggesting adding an existing schema like Video or Image as a sub-schema to these and moving the appropriate attributes under those? Or are we discussing more of nomenclature of the existing schema?

Hi @gabebarcelos-adobe, I am not actually suggesting we include existing schemas directly, since we don't actually have most of the properties of an asset item in these schema. So it is just nomenclature. The use of the term "asset" in these schemas is describing a very different concept than it does in the XDM asset schemas. Also, the use of the term isn't completely consistent within the new schemas themselves, with multiple concepts all being called "asset".

After a number of discussion @kstreeter is more comfortable with the usage of "asset" in this PR. He is also understanding that the Creative Cloud teams are also not having concerns with the usage from their reviews.

Issue considered closed.

I'm going to re-open it. I am OK calling it asset, but it can't be assetID, as that is already used in the asset schema. It needs a different/unique name unless you are using it the same way - then it's OK.

One possibility is to use Iptc4xmpExt:Identifier

The right solution seemed to be to move to the IPTC Series structure. This gave me a way to resolve showName and assetID in a consistent way.
"iptc4xmpExt:Series": {
"iptc4xmpExt:Name": "nba_highlights",
"iptc4xmpExt:Identifier": "http://espn.com/series-identifiers/2613953",
},

kstreeter · 2018-06-21T23:51:22Z

schemas/context/media-timed-asset-view-details.schema.json

+            "VOD": "Video-on-Demand",
+            "Live": "Live Streaming",
+            "Linear": "Linear playback of the media asset",
+            "UGG": "User-generated Content",


UG "C" or UG "G"?

Corrected enum s/UGC/UGG/

ogoldman · 2018-06-27T05:01:42Z

schemas/context/advertising-timed-asset-reference.schema.json

+          "type": "string",
+          "description": "Identifier of the ad asset."
+        },
+        "xdm:name": {


Shouldn't this be dc:title?

Corrected - done

ogoldman · 2018-06-27T05:01:54Z

schemas/context/advertising-timed-asset-reference.schema.json

+          "type": "string",
+          "description": "The friendly (human-readable) name of the ad asset."
+        },
+        "xdm:duration": {


Shouldn't this be xmpDM:duration?

ogoldman · 2018-06-27T05:04:17Z

It looks to me like we should make a sweep through this entire PR and update all properties that are defined in XMP vocabs to leverage the same. Many of the properties here appear to have definitions in the XMP Dynamic Media namespace--which shouldn't be a surprise! For reference, see https://wwwimages2.adobe.com/content/dam/acom/en/devnet/xmp/pdfs/XMP%20SDK%20Release%20cc-2016-08/XMPSpecificationPart2.pdf

lrosenthol

There are numerous problems that need to be correct with this PR, including some clear misunderstandings about how to model data in XDM and lack of usage of existing standards in the industry.

lrosenthol · 2018-06-27T11:03:41Z

schemas/context/advertising-break.schema.json

+          "type": "string",
+          "description": "Identifier of the ad break."
+        },
+        "xdm:podName": {


why podName and not just name?

moved to dc:title, github seems to have an issues as I am looking at this and not showing the change. It is definitely in the source files.

lrosenthol · 2018-06-27T11:03:56Z

schemas/context/advertising-break.schema.json

+          "type": "string",
+          "description": "The friendly name of the ad break."
+        },
+        "xdm:podOffset": {


again, why podOffset and not just offset?

moved to xdm:offset, github seems to have an issues as I am looking at this and not showing the change. It is definitely in the source files.

lrosenthol · 2018-06-27T11:04:40Z

schemas/context/advertising-timed-asset-reference.schema.json

+        "@id": {
+          "title": "Ad ID",
+          "type": "string",
+          "description": "Identifier of the ad asset."


is this a unique ID? Is it related to the AdID standard? Please clarify

The Ad ID is provided by Media Analytics customers when they track ads. It might be an internal ID from their CMS system, it might be from their ad provider (e.g. Freewheel) - there is no standardisation around this.

OK, then please clarify that in the description.

Improved - Closed

lrosenthol · 2018-06-27T11:05:51Z

schemas/context/advertising-timed-asset-view-details.schema.json

+          "type": "string",
+          "description": "The name of the player responsible for rendering the ad."
+        },
+        "xdm:podPosition": {


again, why pod?

lrosenthol · 2018-06-27T12:01:47Z

schemas/context/advertising-timed-asset-view-details.schema.json

+        "xdm:podPosition": {
+          "title": "Ad Position in Pod",
+          "type": "integer",
+          "description": "The position (index) of the ad inside the parent ad break. The first ad has index 0, the second 1, and so on."


Should this be index instead of position then? Position seems the wrong term

lrosenthol · 2018-06-27T12:21:53Z

schemas/data/stall-time.schema.json

+  "meta:extends": [
+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "Describes the duration in which the playback was stalled during playback.",


after seeing different schemas that only differ slightly, they should all be a single schema with different values and not separate schemas

This is a pattern that @trieloff introduced a while ago and is intended to provide the option to add additional metadata about the metrics so that design tools and automated processors can have more intelligence about the specifics of each metric.

lrosenthol · 2018-06-27T12:21:58Z

schemas/data/stalls.schema.json

+  "meta:extends": [
+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "The number of stall states that occurred during a playback session.",


after seeing different schemas that only differ slightly, they should all be a single schema with different values and not separate schemas

see response to schemas/data/stall-time.schema.json on the same comment.

lrosenthol · 2018-06-27T12:22:06Z

schemas/data/time-played.schema.json

+  "meta:extends": [
+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "Describes the amount of time spent by a user on a specific timed media asset.",


after seeing different schemas that only differ slightly, they should all be a single schema with different values and not separate schemas

see response to schemas/data/stall-time.schema.json on the same comment.

lrosenthol · 2018-06-27T12:22:12Z

schemas/data/time-to-start.schema.json

+  "meta:extends": [
+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "Describes the duration passed between video load and start.",


after seeing different schemas that only differ slightly, they should all be a single schema with different values and not separate schemas

see response to schemas/data/stall-time.schema.json on the same comment.

lrosenthol · 2018-06-27T12:22:18Z

schemas/data/total-time-played.schema.json

+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "Describes the total amount of time spent by a user on a specific timed media asset, which includes time spent watching ads.",
+  "definitions": {


after seeing different schemas that only differ slightly, they should all be a single schema with different values and not separate schemas

see response to schemas/data/stall-time.schema.json on the same comment.

cdegroot-adobe

We need to resolve the ITPC questions asap please.

cdegroot-adobe · 2018-07-09T18:01:57Z

schemas/context/advertising.schema.json

+        },
+        "xdm:clicks": {
+          "$ref": "https://ns.adobe.com/xdm/data/measure",
+          "description": "Click(s) actions on an advertisement."
        },
        "xdm:conversions": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",


It is, this is how we implement metrics across all the schemas in XC.

cdegroot-adobe · 2018-07-09T18:02:11Z

schemas/context/advertising.schema.json

        },
        "xdm:conversions": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",
-          "description": "A pre-defined action on a website triggered a conversion event to be fired"
+          "description": "A costumer pre-defined action(s) which triggers an event for performance evaluation."
        },
        "xdm:firstQuartiles": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",


It is, this is how we implement metrics across all the schemas in XC.

cdegroot-adobe · 2018-07-09T18:02:18Z

schemas/context/advertising.schema.json

        },
        "xdm:firstQuartiles": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",
-          "description": "A digital video ad has played through 25% of it's duration at normal speed."
+          "description": "A digital video ad has played through 25% of its duration at normal speed."
        },
        "xdm:impressions": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",


It is, this is how we implement metrics across all the schemas in XC.

cdegroot-adobe · 2018-07-09T18:02:23Z

schemas/context/advertising.schema.json

        },
        "xdm:firstQuartiles": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",
-          "description": "A digital video ad has played through 25% of it's duration at normal speed."
+          "description": "A digital video ad has played through 25% of its duration at normal speed."
        },
        "xdm:impressions": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",
          "description": "Impression(s) of an advertisement to an end user with the potential of being viewed."
        },
        "xdm:midpoints": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",


It is, this is how we implement metrics across all the schemas in XC.

cdegroot-adobe · 2018-07-09T18:02:29Z

schemas/context/advertising.schema.json

        },
        "xdm:impressions": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",
          "description": "Impression(s) of an advertisement to an end user with the potential of being viewed."
        },
        "xdm:midpoints": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",
-          "description": "A digital video ad has played through 50% of it's duration at normal speed."
+          "description": "A digital video ad has played through 50% of its duration at normal speed."
        },
        "xdm:starts": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",
          "description": "A digital video ad has started playing."
        },
        "xdm:thirdQuartiles": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",


It is, this is how we implement metrics across all the schemas in XC.

cdegroot-adobe · 2018-07-09T18:24:10Z

schemas/data/pause-time.schema.json

+  "meta:extends": [
+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "Describes the duration in which playback was paused by the user.",


It is, this is how we implement metrics across all the schemas in XC.

cdegroot-adobe · 2018-07-09T18:24:17Z

schemas/data/pauses.schema.json

+  "meta:extends": [
+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "The number of pause periods that occurred during playback.",


It is, this is how we implement metrics across all the schemas in XC.

cdegroot-adobe · 2018-07-09T18:24:23Z

schemas/data/progress10.schema.json

+  "meta:extends": [
+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "Indicates that the playhead passed the 10% marker of media based on stream length. The marker is only counted once, even if seeking backwards. If seeking forward, markers that are skipped are not counted.",


It is, this is how we implement metrics across all the schemas in XC.

cdegroot-adobe · 2018-07-09T18:24:29Z

schemas/data/progress95.schema.json

+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "Indicates that the playhead passed the 95% marker of media based on stream length. The marker is only counted once, even if seeking backwards. If seeking forward, markers that are skipped are not counted.",
+  "definitions": {


It is, this is how we implement metrics across all the schemas in XC.

cdegroot-adobe · 2018-07-09T18:24:35Z

schemas/data/resumes.schema.json

+  "meta:extends": [
+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "Marks each playback that was resumed after more than 30 minutes of buffer, pause, or stall period.",


It is, this is how we implement metrics across all the schemas in XC.

cdegroot-adobe · 2018-07-11T20:25:09Z

schemas/context/media-timed-asset-reference.schema.json

@@ -0,0 +1,173 @@
+{


@lrosenthol @ogoldman @cluby-adobe @cosminci - Please re-review this specific schema as we have adopted the IPTC standard in several places and I want you opinion on the correctness and if we can use other IPTC fields in cases we have not yet. Thanks C.

Note I will look to externalize the IPTC complex objects in the \schemas\external\iptc once I figureout what legal attribution is more appropriate.

lrosenthol

Much better! But still a few remaining items to resolve.

lrosenthol · 2018-07-12T17:54:36Z

schemas/context/advertising.schema.json

        },
        "xdm:conversions": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",
-          "description": "A pre-defined action on a website triggered a conversion event to be fired"
+          "description": "A costumer pre-defined action(s) which triggers an event for performance evaluation."


costumer -> customer

lrosenthol · 2018-07-12T17:57:58Z

schemas/context/media-timed-asset-reference.schema.json

+    "media-asset-reference": {
+      "properties": {
+        "@id": {
+          "title": "Content ID",


Why is this content ID and not assetID (which we already have)?

Yes, this is something that needs to align better. Converting to "Asset"

lrosenthol · 2018-07-12T18:00:47Z

schemas/context/media-timed-asset-reference.schema.json

+          "type": "integer",
+          "description": "Length of primary media asset in seconds."
+        },
+        "xdm:showName": {


Yes that is what I would think to use.

lrosenthol · 2018-07-12T18:02:21Z

schemas/context/media-timed-asset-reference.schema.json

+          "type": "string",
+          "description": "Program/Series Name."
+        },
+        "xdm:assetID": {


I'm going to re-open it. I am OK calling it asset, but it can't be assetID, as that is already used in the asset schema. It needs a different/unique name unless you are using it the same way - then it's OK.

lrosenthol · 2018-07-12T18:03:20Z

schemas/context/media-timed-asset-reference.schema.json

+          "type": "string",
+          "description": "Program/Series Name."
+        },
+        "xdm:assetID": {


One possibility is to use Iptc4xmpExt:Identifier

lrosenthol · 2018-07-12T18:12:03Z

schemas/context/experienceevent.example.5.json

+        },
+        "xdm:broadcastNetwork": "nbcu",
+        "xdm:adLoadType": "2",
+        "xdm:dayPart": "DAY",


I don't see dayPart defined anywhere in a schema...

lrosenthol · 2018-07-12T18:12:13Z

schemas/context/experienceevent.example.6.json

+        },
+        "xdm:broadcastNetwork": "nbcu",
+        "xdm:adLoadType": "2",
+        "xdm:dayPart": "DAY",


I don't see dayPart defined anywhere in a schema...

lrosenthol · 2018-07-12T18:12:23Z

schemas/context/media-timed-asset-view-details.example.1.json

+  },
+  "xdm:broadcastNetwork": "nbcu",
+  "xdm:adLoadType": "2",
+  "xdm:dayPart": "DAY",


I don't see dayPart defined anywhere in a schema...

lrosenthol · 2018-07-12T18:12:37Z

schemas/context/media-timed.example.1.json

+    },
+    "xdm:broadcastNetwork": "nbcu",
+    "xdm:adLoadType": "2",
+    "xdm:dayPart": "DAY",


I don't see dayPart defined anywhere in a schema...

lrosenthol · 2018-07-12T18:12:46Z

schemas/context/media.example.1.json

+      },
+      "xdm:broadcastNetwork": "nbcu",
+      "xdm:adLoadType": "2",
+      "xdm:dayPart": "DAY",


I don't see dayPart defined anywhere in a schema...

"iptc4xmpExt:Series": { "iptc4xmpExt:Name": "nba_highlights", "iptc4xmpExt:Identifier": "http://espn.com/series-identifiers/2613953", },

cdegroot-adobe

I think that we have resolved the outstanding questions. I will log issues for items to track which are larger then this PR. But I do not believe this PR is blocked form merging because of them.

cdegroot-adobe · 2018-07-12T20:25:53Z

schemas/context/advertising.schema.json

        },
        "xdm:completes": {
+          "title": "Completes",
+          "$ref": "https://ns.adobe.com/xdm/data/measure",


cdegroot-adobe · 2018-07-12T20:26:01Z

schemas/context/advertising.schema.json

+        },
+        "xdm:federated": {
+          "title": "Federated",
+          "$ref": "https://ns.adobe.com/xdm/data/measure",


cdegroot-adobe · 2018-07-12T20:26:07Z

schemas/context/advertising.schema.json

+          "description": "Indicates if an experience event was created through data federation (data sharing between customers)."
+        },
+        "xdm:clicks": {
+          "$ref": "https://ns.adobe.com/xdm/data/measure",


cdegroot-adobe · 2018-07-12T20:26:15Z

schemas/context/advertising.schema.json

+        },
+        "xdm:clicks": {
+          "$ref": "https://ns.adobe.com/xdm/data/measure",
+          "description": "Click(s) actions on an advertisement."
        },
        "xdm:conversions": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",


cdegroot-adobe · 2018-07-12T20:26:22Z

schemas/context/advertising.schema.json

        },
        "xdm:conversions": {
          "$ref": "https://ns.adobe.com/xdm/data/measure",
-          "description": "A pre-defined action on a website triggered a conversion event to be fired"
+          "description": "A costumer pre-defined action(s) which triggers an event for performance evaluation."


cdegroot-adobe · 2018-07-12T21:07:12Z

schemas/data/stall-time.schema.json

+  "meta:extends": [
+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "Describes the duration in which the playback was stalled during playback.",


cdegroot-adobe · 2018-07-12T21:07:37Z

schemas/data/stalls.schema.json

+  "meta:extends": [
+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "The number of stall states that occurred during a playback session.",


cdegroot-adobe · 2018-07-12T21:07:46Z

schemas/data/time-played.schema.json

+  "meta:extends": [
+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "Describes the amount of time spent by a user on a specific timed media asset.",


cdegroot-adobe · 2018-07-12T21:07:51Z

schemas/data/time-to-start.schema.json

+  "meta:extends": [
+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "Describes the duration passed between video load and start.",


cdegroot-adobe · 2018-07-12T21:07:58Z

schemas/data/total-time-played.schema.json

+    "https://ns.adobe.com/xdm/data/metricdefinition"
+  ],
+  "description": "Describes the total amount of time spent by a user on a specific timed media asset, which includes time spent watching ads.",
+  "definitions": {


lrosenthol · 2018-07-13T03:11:35Z

Thanks Chris - all good!
Shall I merge it @cdegroot-adobe ?

… that we can have more time to review and get it right.

… future one so that we can have more time to review and get it right.

cdegroot-adobe · 2018-07-13T18:48:00Z

@fmeschbe I have created a new PR with the 4 properties that did not stabilize adequately during the review cycle. #433

This PR #417 is ready to merge now.

…count. Corrected example for rating.

Cosmin Ciobanu and others added 14 commits June 15, 2018 11:05

proposal #1

3b01868

* no metric definitions

first set of metric definitions

9c65fb2

1

0195807

2

6cd42f4

proposal #1

914f0b7

* no metric definitions

first set of metric definitions

198e6bd

Run npm run lint

5cfcf71

Merge branch 'media-analytics-schemas' of https://git.corp.adobe.com/…

8b07ef5

…VideoAnalytics/xdm-schemas into media-analytics-schemas

Corrected naming, removed undefined fields in example for errors.

102829d

sdk->playerSDK removed vhl to put it in a different branch/PR as a vendor extension.

Removed files that did were duplicates due to media-timed renaming

b686ffc

Extracted the advertising-timed schemas out of advertising.schema.json

d614976

typo

e910ee7

typo

94a3b87

Merge branch 'master' into final-PR-to-Adobe-WG

ab9e445

cdegroot-adobe requested review from lrosenthol and kstreeter June 20, 2018 18:27

Update package.json

c934240

Schema count is now 208

cdegroot-adobe changed the title ~~Issue#364 - Video Analytics additions for ExperienceEvent~~ Issue#364 - Video Analytics additions for ExperienceEvent - June 29th Milestone Jun 20, 2018

kstreeter reviewed Jun 22, 2018

View reviewed changes

chrisdegroot added 2 commits June 22, 2018 14:45

Added uri format to @id in advertising-break schema

7e1cd04

Corrected enum s/UGC/UGG/

Updated ad-break examples to be URIs

ff1e440

ogoldman reviewed Jun 27, 2018

View reviewed changes

lrosenthol requested changes Jun 27, 2018

View reviewed changes

pr feedback #1

1ab8e76

cdegroot-adobe commented Jul 9, 2018

View reviewed changes

Cosmin Ciobanu added 2 commits July 11, 2018 11:12

update several properties to follow ITPC standard

c5e4091

fix validation issues

1271312

Corrected example type

938355b

cdegroot-adobe commented Jul 11, 2018

View reviewed changes

lrosenthol requested changes Jul 12, 2018

View reviewed changes

chrisdegroot added 5 commits July 12, 2018 15:33

Removed "xdm:dayPart" from examples.

5ba57bc

Corrected examples

f65652c

Corrected description of

71d1563

Changed the title of @id from "Content ID" to "Asset ID"

d42e603

Moved ShowName and assetID to be an IPTC Series structure.

e9ac45a

"iptc4xmpExt:Series": { "iptc4xmpExt:Name": "nba_highlights", "iptc4xmpExt:Identifier": "http://espn.com/series-identifiers/2613953", },

cdegroot-adobe commented Jul 12, 2018

View reviewed changes

chrisdegroot added 3 commits July 12, 2018 17:12

Corrected examples, typo

06f01ba

Merge remote-tracking branch 'upstream/master' into final-PR-to-Adobe-WG

0214f1d

Updated change log

8464282

ogoldman approved these changes Jul 12, 2018

View reviewed changes

lrosenthol approved these changes Jul 13, 2018

View reviewed changes

fmeschbe added blocked Blocked due to another open issue v0.9.3 Scheduled for v0.9.3 and removed blocked Blocked due to another open issue labels Jul 13, 2018

chrisdegroot added 3 commits July 13, 2018 14:31

Moved airDate and digitalDate out of this PR and into a future one so…

443cd81

… that we can have more time to review and get it right.

Moved mediaSegment and bitrateAverageBucket out of this PR and into a…

50aa3db

… future one so that we can have more time to review and get it right.

Updated package schema count

9b103db

chrisdegroot added 4 commits July 13, 2018 15:37

Extracted the IPTC abstract schemas tot he \external\iptc folder.

d08209f

Added rating schema

f33057a

added iptc.org to the validator. Incremented the package.json schema …

a859d51

…count. Corrected example for rating.

typo

91651f1

fmeschbe mentioned this pull request Jul 14, 2018

Video Analytics additions for ExperienceEvent, part 2 #435

Open

Merge branch 'master' into final-PR-to-Adobe-WG

2ec0440

fmeschbe merged commit ea50992 into adobe:master Jul 14, 2018

fmeschbe mentioned this pull request Jul 14, 2018

Video Analytics additions for ExperienceEvent #364

Closed

Issue#364 - Video Analytics additions for ExperienceEvent - June 29th Milestone #417

Issue#364 - Video Analytics additions for ExperienceEvent - June 29th Milestone #417

Conversation

cdegroot-adobe commented Jun 20, 2018

cdegroot-adobe commented Jun 20, 2018

kstreeter left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

cosminci Jun 25, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ogoldman commented Jun 27, 2018

lrosenthol left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

cdegroot-adobe left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

lrosenthol left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

cosminci Jun 25, 2018 •

edited

Loading