Open shashi-banger opened 7 months ago
@shashi-banger In the publication cap example, both caps are 10/1M. For better illustration, we can make them as {30/1M & 10/1W}.
@shashi-banger To support this, we will have to change the manner in which licences are given in amagi format.
Amagi format hierarchy: licenses -> platforms
<amagi:licenses>
<amagi:regions>
<amagi:includes amagi:value="US"/>
</amagi:regions>
<amagi:licensePeriod end="2023-09-20T00:00:00Z" start="2023-09-01T00:00:00Z" type="VOD">
<amagi:vodPlatforms>
<amagi:meta-value amagi:value="philo"/>
<amagi:meta-value amagi:value="fubo"/>
</amagi:vodPlatforms>
</amagi:licensePeriod>
<amagi:licensePeriod end="2023-08-01T00:00:00Z" start="2023-07-01T00:00:00Z" type="VOD">
<amagi:vodPlatforms>
<amagi:meta-value amagi:value="philo"/>
<amagi:meta-value amagi:value="fubo"/>
</amagi:vodPlatforms>
</amagi:licensePeriod>
</amagi:licenses>
Need to change to: platforms -> licenses
<amagi:licenses>
<amagi:vodPlatforms>
<amagi:meta-value amagi:value="philo">
<amagi:licensePeriod end="2023-09-20T00:00:00Z" start="2023-09-01T00:00:00Z" type="VOD" includeRegions="US">
<amagi:licensePeriod end="2023-08-01T00:00:00Z" start="2023-07-01T00:00:00Z" type="VOD" includeRegions="US">
</amagi:meta-value>
<amagi:meta-value amagi:value="fubo">
<amagi:licensePeriod end="2023-09-20T00:00:00Z" start="2023-09-01T00:00:00Z" type="VOD" includeRegions="US">
<amagi:licensePeriod end="2023-08-01T00:00:00Z" start="2023-07-01T00:00:00Z" type="VOD" includeRegions="US">
</amagi:meta-value>
</amagi:vodPlatforms>
</amagi:licenses>
@shashi-banger To support this, we will have to change the manner in which licences are given in amagi format.
Amagi format hierarchy: licenses -> platforms
<amagi:licenses> <amagi:regions> <amagi:includes amagi:value="US"/> </amagi:regions> <amagi:licensePeriod end="2023-09-20T00:00:00Z" start="2023-09-01T00:00:00Z" type="VOD"> <amagi:vodPlatforms> <amagi:meta-value amagi:value="philo"/> <amagi:meta-value amagi:value="fubo"/> </amagi:vodPlatforms> </amagi:licensePeriod> <amagi:licensePeriod end="2023-08-01T00:00:00Z" start="2023-07-01T00:00:00Z" type="VOD"> <amagi:vodPlatforms> <amagi:meta-value amagi:value="philo"/> <amagi:meta-value amagi:value="fubo"/> </amagi:vodPlatforms> </amagi:licensePeriod> </amagi:licenses>
Need to change to: platforms -> licenses
<amagi:licenses> <amagi:vodPlatforms> <amagi:meta-value amagi:value="philo"> <amagi:licensePeriod end="2023-09-20T00:00:00Z" start="2023-09-01T00:00:00Z" type="VOD" includeRegions="US"> <amagi:licensePeriod end="2023-08-01T00:00:00Z" start="2023-07-01T00:00:00Z" type="VOD" includeRegions="US"> </amagi:meta-value> <amagi:meta-value amagi:value="fubo"> <amagi:licensePeriod end="2023-09-20T00:00:00Z" start="2023-09-01T00:00:00Z" type="VOD" includeRegions="US"> <amagi:licensePeriod end="2023-08-01T00:00:00Z" start="2023-07-01T00:00:00Z" type="VOD" includeRegions="US"> </amagi:meta-value> </amagi:vodPlatforms> </amagi:licenses>
@shashi-banger , How this request will be getting translated to coverageRestrictions.
@mbm-c The above will translate to the following in amgrss
<amg:rights>
<amg:coverageRestrictions>
<amg:rightsStartDateTime>2023-09-01T00:00:00Z</amg:rightsStartDateTime>
<amg:rightsEndDateTime>2023-09-20T00:00:00Z</amg:rightsEndDateTime>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_US</amg:rightsTerritoryIncludes>
</amg:coverageRestrictions>
<amg:coverageRestrictions>
<amg:rightsStartDateTime>2023-07-01T00:00:00Z</amg:rightsStartDateTime>
<amg:rightsEndDateTime>2023-08-01T00:00:00Z</amg:rightsEndDateTime>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_US</amg:rightsTerritoryIncludes>
</amg:coverageRestrictions>
<amg:serviceId>AMGPLT1234</amg:serviceId>
<amg:serviceName>philo</amg:serviceName>
<amg:serviceType>VOD</amg:serviceType>
</amg:rights>
<amg:rights>
<amg:coverageRestrictions>
<amg:rightsStartDateTime>2023-09-01T00:00:00Z</amg:rightsStartDateTime>
<amg:rightsEndDateTime>2023-09-20T00:00:00Z</amg:rightsEndDateTime>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_US</amg:rightsTerritoryIncludes>
</amg:coverageRestrictions>
<amg:coverageRestrictions>
<amg:rightsStartDateTime>2023-07-01T00:00:00Z</amg:rightsStartDateTime>
<amg:rightsEndDateTime>2023-08-01T00:00:00Z</amg:rightsEndDateTime>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_US</amg:rightsTerritoryIncludes>
</amg:coverageRestrictions>
<amg:serviceId>AMGPLT4567</amg:serviceId>
<amg:serviceName>fubo</amg:serviceName>
<amg:serviceType>VOD</amg:serviceType>
</amg:rights>
Consider the example as shown below, of having multiple rights for the same service with different date ranges. Today we express the multiple rights for same service(platform or channel) as separate elements.
It would be nice to have rights for a given platform or channel expressed within a single element. If we use the the new elements
amg:coverageRestrictions
then the above will look as followsAlso there is a requirement for publication restrictions. If we want to associate one or more publication restrictions(frequency caps) we can do as follows