Some fields input.

[Mark Shephard]

This email is primarily for Mark Miller and Carl who are charged with 
the task of starting a iFeilds document.

Since many of the requirements discussed at the bootcamp this week are 
the same as what the RPI team was using in 04 when we started the 
attached document, I thought Mark and Carl could benefit by seeing some 
of the things we were attempting to do. Although we often used different 
terms this week, one will see this document attempts a structure for 
fields that deals with many (not all) of the requirements we discussed 
for at least mesh level representations of fields. There is no claim 
that this structure is ideal of the one we should adopt.

The .fm file is for Mark Miller since he is one of the other 5 or so 
remaining Framemaker users left.

Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fields-v08.pdf
Type: application/pdf
Size: 160579 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/tstt-interface/attachments/20091017/261e8189/attachment-0001.pdf>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: fields-v08.txt
URL: <http://lists.mcs.anl.gov/pipermail/tstt-interface/attachments/20091017/261e8189/attachment-0001.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fields-v08.doc
Type: application/msword
Size: 123392 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/tstt-interface/attachments/20091017/261e8189/attachment-0001.doc>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fields-v08.fm
Type: application/octet-stream
Size: 111616 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/tstt-interface/attachments/20091017/261e8189/attachment-0001.obj>