diff --git a/P5/Source/Guidelines/en/ND-NamesDates.xml b/P5/Source/Guidelines/en/ND-NamesDates.xml index 3a53dd3946..2c15edc7d7 100644 --- a/P5/Source/Guidelines/en/ND-NamesDates.xml +++ b/P5/Source/Guidelines/en/ND-NamesDates.xml @@ -754,7 +754,7 @@ target="#CONA"/>). The tag -->The granularity of events (and hence of their names) are up to the encoders.

eventName may be used in conjunction with well-defined (e.g. historical) events that are established in a particular - discipline, and which may have lead to authority file inclusion. There are two major applications of eventName: + discipline, and which may have led to authority file inclusion. There are two major applications of eventName: The element may be used for inline markup of mentioned named events such as in the above example; another typical use case are lists of named events. A sibling idno in @@ -823,7 +823,7 @@ target="#CONA"/>). The tag -->The the text, and encode it directly using the more specific elements described in this section.

Basic Principles -

Information about people, places, organizations, events, of whatever type, essentially comprises a series of statements or +

Information about people, places, organizations, and events, of whatever type, essentially comprises a series of statements or assertions relating to: characteristics or traits which do not, by and large, change over time characteristics or states which hold true only at a specific time @@ -1306,7 +1306,7 @@ exemplifying here too? --> may be recorded using the generic element event, which may be grouped with listEvent, and has a content model similar to that of state and trait. The chief difference is that event can include a placeName element to identify the name of the place where the event occurred.

-

Two particular events in a persons life, namely birth and death, are both ubiquitous and usually considered +

Two particular events in a person's life, namely birth and death, are both ubiquitous and usually considered particularly important, and thus may be represented by specialized elements for the purpose: @@ -2097,13 +2097,12 @@ occupation and residence.

However, many events are not named but the event element may still be used to provide a description of them, using head or label and desc to encode the available information.

-

The Guidelines do not prescribe what editors count as events, their granularity, nesting, and amount of other information to encode in - relation to an event. Yet, most events can be identified either by using temporal, spatial or information with regard to specific agents - involved (be it an org, person or object).

-

An event element may be used to record information about a place, a person or organisation related to the described event; for this reason the element - may appear as content of a place, person or org. However, it is also possible to describe events - independently of either a person, organization or a place. This may be useful not only for encoding texts which describe named events and - their eventNames, but also in applications as chronologies, lists of significant events such as battles, legislation, etc.

+

These guidelines do not prescribe what encoders count as events, nor their granularity, + nesting, or amount of other information to record in relation to each event. Yet, most events can be identified by their time, location, or agents involved (be they organizations, persons, or objects).

+

An event element may be used to record information about a place, person, or organization related to the described event; for this reason the element + may appear as content of a place, person, or org. However, it is also possible to describe events + independently of either a place, person, or organization. This may be useful not only for encoding texts which describe named events and + their eventNames, but also in applications as chronologies or lists of significant events (e.g., important battles, legislative milestones, or the stages of construction of a large building, etc.).

The listEvent element is a member of the model.listLike class, and may therefore @@ -2114,11 +2113,13 @@ occupation and residence.

- + - + France ceded to Great Britain its claims to the Hudson's Bay Company territories in Rupert's Land, Newfoundland, and Acadia and recognized British suzerainty over the Iroquois but retained its other pre-war @@ -2335,13 +2336,6 @@ occupation and residence.

For event as a child element of person, note the Section .

-

- - - - -

-
diff --git a/P5/Source/Specs/eventName.xml b/P5/Source/Specs/eventName.xml index fee3c33bdd..ec724ecbc4 100644 --- a/P5/Source/Specs/eventName.xml +++ b/P5/Source/Specs/eventName.xml @@ -1,4 +1,5 @@ -