- From: Glenn Adams <glenn@skynav.com>
- Date: Fri, 25 Jan 2019 11:52:49 -0700
- To: Nigel Megitt <nigel.megitt@bbc.co.uk>
- Cc: Timed Text Working Group <public-tt@w3.org>
- Message-ID: <CACQ=j+c23xPio=YyoKZ1oKdZg0twhAyt7zRdM7LNGzvX8URUrA@mail.gmail.com>
Simple answer: use absolute URIs when you need to do so, e.g., <extensions xml:base="urn:my:namespace"> <extension restricts="http://www.w3.org/ns/ttml/feature/ #timeBase-media">#my-timebase-extension</extension> </extensions> On Fri, Jan 25, 2019 at 8:06 AM Nigel Megitt <nigel.megitt@bbc.co.uk> wrote: > All (but probably Glenn is best placed to answer this right now), > > I'm considering making a TTML2 processor profile that adds an extension > feature which imposes a restriction on #timeBase-media. This gives me a > syntactic headache concerning xml:base, which is not permitted on the > extension element but is permitted on its ancestor extensions element. > > How do I specify that the value of @restricts is relative to the TTML > namespace and the content of the extension element is relative to another > (local) namespace? > > If I specify: > > <extensions xml:base="urn:my:namespace"> > <extension > restricts="#timeBase-media">#my-timebase-extension</extension> > </extensions> > > it doesn't look right because it is not clear which namespace the > #timeBase-media feature is in, or it may be assumed incorrectly to be the > namespace specified by the parent element's @xml:base. > > kind regards, > > Nigel > > > > ---------------------------- > > http://www.bbc.co.uk > This e-mail (and any attachments) is confidential and may contain personal > views which are not the views of the BBC unless specifically stated. > If you have received it in error, please delete it from your system. > Do not use, copy or disclose the information in any way nor act in > reliance on it and notify the sender immediately. > Please note that the BBC monitors e-mails sent or received. > Further communication will signify your consent to this. > > --------------------- >
Received on Friday, 25 January 2019 18:53:29 UTC