| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: XML Nodelist Proposal |
>>
>> Which attributes should we have for node? Here are some thoughts. Should
s> any
>> of these be a child to node?
s> Are there any guidelines as to where attributes are used over children?
s> Of all the XML tutorials I never figured out where one was preferable
s> over the other.
I am hoping that Chris Cranford will pop up in here. He is supposed to be
VERY GOOD with XML. I think he could guide us on that. My first thought are
that if a child doesn't have any attributes then why not make it an
attribute of the "parent".
>> number=
s> Definately number, it identifies the node. It doesn't matter for the
s> rest, except for readability (IMO children are more readable than
s> attributes).
I agree with this.
What about something like flags, should their be children flags?
>> points should be a child to node, I believe. Points should have similar
>> if not the same attributes /children as a node.
s> Any reason for having points as under a
child,
s> instead of just ?
I thought for Readability and structure. Let me set some up as you suggest
and see how that works out.
With best regards, Dale Ross. E-mail: Dale.Ross{at}p1.f1.n379.z1.fidonet.org
--- Fidolook Lite FTN stub
* Origin: FidoHub Point 1 (1:379/1.1)SEEN-BY: 633/267 270 @PATH: 379/1 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.