Representation:
<calendricSystem name = "american">
<importCalendar name = "Gregorian"
url =
"*.xml" /> <!-- url is of instant input format (it may be other than InstantInputFormat of default Properties) --> <!-- name should be equal to one of the above -->
<calendricSystemEpoch name = "Gregorian" url = "*.xml"
/>
<start calendarName =
"none" >
<!-- url is of default properties -->
<fieldValueFunctions>
</fieldValueFunctions> <!-- The anchor will be zero if it is not explicitly specified. Each calendar should have its underlying granularity mapped in terms of other known granularity except the first imported calendar, which contains the base line granularity, in our case Gregorian and Gregorian.second.--> <!-- See the design decision on representation of Regular Mappings in a Calendric Spec.. -->
<regularGranularityMappings>
<!-- Below is just a imaginary, irregular mapping example purposed, assume we have Timecard cal.-->
<!-- See another
way of representing an irregular mapping in Calendric Spec.. -->
<irregularGranularityMappings> <function name = "astroCastYearToDay" /> <function name = "astroCastDayToYear" />
</mapping>
from FVT -->
<defaults plausability = "50" maxNumberOfGranularity = "15" token = "[^\s]+"/> |
When analyzing examples, note that some of the structure is changed. I left the above representation untouched to see the differences.
See an example of american Calendric System.
See also a discussion on improving descriptiveness of this specification file.