MCE Revision Issue: §10.6, "Justification of Ignorable Foreign Children of AlternateContent"
Francis Cave
francis at franciscave.com
Tue Aug 13 15:50:58 CEST 2013
Re-write following WG 4 discussion during teleconference on 2013-08-13. The
addition of the first sentence from the original text makes it necessary to
remove the later sentence that says the same thing. Ive also done some
word-smithing to correct the spelling of AlternateContent and to avoid use
of the term extension element, which has a special meaning.
Ignorable elements are allowed as child elements of AlternateContent to
allow for future extensions to this construct. If AlternateContent were
specified to contain only Choice and Fallback elements from the Markup
Compatibility namespace (see §8.5), this would prevent the use of other
Markup Compatibility elements that would allow extension of AlternateContent
in future versions of MCE. Any MCE processor that encounters a child element
of AlternateContent that is in the namespace of an intended future extension
of MCE will not fail to process the document, provided the namespace of this
child element is ignorable, because it will discard all elements in
ignorable namespaces that are not understood before making a selection
between the remaining Choice and Fallback elements.
Francis
From: Francis Cave [mailto:francis at franciscave.com]
Sent: 23 July 2013 00:42
To: 'SC 34 WG4'
Subject: RE: MCE Revision Issue: §10.6, "Justification of Ignorable Foreign
Children of AlternateContent"
I would suggest the following text for this paragraph:
The way that AlternativeContent is specified to contain only Choice and
Fallback elements from the Markup Compatibility namespace (see §8.5)
prevents the use of other Markup Compatibility elements that would otherwise
allow extension of AlternativeContent in future versions of MCE. For this
reason the specification of AlternativeContent allows elements from
Ignorable namespaces as children of AlternativeContent. Any MCE processor
that encounters a child element of AlternativeContent that is in the
namespace of an intended future extension of MCE will not fail to process
the document, provided the namespace of the extension element is ignorable,
because it will discard all elements in ignorable namespaces that are not
understood before making a selection between the remaining Choice and
Fallback elements.
I think that a re-write along these lines is clearer than attempting to
revise the existing paragraph word-by-word.
Francis
From: Rex Jaeschke [mailto:rex at RexJaeschke.com]
Sent: 22 July 2013 18:47
To: SC 34 WG4
Subject: MCE Revision Issue: §10.6, "Justification of Ignorable Foreign
Children of AlternateContent"
A few days ago, I posted to this email list, WG N 0264, 29500-3 (MCE)
Revision, WD0.91. It contains proposed changes by John H. based on an
action item he took at the Bellevue F2F meeting. This action item was:
Needs wordsmithing this was an e-mail John sent during the London 2012
meeting to capture some discussion.
Please post your feedback to this list. If we get enough support, well
close this issue on the next teleconference; otherwise, well deal with it
at the Delft F2F meeting.
Rex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20130813/1fa24382/attachment.html>
More information about the sc34wg4
mailing list