|The Library of Congress » Standards » MODS Official Web Site|
|HOME >> MODS 3.6 Changes
Approved <hierarchicalGeographic> Proposal in MODS 3.6
November 20, 2014 -- MODS HierarchicalGeographic Proposal -- Approved
1.1 State and Province
<province> will be deprecated; <state> will be re-defined:
<state> includes first order political jurisdictions under countries, such as states, provinces, cantons, Länder, etc. regardless of what they are called in the particular country.
See Commentary and Examples: 1.
1.2 New Attributes to Indicate Place Types
Attributes @areaType, @regionType, and @sectionType will be defined for elements <area>, <region>, and <citySection> respectively. These would of course be optional.
See Commentary and Examples: 2.
1.3 Indication of hierarchical level
Attribute @level will be defined for all place type elements to indicate hierarchical level. It would of course be optional.
The authority attributeGroup (authority, authorityURI, and valueURI) will be added to all place type elements.
1.5 Places that no longer exist
Attribute @period will be defined. Its presence will indicate that the described entity once existed but no longer exists. Its value would be a hint of when it existed (it could simply be a date).
See Commentary and Examples: 4.
Commentary and Examples
<state> – Includes first order political divisions called states within a country, e.g. in U.S., Argentina, Italy. Use also for France département.
<province> – Includes first order political divisions called provinces within a country, e.g. in Canada.
So first order political divisions mostly go under <state> unless they're called <province>. And we're silent on what they call them in other countries.
The committee thinks it desirable to put all first order political divisions under one element. The term "first order political division" or "first order political jurisdiction" is rather unwieldy. So the proposal is to deprecate province and define <state> as all first order political jurisdictions.
<citySection> for example is currently defined as:
<citySection>-- Name of a smaller unit within a populated place, e.g., neighborhoods, parks, or streets
Thus, citySection is a broad term that can be used without the @sectionType attribute, but if you want to designate a specific type of city section you could say
<citySection sectionType="neighborhood" >
for formally established neighborhoods, or
Note that the use of "city" here doesn't preclude towns.
<area> could take an @areaType attribute to accommodate some of those areas that have been suggested-- national parks, rivers, Indian reservation, etc.
There is no need for @level for simple cases like the following where the hierarchy is easily inferred:
But there are a few cases where @level would be useful:
To elaborate of the latter two points:
Consider the following example, where Blackstone is a sub-neighborhood of East Side, in Providence.
<citySection citySectiontype="neighborhood" level="1">East Side</ citySection >
< citySection citySectiontype="neighborhood" level="2">Blackstone</ citySection >
Another example, consider Massachusetts Avenue which runs through Lincoln Park within Capitol Hill in Washington DC. Say you want to identify that section of Mass Ave within the park:
<state>District of Columbia</state>
<citySection citySectionType ="neighborhood" level="1">Capitol Hill</ citySection>
< citySection citySectionType =”park” level="2">Lincoln Park</ citySection>
<citySection citySectionType =”street” level="2">Massachusetts Avenue</citySection>
Whenever the level is the same for two places the intersection is indicated. This example indicates the intersection of the two level 5 entities.
<area level="3"type="trail" period="gold rush">Oregon Trail</area>
<country period=”1945-1990”>East Germany</country>
|HOME >> Changes for MODS Version 3.6
Questions and comments: