A place name may contain text with no indication of its internal structure: Rochester, NY More usually however, a place name of this kind will be further analysed in terms of its constitutive geo-political or administrative units. These may be arranged in ascending sequence according to their size or administrative importance, for example: Rochester, New York, or as a single such unit, for example Belgium. These Guidelines provide a hierarchy of generic element names, each of which may be more exactly specified by means of a type attribute:

These elements are all members of the model.placeNamePart class, members of which may be used anywhere that text is permitted, including within each other as in the following examples: Rochester, New York Laos, Southeast Asia 6ème Paris, France

Places may also be named in terms of geographic features such as mountains, lakes, or rivers, independently of geo-political units. The geogName is provided to mark up such names, as an alternative to the placeName element discussed above. For example: Mississippi River

In addition to the usual phrase level elements, the geogName element may contain the following specialized element:

Where the geogFeat element is used to characterize the kind of geographic feature being named, the name element will generally also be used to mark the associated proper noun or noun phrase: Mississippi River A more complex example, showing a variety of practices, follows: The isolated ridge separates two great corridors which run from Glencoe into Glen Etive , the Lairig Gartain and the Lairig Eilde

The Gaelic word lairig may be glossed as sloping hill face. The most efficient way of including this information in the above encoding would be to create a separate nym element for this component of the name and then point to it using the nymRef attribute, as further discussed in .

All the place name specifications so far discussed are absolute, in the sense that they define only one place. A place may however be specified in terms of its relationship to another place, for example 10 miles northeast of Paris or near the top of Mount Sinai. These relative place names will contain a place name which acts as a referent (e.g. Paris and Mount Sinai). They will also contain a word or phrase indicating the position of the place being named in relation to the referent (e.g. the top of, north of). A distance, possibly only vaguely specified, between the referent place and the place being indicated may also be present (e.g. 10 miles, near).

Relative place names may be encoded using the following elements in combination with either a placeName or a geogName element. Some examples of relative place names are: near the top of Mount Sinai 20 km north of Paris If desired, the distance specified may be normalized using the unit and quantity attributes of measure: 11 miles Northwest of Providence, RI

The internal structure of place names is like that of personal names—complex and subject to an enormous amount of variation across time and different cultures. The recommendations in this section should however be adequate for a majority of users and applications; they may be extended using the mechanisms described in chapter to add new elements to the existing classes. When the focus of interest is on the name components themselves, as in place name studies for example, the elements discussed in may also be of use. Alternatively, the meaning structure itself may be represented using feature structures ().

The model.persStateLike class contains elements describing physical or socially-constructed characteristics, traits, or states of a person. Members of the class comprise the following specific elements: All, apart from langKnowledge, allow content of ordinary prose containing phrase-level elements. Status AB1 in the RG Classification scheme

The meanings of concepts such as sex, nationality, or age are highly culturally-dependent, and the encoder should take particular care to be explicit about any assumptions underlying their usage of them. For example, when recording personal age in different cultures, there may be different assumptions about the point from which age is reckoned. A statement of the practice adopted in a given encoding may usefully be provided in the editorialDecl element discussed in .

The langKnowledge element contains either paragraphs or a number of langKnown elements; it may take a tags attribute, which provides one or more standard codes or tags for the languages. The langKnown element must have a tag attribute, which indicates the language with the same kind of language tag. These language tags are discussed in detail in .

Furthermore, the langKnown element also has a level attribute to indicate the level of the person's competence in the language. It is thus possible either to say:

Speaks fluent Fulani, Wolof, and French. Some knowledge of English.

The sex element carries a value attribute to give values from a project-internal taxonomy, or an external standard, such as vCard's sex property (in which M indicates male, F indicates female, O indicates other, N indicates none or not applicable, U indicates unknown) or the often used ISO 5218:2004 (in which 0 indicates unknown; 1 indicates male; 2 indicates female; and 9 indicates not applicable, although the ISO standard is widely considered inadequate). female As elsewhere, these coded values may be used as an alternative to or normalization of the actual descriptive text contained in the element. The previous example might equally well be given as

