[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xsl-list
Subject:    Re: [xsl] How to retain the end tag when outputting an empty element?
From:       "Peter Flynn peter () silmaril ! ie" <xsl-list-service () lists ! mulberrytech ! com>
Date:       2022-06-19 14:13:33
Message-ID: 20220619101301.7bd095de () lists ! mulberrytech ! com
[Download RAW message or body]

On 19/06/2022 11:31, Andrew Sales andrew@andrewsales.com wrote:
>     But several people felt that
>     <test/> meant "this element type is declared as EMPTY, so it can never
>     have an end-tag"
>     whereas
>     <test></test> meant "this element is declared with potential content of
>     some kind, but for whatever reason on this occasion it has none".
> 
> 
> As an aside here, I wonder if this preference has been influenced at all 
> by the sentence from the Recommendation: "For interoperability [with 
> SGML processors], the empty-element tag should be used, and should only 
> be used, for elements which are declared EMPTY." [1]

It may have been the other way round :-) it's rather a long time ago and 
my brain has only limited reach.

P
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/651070
or by email: xsl-list-unsub@lists.mulberrytech.com
--~--

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic