Closed mhyv closed 1 year ago
const perms = `
<profilelist>
<ui_profile name="OITF_HD_UIPROF+META_BCG+TRICKMODE">
<ext>
<clientMetadata type="bcg">true</clientMetadata>
</ext>
</ui_profile>
</profilelist>`;
const caps: any = document.getElementById('oipf-capabilities');
const xml = new DOMParser();
const doc = xml.parseFromString(perms, 'text/xml');
caps.innerHTML = doc.documentElement;
This is how I am currently attempting to inject the XML permissions, but this doesn't seem to be doing much since the default profile list is still being used.
If you dump oipfCapabilities.xmlCapabilities
xml object can you see appropriate attributes supported by the device?
Did you study application/oipfConfiguration”
OIPF object wrapper?
The Configuration object allows configuration items within the system to be read and modified. This includes
settings such as audio and subtitle languages, display aspect ratios and other similar settings
Hi @Murmur. Yes, I can see the attributes supported when dumping oipfCapabilities.xmlCapabilities
, but I need additional capabilities to access certain additional metadata fields (such as the Genre of a given channel) but the permissions for this are currently missing from oipfCapabilities.xmlCapabilities
.
I believe I need to add <contentMetadata type="bcg">true</contentMetadata>
, but can't find the correct api for this, does this exist/is this accessible to developers?
Had a look at application/oipfConfiguration
but this doesn't seem to meet my requirements.
Hello @mhyv, this question is better suited to HbbTV Developer portal, and its Stack Overflow community
Hi,
I am trying to configure an OIPF application using the HBBTV spec.
I am currently trying to grant the application permission to access additional metadata for the current Channel.
I have read the spec here https://www.etsi.org/deliver/etsi_ts/102700_102799/102796/01.04.01_60/ts_102796v010401p.pdf
Which says that the oipfCapabilities embedded object has to have an XML document with some additional configuration to specify contentMetadata and extendedAVControl permissions.
My question is, at what point do I need to inject these permissions and how? The xmlCapabilites property on the oipfCapabilities object is read only, and it’s not entirely clear from the documentation where you specify or how you specify custom permissions.
Looking forward to your response.