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.
<rss xmlns:amg="http://www.amagi.com/amgrss/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:amgt="http://www.amagi.com/amgrss/transient/" xmlns:mediat="http://www.amagi.com/mrss/transient/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:amagi="http://www.amagi.com/rss/namespace">
<!--Amagi RSS to Amagi Internal Feed-->
<channel>
<item amg:itemType="Episode">
<amg:longDescription>Chef Andrew Zimmern prepares the ultimate shore lunch of fried walleye filets, served with a tangy homemade tartar sauce, coleslaw, and crispy fried potatoes. Next, chef grills bone-in elk chops with a simple mustard glaze over hardwood charcoal.</amg:longDescription>
<amg:assetId>tmk-video-214b1e60d76f4101a4a5254f65fe0841</amg:assetId>
<amg:externalId label="TMSID" amg:idType="https://metadata.amagi.tv/skos/amagi_ebu_IdentifierTypeCS#_tmsid">EP036334800009</amg:externalId>
<media:description>Chef Andrew Zimmern cooks up some grilled Walleye and elk chops, over an open flame.</media:description>
<media:subTitle href="https://assets.tastemadecdn.net/files/ef749b/a8bf99407c80b27940ac/b0048a.scc" amg:lang="http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso639_1LanguageCodeCS#_en"/>
<amg:rights>
<amg:rightsStartDateTime>2035-01-01T00:00:00+00:00</amg:rightsStartDateTime>
<amg:rightsEndDateTime>2050-01-01T00:00:00+00:00</amg:rightsEndDateTime>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_US</amg:rightsTerritoryIncludes>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_CA</amg:rightsTerritoryIncludes>
<amg:rightsTerritoryExcludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_MX</amg:rightsTerritoryExcludes>
<amg:serviceId>roku</amg:serviceId>
<amg:serviceName>roku</amg:serviceName>
<amg:serviceType>VOD</amg:serviceType>
</amg:rights>
<amg:rights>
<amg:rightsStartDateTime>2050-01-01T00:00:00+00:00</amg:rightsStartDateTime>
<amg:rightsEndDateTime>2060-01-01T00:00:00+00:00</amg:rightsEndDateTime>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_US</amg:rightsTerritoryIncludes>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_CA</amg:rightsTerritoryIncludes>
<amg:rightsTerritoryExcludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_MX</amg:rightsTerritoryExcludes>
<amg:serviceId>roku</amg:serviceId>
<amg:serviceName>roku</amg:serviceName>
<amg:serviceType>VOD</amg:serviceType>
</amg:rights>
</item>
</channel>
</rss>
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 follows
<rss xmlns:amg="http://www.amagi.com/amgrss/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:amgt="http://www.amagi.com/amgrss/transient/" xmlns:mediat="http://www.amagi.com/mrss/transient/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:amagi="http://www.amagi.com/rss/namespace">
<!--Amagi RSS to Amagi Internal Feed-->
<channel>
<item amg:itemType="Episode">
<amg:longDescription>Chef Andrew Zimmern prepares the ultimate shore lunch of fried walleye filets, served with a tangy homemade tartar sauce, coleslaw, and crispy fried potatoes. Next, chef grills bone-in elk chops with a simple mustard glaze over hardwood charcoal.</amg:longDescription>
<amg:assetId>tmk-video-214b1e60d76f4101a4a5254f65fe0841</amg:assetId>
<amg:externalId label="TMSID" amg:idType="https://metadata.amagi.tv/skos/amagi_ebu_IdentifierTypeCS#_tmsid">EP036334800009</amg:externalId>
<media:description>Chef Andrew Zimmern cooks up some grilled Walleye and elk chops, over an open flame.</media:description>
<media:subTitle href="https://assets.tastemadecdn.net/files/ef749b/a8bf99407c80b27940ac/b0048a.scc" amg:lang="http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso639_1LanguageCodeCS#_en"/>
<amg:rights>
<amg:coverageRestrictions>
<amg:rightsStartDateTime>2035-01-01T00:00:00+00:00</amg:rightsStartDateTime>
<amg:rightsEndDateTime>2050-01-01T00:00:00+00:00</amg:rightsEndDateTime>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_US</amg:rightsTerritoryIncludes>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_CA</amg:rightsTerritoryIncludes>
<amg:rightsTerritoryExcludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_MX</amg:rightsTerritoryExcludes>
</amg:coverageRestrictions>
<amg:coverageRestrictions>
<amg:rightsStartDateTime>2050-01-01T00:00:00+00:00</amg:rightsStartDateTime>
<amg:rightsEndDateTime>2060-01-01T00:00:00+00:00</amg:rightsEndDateTime>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_US</amg:rightsTerritoryIncludes>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_CA</amg:rightsTerritoryIncludes>
<amg:rightsTerritoryExcludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_MX</amg:rightsTerritoryExcludes>
</amg:coverageRestrictions>
<amg:serviceId>roku</amg:serviceId>
<amg:serviceName>roku</amg:serviceName>
<amg:serviceType>VOD</amg:serviceType>
</amg:rights>
</item>
</channel>
</rss>
Also there is a requirement for publication restrictions. If we want to associate one or more publication restrictions(frequency caps) we can do as follows
<rss xmlns:amg="http://www.amagi.com/amgrss/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:amgt="http://www.amagi.com/amgrss/transient/" xmlns:mediat="http://www.amagi.com/mrss/transient/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:amagi="http://www.amagi.com/rss/namespace">
<!--Amagi RSS to Amagi Internal Feed-->
<channel>
<item amg:itemType="Episode">
<amg:longDescription>Chef Andrew Zimmern prepares the ultimate shore lunch of fried walleye filets, served with a tangy homemade tartar sauce, coleslaw, and crispy fried potatoes. Next, chef grills bone-in elk chops with a simple mustard glaze over hardwood charcoal.</amg:longDescription>
<amg:assetId>tmk-video-214b1e60d76f4101a4a5254f65fe0841</amg:assetId>
<amg:externalId label="TMSID" amg:idType="https://metadata.amagi.tv/skos/amagi_ebu_IdentifierTypeCS#_tmsid">EP036334800009</amg:externalId>
<media:description>Chef Andrew Zimmern cooks up some grilled Walleye and elk chops, over an open flame.</media:description>
<media:subTitle href="https://assets.tastemadecdn.net/files/ef749b/a8bf99407c80b27940ac/b0048a.scc" amg:lang="http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso639_1LanguageCodeCS#_en"/>
<amg:rights>
<amg:coverageRestrictions>
<amg:rightsStartDateTime>2035-01-01T00:00:00+00:00</amg:rightsStartDateTime>
<amg:rightsEndDateTime>2050-01-01T00:00:00+00:00</amg:rightsEndDateTime>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_US</amg:rightsTerritoryIncludes>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_CA</amg:rightsTerritoryIncludes>
<amg:rightsTerritoryExcludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_MX</amg:rightsTerritoryExcludes>
</amg:coverageRestrictions>
<amg:coverageRestrictions>
<amg:rightsStartDateTime>2050-01-01T00:00:00+00:00</amg:rightsStartDateTime>
<amg:rightsEndDateTime>2060-01-01T00:00:00+00:00</amg:rightsEndDateTime>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_US</amg:rightsTerritoryIncludes>
<amg:rightsTerritoryIncludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_CA</amg:rightsTerritoryIncludes>
<amg:rightsTerritoryExcludes>http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#_MX</amg:rightsTerritoryExcludes>
</amg:coverageRestrictions>
<amg:publicationRestrictions>
<amg:rightsStartDateTime>2050-01-01T00:00:00+00:00</amg:rightsStartDateTime>
<amg:rightsEndDateTime>2060-01-01T00:00:00+00:00</amg:rightsEndDateTime>
<amg:publicationCap>
<amg:publicationLimit>10</amg:publicationLimit>
<amg:publicationCapPeriod>1M</amg:publicationCapPeriod>
</amg:publicationCap>
<amg:publicationCap>
<amg:publicationLimit>10</amg:publicationLimit>
<amg:publicationCapPeriod>1M</amg:publicationCapPeriod>
</amg:publicationCap>
</amg:coverageRestrictions>
<amg:serviceId>roku</amg:serviceId>
<amg:serviceName>roku</amg:serviceName>
<amg:serviceType>VOD</amg:serviceType>
</amg:rights>
</item>
</channel>
</rss>
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:coverageRestrictionsthen 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