The generic trait and state elements are also a member of this class, These element can be used to extend the range of information supplied about an individual's personal characteristics. Either may contain an optional label element, used to provide a human-readable specification for the characteristic concerned and a description of the feature itself supplied within a desc element. These may be followed by or one or more p elements supplying more detailed information about the trait. In either case, these may be followed by one or more notes or bibliographical references. The type, ref, and key attributes may be used to indicate a fuller definition of the combination of feature and value. Ethnicity Ethnic Albanian.

These elements are provided as a simple means of extending the set of descriptive features available in a standardized way. For example, there are no predefined elements for such features as eye or hair colour. If these are to be recorded, they may simply be added as new types of trait: eye colour blue hair colour brown

If none of the more specialized elements listed above is appropriate, then a choice must be made between the two generic elements trait and state. If you wish to distinguish between characteristics that are generally perceived to be transient and those which are generally considered unchanging, use state for the former, and trait for the latter. It may also be helpful to note that traits are typically, but not necessarily, independent of the volition or action of the holder. If the distinction between state and trait is not considered relevant or useful, use state.

The persName element is repeatable and can, like all TEI elements, take the attribute xml:lang to indicate the language of the content of the element, as well as a type attribute to indicate the type of name, whether a nickname, maiden or birth name, alternative form, etc. This is useful in cases where, for example, a person is known by a Latin name and also by any number of vernacular names, many or all of which may have claims to authenticity. In order to ensure uniformity, the method generally employed in the library world has been to accept the form found in some authority file, for example that of the American Library of Congress, as the base or neutral form. Feelings can run high on this matter, however, and people are often reluctant to accept as neutral an overtly foreign form of the name of their local saint or hero. Within the person element any number of variant forms of a name can be given, with no prioritization, and hence less likelihood of offence. The Icelandic scholar and manuscript collector Árni Magnússon, to give his name in standard modern Icelandic spelling, is known in Danish as Arne Magnusson, the form which he himself, as a long term resident of Denmark, generally used; there is also a Latinized form, Arnas Magnæus, which he used in his scholarly writings. All three forms can be given, and in any order: Árni Magnússon Arne Magnusson Arnas Magnæus

At the other extreme, a person may be named periphrastically as in the following example: Simon, son of Richard Essex 1219-1223

Alternatively, the generic name element may be used for all of the naming components in a description. For example, a description of the first living held by the Icelandic clergyman and poet Jón Oddsson Hjaltalín might be tagged as follows:

Jón's first living — which he apparently accepted rather reluctantly — was at Háls í Hamarsfirði, Múlasýsla, to which he was presented on 7 April 1777. He was ordained the following month and spent three years at Háls, but was never happy there, due largely to the general penury in which he was forced to live — a recurrent theme throughout the early part of his life. In June of 1780 the bishop recommended that Jón should promoveres til andet bedre kald, end det hand hidindtil har havt, and on 12 July it was agreed that he should exchange livings with sr. Þórður Jónsson at Kálfafell á Síðu, Skaftafellssýsla.

Similarly, the generic state or trait element may be used in preference to the more specific elements listed above: Nationality American citizen from 15 January 2002. is the same as: American citizen from 15 January 2002. or even:

Events in a person's history are not characteristics of an individual, but often cause an individual to gain such characteristics, or to enter a new state. Most such events, for example marriage, appointment, promotion, or a journey 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 particularly important, and thus may be represented by specialized elements for the purpose:

In the following example, we give a brief summary of the wedding of Jane Burden to the English writer, designer, and socialist William Morris, encoded as an event element embedded within the person element used to record data about Morris, though we could equally well have embedded the event within the person element for Burden, or have given it as a freestanding event independent of either person element: Marriage William Morris and Jane Burden were married at St Michael's Church, Ship Street, Oxford on 26 April 1859. The wedding was conducted by Morris's friend R. W. Dixon with Charles Faulkner as the best man. The bride was given away by her father, Robert Burden. According to the account that Burne-Jones gave Mackail M. said to Dixon beforehand Mind you don't call her Mary but he did. The entry in the Register reads: William Morris, 25, Bachelor Gentleman, 13 George Street, son of William Morris decd. Gentleman. Jane Burden, minor, spinster, 65 Holywell Street, d. of Robert Burden, Groom. The witnesses were Jane's parents and Faulkner. None of Morris's family attended the ceremony. Morris presented Jane with a plain gold ring bearing the London hallmark for 1858. She gave her husband a double-handled antique silver cup. J. W. Mackail, , 1899. Robert Burden R.W. Dixon Charles Faulkner Edward Burne-Jones J.W. Mackail In this example the ref attributes on the various name elements point either to an external source or to a person element within which other information about the person named may be found. As further discussed below (), a relation element may then be used to link them in a more meaningful way:

