Good enough , it seems like an obvious choice to save the extra verbosity of a subelement and create a 好极了，这似乎是一个明显的选择，省去额外冗长的子元素，并为
An important feature for every object that represents a subelement is the ability to serialize itself to xml 每一个表示子元素的对象的重要特性是将其本身序列化成xml的能力。
Personally , i find it much easier to read and write attribute - oriented xml formats than subelement - oriented ones 从个人角度来讲，我发现阅读和编写面向属性的xml格式要比面向子元素的容易得多。
As well as powerful type declaration , xml schemas improve upon the dtd s ability to declare the cardinality of subelement patterns 除了强大的类型声明以外， xml模式还在dtd声明子元素模式的基数性能力的基础上进行了改进。
In this tip , developerworks columnist david mertz advises when to use tag attributes and when to use subelement contents to represent data 在本文中， developerworks专栏作家david mertz就何时使用标记属性以及何时使用子元素内容来表示数据提出了一些建议。
Neither is horrible to read , but the attribute version in listing 2 is easier - and better still to write , because you do not need to worry about capricious subelement ordering 但清单1的属性版本要更容易阅读些而且也更易于编写，因为不必担心多变的子元素次序。
Subelement . these unwanted shell databases may interfere with subsequent tuning sessions and should be dropped before performing another test server production server tuning session 这些无用的shell数据库可能会妨碍后续的会话优化操作，因此，在执行其他测试服务器/生产服务器优化会话之前，应先删除这些shell数据库。
As a side matter , dtds do not make the specification of subelement cardinality easy you can compactly specify " one or more " of a subelement , but specifying " between seven and twelve " is , while possible , excessively verbose , or even outright contorted 还有一个次要问题，即dtd无法简化子元素基数性的规范（可以简洁地指定“一个或多个”子元素，但即使可能，指定“七到十二之间”也会过分冗长，甚至完全曲解） 。
An odd thing about xml is that it provides two almost , but not quite , equivalent ways of spelling " this is the data . " one way to indicate a data value is to put it inside a subelement ; another way is to put it in attribute values 关于xml的一件不同寻常的事情是，对于表示“这是数据” ，它提供了几乎相同但又不完全相同的两种方式。一种表示数据值的方式是，将数据值放入子元素中；另一种方式是将数据值放入属性值中。
