OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [dita] Those XML mention names

I have to agree with Dick: the letter of the XML spec is clear and I think
we have to adhere to it. At a minimum, not doing so would put the whole
DITA 1.3 schedule at serious risk since it would only take one reviewer to
make a stink for us to have to change.

It's certainly my fault for not having remembered (or noticed
subsequently) this constraint in the XML spec, but at least we noticed it
now while it's relatively easy to change.


Eliot Kimber, Owner
Contrext, LLC

On 8/19/14, 4:21 PM, "Richard Hamilton" <hamilton@xmlpress.net> wrote:

>Hi Tom,
>Interesting information from George, and a reasonable interpretation.
>I would argue against using xml in these names. While the risk may be
>low, the consequences would be pretty bad if W3C decided to use one of
>those names. I would also argue that "reserved" is for all practical
>purposes "invalid" for anyone except W3C.
>Best regards,
>XML Press
>XML for Technical Communicators
>On Aug 19, 2014, at 2:04 PM, Tom Magliery <tom.magliery@justsystems.com>
>> I mentioned to George Bina our discovery about the element names in the
>>XML-mention domain. Mostly I was just expressing my surprise that no one
>>of us had noticed before, presumably because no tools flagged those
>>element names as being any kind of problem in a DTD. I confirmed for
>>myself (both in and outside of DITA) that XMetaL certainly doesn't, and
>>George confirmed that oXygen doesn't either. He thought that some
>>earlier versions of Xerces might have given warnings.
>> He raised a good point about why this is correct behaviour for the
>>tools: The spec doesn't say that these names are invalid, just that
>>they're reserved for future W3C use. If W3C were to use such names in a
>>DTD someday, we wouldn't want our tools rejecting their DTDs.
>> He also suggested (and I agree) that our decision to use/not use these
>>names is therefore a risk/benefit analysis: What is the risk, should we
>>decide to use the names "xmlelement", "xmlatt", etc., that W3C would
>>come along one day and declare that the names are going to serve some
>>official, other purpose?
>> Maybe we should weigh that against the aesthetics of these names
>>compared with the "xm-" versions, before we make our final decision.
>> mag
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  Follow this link to all your TCs in OASIS at:

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]