As mentioned above, all these elements, both the specific and the generic, are members of the att.datable attribute class, which means they can be limited in terms of time. The following encoding, for example, demonstrates that the person named David Jones changed his name in 1966 to David Bowie: David Jones David Bowie

All the generic elements are also members of the att.global.responsibility and att.editLike classes. These classes make available the attributes cert, to indicate the degree of certainty, resp, the agency responsible, evidence, the nature of the evidence used, and source, a pointer to a resource from which the information derives. In this way it is possible, in the case of multiple and conflicting sources, to provide more than one view of what happened, as in the following example:

Born in Brixton on 8 January 1947.

When the module defined by this chapter is included in a schema, the following two elements may be used to document relationships amongst the persons, places, or organizations identified: These elements are both members of the att.typed class, from which they inherit the type and subtype attributes in the usual way. The value specified for either attribute on a listRelation element is implicitly applicable to all of its child relation elements, unless overridden.

A relationship, as defined here, may be any kind of describable link between specified participants. A participant (in this sense) might be a person, a place, or an organization. In the case of persons, therefore, a relationship might be a social relationship (such as employer/employee), a personal relationship (such as sibling, spouse, etc.) or something less precise such as possessing shared knowledge. A relationship may be mutual, in that all the participants engage in it on an equal footing (for example the sibling relationship); or it may not be if participants are not identical with respect to their role in the relationship (for example, the employer relationship). For non-mutual relationships, only two kinds of role are currently supported; they are named active and passive. These names are chosen to reflect the fact that non-mutual relations are directed, in the sense that they are most readily described by a transitive verb, or a verb phrase of the form is X of or is X to. The subject of the verb is classed as active; the direct object of the verb, or the object of the concluding preposition, as passive. Thus parents are active and children passive in the relationship parent (interpreted as is parent of); the employer is active, the employee passive, in the relationship employs. These relationships can be inverted: parents are passive and children active in the relationship is child of; similarly works for inverts the active and passive roles of employs.

For example: This example defines the relationships amongst a number of people not further described here; we assume however that each person has been allocated an identifier such as P1, P2, etc. which can be linked to using references such as #P1, #P2, etc. Then the above set of relation elements describe the following three relationships amongst the people referenced: P1 and P2 are parents of P3 and P4. P1 and P2 are linked in a mutual relationship called spouse—that is, P2 is the spouse of P1, and P1 is the spouse of P2. P1 has the social relationship employer with respect to P3 and P4.

Relationships within places and organizations are further discussed in the relevant sections below. Relationships between for example organizations and places, or places and persons, may be handled in exactly the same way.

A location may be specified in one or more of the following ways: by supplying a string representing its coordinates in some standardized way within a geo element, as shown below by supplying one or more place name component elements (e.g. country, settlement etc.) to place it within a geo-political context by supplying a postal address, e.g. using the address element by supplying a brief textual description, e.g. using the desc element by using a non-TEI XML vocabulary such as the Geography Markup Language We give examples of all of these methods in the remainder of this section.

The simplest method of specifying a location is by means of its geographic coordinates, supplied within the geo element. This may be used to supply any kind of positional information, using one of the many different geodetic systems available. Such systems vary in their format, in their scope or coverage, and more fundamentally in the reference frame (the datum) used for the coordinate system itself. The default recommended by these Guidelines is to supply a string containing two real numbers separated by whitespace, of which the first indicates latitude and the second longitude according to the 1984 World Geodetic System (WGS84); this is the system currently used by most GPS applications which TEI users are likely to encounter.See . The most recent revision of this standard is known as the Earth Gravity Model 1996.We might therefore record the information about the place known as Lyon as follows: Lyon Lugdunum 45.769559 4.834843

Identifying Lyon by its geo-political status as a settlement within a country forming part of a larger political entity, we might represent the same place as follows: Lyon Lugdunum EU France Elements such as bloc are specialized forms of placeName, as discussed in .

