RE: [t13] Command Format

[Tony Goodfellow]

Title: Command Format

For what it is worth – here are my comments.   a)       Command Code – It would be a pain to have to flip back to a table – and for those of use who read these things electronically it is a good search key. b)       Protocol – It is again useful information. It needs two references, PATA,SATA. c)       Prerequisites – Again it needs two sub sections – PATA and SATA d)       Description- I have always complained that putting the description at the end of the definition is a very inconvenient place. To my mind it should be at the beginning after the Command Code. If the description is different for P{ATA and SATA then two descriptions should be given.   Tony Goodfellow -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Stevens Sent: Monday, 09 August, 2004 15:06 To: ATA (E-mail) Subject: [t13] Command Format   This following document has been posted: http://www.t13.org/docs2004/e04139r0-Command_Format_Example.pdf  This contains some sample command proposals for the new command set standard.  There are also several questions about what kind of information needs to reside in this doc.  Please take a look and forward me your commands.  It would be good if I could get a second rev up prior to the meeting. ------------------------------------------------ Curtis E. Stevens 20511 Lake Forest Dr.  #C 214-D Lake Forest, Ca. 92630   Phone: 949-672-7933 Cell: 949-307-5050 E-Mail: [EMAIL PROTECTED]