View Single Post
  #14   Spotlight this post!  
Unread 31-12-2002, 00:18
jonathan lall's Avatar
jonathan lall jonathan lall is offline
Registered User
FRC #2505 (The Electric Sheep; FRC #0188 alumnus)
Team Role: Mentor
 
Join Date: Jan 2002
Rookie Year: 2001
Location: Toronto, Canada
Posts: 547
jonathan lall has a reputation beyond reputejonathan lall has a reputation beyond reputejonathan lall has a reputation beyond reputejonathan lall has a reputation beyond reputejonathan lall has a reputation beyond reputejonathan lall has a reputation beyond reputejonathan lall has a reputation beyond reputejonathan lall has a reputation beyond reputejonathan lall has a reputation beyond reputejonathan lall has a reputation beyond reputejonathan lall has a reputation beyond repute
Send a message via MSN to jonathan lall
Here's what I mean. This is an example of how a simple XML-based scouting sheet could look:

Code:
<?xml version="1.0" encoding="utf-8"?>
<scoutinfo>
	<team number="188" name="Woburn Robotics"></team>
	<robot name="Blizzard 3" type="goalbot"></robot>
	<goals number="2">excellent</goals>
	<balls number="0">N/A</balls>
	<traction>excellent</traction>
	<speed>good</speed>
	<motorpower number="6">excellent</motorpower>
	<gearbox type="one-speed"></gearbox>
	<gohome boolean="true">poor</gohome>
	<comments rating="8">
That's one nice robot. Fairly fast, really powerful, won't let go of goals involuntarily.
	</comments>
</scoutinfo>
All elements here are concrete values, whereas the attributes are more subjective. Since it's extensible, missing info shouldn't be a problem. There are a few ways we could do its DTD. All the attribute names are type, name, boolean, and number.
__________________