We may use the same procedure to represent the location of smaller places, such as a street or even an individual building: Brasserie Georges Lyon IIème Perrache Cours de Verdun Note the use of the type attribute to categorize more precisely both the kind of place concerned (a building) and the kind of name used to locate it, for example by characterizing the generic district as an arrondissement, or a quartier.

We may also treat imaginary places in the same way: Atlantis beyond The Pillars of Hercules

A location sometimes resembles a set of instructions for finding a place, rather than a name: Yasgur's Farm Woodstock Festival Site one mile north west of Bethel New York

The element address may also be used to identify a location in terms of its postal or other address: Protestant Cemetery Cimitero Acattolico Italy Rome Testaccio

The location element may thus identify a place to a greater or lesser degree of precision, using a variety of means: a name, a set of names, or a set of coordinates. The geo element introduced earlier is by default understood to supply a value expressed in a specific (and widely used) notation. If a location contains more than one geo, this is interpreted as being really the same place in the universe, but with different systems used to refer to it. If there is a lack of consensus about the location (of, for example, Camelot), more than one location should be used, each with its own geo.

By default, the content of geo is interpreted as following the standard known as the World Geodetic System (WGS). This may be modified, however, in two ways.

Firstly, the content of the geo element can be expressed some other way, that is, according to some different geodetic system. The decls attribute is used point to a geoDecl element defined in the document header, which describes a different datum.

Secondly, the element geo may be redefined to contain markup from a different XML vocabulary which is specifically designed to represent this kind of information. This technique is used throughout the Guidelines where specialized markup is required, for example to embed mathematical expressions or vector graphics, and is further described and exemplified in . For geographic information, suitable non-TEI vocabularies include: the OpenGIS Geography Markup Language (GML) being defined by the OGCThe OGC is an international voluntary consensus standards organization whose members maintain the Geography Markup Language standard. The OGC coordinates with the ISO TC 211 standards organization to maintain consistency between OGC and ISO standards work. GML is also an ISO standard (ISO 19136:2007). the Keyhole Markup Language (KML) used by Google MapsSee

In the following example, we have defined the location of the place Lyon using GML and indicated the two names associated with it at different times: Lyon Lugdunum 45.256 -110.45 46.46 -109.48 43.84 -109.86 45.8 -109.2 45.256 -110.45

A bibl element may be used within location to indicate the source of the location information.

A place may contain other places. This containment relation can be directly modelled in XML: thus we can say that the towns of Vilnius and Kaunas are both in a place called Lithuania (or Lietuva) as follows: Lithuania Lietuva Vilnius Kaunas

This does not, of course, imply that Vilnius and Kaunas are the only places constituting Lithuania; only that they are within it. A separate place element may indicate that it is a part of Lithuania by supplying a relation element, as discussed below ().

As a further example, the islands of Mauritius, Réunion, and Rodrigues are collectively known as the Mascarene Islands. Grouped together with Mauritius there are also several smaller offshore islands, with rather picturesque French names. These offshore islands do not however constitute an identifiable place as a whole. One way of representing this is as follows: Mascarene Islands Mascarenhas Archipelago Mauritius La roche qui pleure Île aux cerfs Rodrigues Réunion

Here is a more complex example, showing the variety of names associated at different times and in different languages with a set of hierarchically grouped places—the settlement of Carmarthen Castle, within the town of Carmarthen, within the administrative county of Carmarthenshire, Wales. Cymru Wales Wallie Wallia Le Waleis Carmarthenshire Carmarthen Kaermerdin Caerfyrddin castle of Carmarthen

As noted previously, country, region, and settlement are all specializations of the generic placeName element; they are not specializations of the place element. If it is desired to distinguish amongst kinds of place this can only be done by means of the type attribute as in the above example.

This use of multiple place elements should be distinguished from the (possibly simpler) case where a number of places with some property in common are being grouped together for convenience, for example, in a gazetteer. The listPlace element is provided as a means of grouping places together where there is no implication that the grouped elements constitute a distinct place. For example: Herefordshire Abbey Dore 51.969604 -2.893146 Acton Beauchamp Hereford Leominster

There are many different kinds of information which it might be considered useful to record for a place in addition to its name and location, and the categories selected are likely to be very project-specific. As with persons therefore these Guidelines make no claim to comprehensiveness in this context. Instead, the generic state, trait, and event elements defined by this module should be used. Each of these may be customized for particular needs by means of their type attribute. These are complemented by a small number of predefined elements of general utility:

