 |
|
|
Jürgen Kahrs wrote:
> Me too. Attributes are definitely the right choice
> in this case (distinct parameter names, each occurring
> only once).
... with simple string values.
But those features mean the values *can* be attributes. It doesn't
necessarily mean attributes are better.
What would make me prefer attributes in this case is that those values
were inherent properties of the server description. In this case, they
aren't -- the network address is, but the database and user are really
attributes of the service or connection being made at that server. If
that's what you're trying describe, I'd be inclined to rename the server
element, or restructure it as an element which contains a <server> where
the latter describes only the server itself. (Probably just rename, but
that would depend on how this is actually being used.)
--
() ASCII Ribbon Campaign | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
