Next / Previous / Contents / Shipman's homepage

5.3. The day-notes element

Each day-notes element represents one day's effort within a single state. If multiple states are covered in a single day, each day's notes must be segregated into a separate day-notes element.

birdnotes.rnc
day-notes = element day-notes
{   attribute state {state-pattern},  1
    attribute date {date-pattern},    2
    attribute day-loc { xsd:Name }?,  3
    day-summary,                      4  
    form*                             5
}
state-pattern = xsd:string{pattern="[a-z]{2,3}"}
date-pattern = xsd:string{pattern="[0-9]{4}-[0-9]{2}-[0-9]{2}"}
1

Defines the state or other region where its sightings occurred. The state and date attributes are required. The state code is case-insensitive, so it isn't necessary to capitalize it. Example:

    state='nm'

2

This attribute specifies the date of the fieldwork. It must have the format yyyy-mm-dd, although unlike the xsd:date datatype, we allow the month or day to be '00'. This necessary because of vague dates like '1974-11-00' (sometime in November 1974) and '1989-00-00' (sometime in 1989). Example:

    date='2004-09-05'

3

The optional day-loc attribute specifies a location code that describes a geographic area containing the entire day's efforts. The name related to this location code will be used as the brief title associated with that day's notes. If given, this attribute's location code must be defined by a loc element (described below).

If no day-loc attribute is supplied, the default location code will be the one given in the default-loc attribute of the day-summary element. See the discussion of the default-loc attribute under day-summary.

4

The content of a day-notes element must start with exactly one day-summary element; see Section 5.4, “The day-summary element: information about the field day”.

5

The rest of the content consists of zero or more form children, one for each kind of bird seen. See Section 5.8, “ The form element: records for one kind of bird ”.