- From: Uche Ogbuji <uche@ogbuji.net>
- Date: Tue, 14 Aug 2012 08:37:51 -0600
- To: public-microxml@w3.org
- Message-ID: <CAPJCua2J0XgQ29=dzemMq1w=ReHir_i6RBoFiP23wp7_F3DsYw@mail.gmail.com>
On Tue, Aug 14, 2012 at 8:23 AM, Murray Maloney <murray@muzmo.com> wrote: > James, > > As a content creator, I tend to agree that it is easier to write <empty > foo="bar"/> than it is to write <empty foo="bar"></empty> > > More importantly, the empty element version reinforces the notion that > content is not allowed inside of this element. Thus it assists writers and > editors who may not be experts in markup languages. > But use of empty element syntax is not really saying that content is not *allowed* inside of the element, though I agree that, that probably happens to be the most common case. I wouldn't want use of an empty element to send a strong signal to another writer or editor on a document that they cannot expand the element to have content. Such a signal should strictly come from the schema layer. I do agree that empty element syntax is nice for authors, and it doesn't complicate the syntax much (one additional production). James has advocated that it have no role at all in the data model, so no complication there at this stage. -- Uche Ogbuji http://uche.ogbuji.net Founding Partner, Zepheira http://zepheira.com http://wearekin.org http://www.thenervousbreakdown.com/author/uogbuji/ http://copia.ogbuji.net http://www.linkedin.com/in/ucheogbuji http://twitter.com/uogbuji
Received on Tuesday, 14 August 2012 14:38:23 UTC