Re: Survey ID vs Survey Trip data storage

From: Richard Knapp (gyp_caver@yahoo.com)
Date: Tue Apr 03 2001 - 17:51:06 CEST


><Surveys>
> <Survey>
> <Date value="04/02/2001">
> <Designation value="E">
> <Data>
> </Data>
> </Designation>
> <Designation value="EA">
> <Data>
> </Data>
> </Designation>
> </Date>
> </Survey>
> <Designation value="A">
> <Date value="01/01/2001">
> <Data>
> </Data>
> </Date>
> <Date value="02/01/2001">
> <Data>
> </Data>
> </Date>
> </Designation>
> <Designation value="B">
> <Date value="01/02/2001"/>
> <Data>
> </Data>
> </Designation>
> </Survey>
></Surveys>

What I got so far is this. I am replacing this element:

<!ELEMENT Survey (Name, Header, Data, Comment*)>

with this structure. (The Header Entity is a replacement of the Header Element. The extra Depth was unnecessary)

<!ENTITY % SurveyHeader "(Name | Declination | Personnel | Equipment | OrderFormat | Comment | BookFormat |
TapeMethod | BackSightMethod | Exclusions | WallFormat*)">

<!ELEMENT Survey (Date | Designation)>
<!ELEMENT Date (%SurveyHeader;, (Designation | Data))+>
<!ELEMENT Designation (Date | Data)+>
<!ATTLIST Designation
            SID ID #IMPLIED
            Value CDATA #IMPLIED>

It does allow unlimited nesting (which may or may not be a problem) but it appears pretty flexible.

        - Richard Knapp

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com



This archive was generated by hypermail 2b30 : Wed May 02 2001 - 12:00:00 CEST