These are all specializations of the generic trait element. This element may be used for almost any kind of event in the life of a place; no specialized version of this element is proposed, nor do we attempt to enumerate the possible values which might be appropriate for the type attribute on any of these generic elements.

Here is an example, showing how the specific and generic elements may be combined: Iceland Ísland 65.00 -18.00 Area: 103,000 sq km

Constitutional republic

In the following example, the climate example is used to provided a detailed discussion of this particular aspect of the information available about a particular place: Greece Greece's climate is divided into three well defined classes: Mediterranean It features mild, wet winters and hot, dry summers. Temperatures rarely reach extremes, although snowfalls do occur occasionally even in Athens, Cyclades or Crete during the winter. Alpine It is found primarily in Western Greece (Epirus, Central Greece, Thessaly, Western Macedonia as well as central parts of Peloponnesus like Achaea, Arcadia and parts of Laconia where the Alpine range pass by) Temperate It is found in Central and Eastern Macedonia as well as in Thrace at places like Komotini, Xanthi and northern Evros. It features cold, damp winters and hot, dry summers.

As the above example shows, state and trait elements, and others of the same class, can be nested hierarchically within each other. When this is done, values for the type attribute are to be understood as cumulatively inherited, as elsewhere in the TEI scheme (for example on category or linkGrp). In the following example, the outermost population element concerns the squirrel population between the dates given. This is then broken down into red and gray squirrel populations, and within that into male and female: 12 15 23 45 The dating and responsibility attributes here behave slightly differently from the type attribute: responsibility is not an additive property, and therefore an element either states it explicitly, or inherits it from its nearest ancestor. Dating is slightly different again, in that a child element may specify a date more precisely than its parent, as in the example above

Events may also be subdivided into other events. For example, a two part meeting might be represented as follows: All day meeting to resolve content models first part second part

An event element is usually used to record information about a place, or a person; for this reason the element usually appears as content of a place or person. However, it is also possible to describe events independently of either a person or a place. This may be useful in such applications as chronologies, lists of significant events such as battles, legislation, etc.

The listEvent element is a member of the model.listLike class, and may therefore appear wherever lists are permitted, in the same way as the listPerson, listPlace etc. elements described elsewhere in this chapter.

The relation element may also be used to express relationships of various kinds between places, or between places and persons, in much the same way as it is used to express relationships between persons alone. Returning to the Mascarene Islands example cited above, we might define the island group and its constituents separately, but indicate the relationship by means of a relation element: Mascarene islands Mascarenhas Archipelago Mauritius Rodrigues Réunion

This stand-off style of representation has the advantage that we can now also represent the fact that a place may be a part of more than one other place; for example, Réunion is part of France, as well as part of the Mascarenes. If we add a declaration for France to the list above: France we can now model this dual allegiance by means of a relation element:

As noted above, relative dates and times such as in the Two Hundredth and First Year of the Republic, twenty minutes before noon, and, more ambiguously, after the lamented death of the Doctor or an hour after the game have two distinct components. As well as the absolute temporal expression or event to which reference is made (e.g. noon, the game, the death of the Doctor, [the foundation of] the Republic), they also contain a description of the distance between the time or date which is indicated and the referent expression (e.g. the Two Hundredth and First Year, twenty minutes, an hour); and (optionally) an offset describing the direction of the distance between the time or date indicated and the referent expression (e.g. of implying after, before, after).

The distance component of a relative temporal expression may be encoded as a temporal element in its own right using either date or time, or with the more generic measure element. A special element, offset, is provided by this module for encoding the offset component of a relative temporal expression. The absolute temporal expression contained within the relative expression may be encoded with a date or time element; in turn, those elements may of course be relative, and thus contain date or time elements within themselves. This allows for deeply nested structures such as the third Sunday after the first Monday before Lammastide in the fifth year of the King's second marriage ... but so does natural language.

In the following examples, the when and dur attributes have been used to simplify processing of variant forms of expression: A fortnight before Christmas 1786 I reached the station precisely half an hour after the departure of the afternoon train to Boston

In the following example, a nested date element is used to show that my birthday and the cited date are parts of the same temporal expression, and hence to disambiguate the phrase A week before my birthday on 9th December: A week before my birthday on 9th December The alternative reading of this phrase could be encoded as follows: A week before my birthday on 9th December

