>>> - source file name (CaveXML data file).
>Source location. Remember that it may be in the same file, on the same
>computer, or not. I think that is what XPointer is for. I haven't ....
I intentionally left out location. Files may move but their name rarely changes. If I copy the files to a floppy or Zip disk so I
can take them with me, I don't want to have to break the link to my PC's directory structure just so I can view the data.
>A sequence of located stations separated by shots defines a polyline if the
>program reading the file cares. Any Station in a list like this that is NOT preceded
>by a Shot element starts a new polyline.
Both ways work the same; one just looks different than the other.
>For a start, so far as I know there are no (or worse many) standard ways to name colors or line thicknesses. What color
exactly is "Blue"? Line thickness is 1 what? Pixels? Meters? This is quite a bit trickier than units for cave measuements;
there is no universal conversion factor from pixels to meters.
These were included as an example but your point is valid. And it does belong in the view. It might be tied - at least at first -
to the survey ID or ? Something else to specify in the heading of the file: ColorMethod. Could be as defined, by survey, by
depth, or ?
>if not physically) all the display information from stuff that describes
>the actual cave.
Agreed.
>Personally I think display options are going to be hard to define in a
>platform (or even program) independant way. So hard in fact that I don't ...
I think just having a View format will address the issue sufficiently that it can be left for later discussion.
- Richard Knapp
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
This archive was generated by hypermail 2b30 : Fri Jun 01 2001 - 12:00:00 CEST