Where more complex or ambiguous expressions are involved, and where it is desirable to make more explicit the interpretive processes required, the feature structure notation described in chapter may be used. Consider, for example, the following temporal expression which occurs in the of August 1850, referring to the summer holiday known in Glasgow simply as the Fair: Not only is the city, during the Fair, a horrible nucleus of immorality and wickedness; it sends our multitudes to pollute and demoralize the country.

For the definition of the ana attribute, see chapter (in particular ). It is used here to link the temporal phrase with an interpretation of it. Like most traditional fairs and market days, the Glasgow Fair was established by local custom and could vary from year to year. Consequently, in order to provide such an interpretation, it is necessary to draw upon additional information which may or may not be located in the particular text in question. In this case, it is necessary at least to know the spatial and temporal context (year and place) of the fair referred to. These and other features required for the analysis of this particular temporal expression may be combined together as one feature structure of type date-analysis: the Fair Glasgow 1850-08-08 1850-09-19 For further discussion of feature structure representation see chapter .

The following are examples of absolute temporal expressions.

The university's view of American affairs produced a stinging attack by Edmund Burke in the Commons debate of 26 October 1775 Friday, 14 May 1993

It may be useful to categorize a temporal expression which is given in terms of a named event, such as a public holiday, or a named time such as tea time or matins: In New York, New Year's Day is the quietest of holidays, Independence Day the most turbulent.

Absolute temporal expressions denoting times which are given in terms of seconds, minutes, hours, or of well-defined events (e.g. noon, sunset) may similarly be represented using the time element. The train leaves for Boston at 13:45 At sunset we walked to the beach. The train leaves for Boston at a quarter of two

The attributes for normalization of dates and times so far described use a standard format defined by . This format is widely accepted and has significant software support. It is essentially a profile of ISO 8601 . The full ISO standard provides formats not available in the W3C recommendation, for example, the capability to refer to a date by its ordinal date or week date, or to refer to a century. It also provides ways of indicating duration and range.

When this module is included in a schema, the following additional attributes are provided: These attributes may be used in preference to their W3C equivalent when it is necessary to provide a normalized value in some form not supported by the W3C attributes. For example, a century date in the W3C format must be expressed as a range, using the from attribute together with either the to attribute or the dur (duration) attribute: fourteenth century fourteenth century With the attribute when-iso, however, it is possible to express the same normalized value in any of the following additional ways: fourteenth century fourteenth century fourteenth century

All date-related encoding described above makes use of the Gregorian calendar, on which both the ISO and W3C datetime formats are based. However, historical texts often pre-date the invention of the Gregorian calendar in the 16th century, or its adoption in Europe over the following centuries, and many other calendars are used in texts from other cultures and contexts. Non-Gregorian dates can be encoded using methods described below.

First, a Calendar Description element needs to be supplied in the teiHeader as described in :

The following attributes can now be used to encode dates using this calendar:

The Poole by S. Giles Churchyarde was a large water in the yeare 1244.

The calendar attribute is used to specify the calendar used in the text content of the dating element which bears it. However, just as we use, for instance, when, notBefore, notAfter etc. to provide more precise expressions of dates and times in a constrained and computable form, it is often necessary to express a date or a date-range from a non-Gregorian calendar in a more precise manner. The attributes whose names end in -custom are provided for this purpose, and the datingMethod is used to identify the calendar used in the content of these attributes: The Tryumphs of Peace. That Celebrated the Solemnity of the right Honorable Sr Francis Iones Knight, at his Inauguration into the Maioraltie of London, on Monday being the 30. of October, 1620. Here, the calendar attribute specifies the calendar used in the text content of the date element, as before, whereas the datingMethod attribute signifies that the calendar used in the when-custom attribute is also Julian. The schema could be customized in order to constrain the content of custom attributes in a manner similar to the constraints provided on regular Gregorian dating attributes such as when, to enforce consistency in the use of non-Gregorian dates.

Custom dating attributes can be combined with any of the standard dating attributes in order to provide a standardized Gregorian version of a non-Gregorian date. We might enhance the preceding example with the addition of when, providing the Gregorian calendar equivalent of the Julian date: 30. of October, 1620.