1. OVERVIEW
| Roster | Date | Author | Record |
|---|---|---|---|
| Category | !! | !! | installation |
| Best definition | 1999-06-28 | jo | isolated individual brick [Input: J716JO.j] |
2. IDENTIFICATION
Designation
| Roster | Date | Author | Record |
|---|---|---|---|
| Description (summary) | 1999-06-28 | jo | line of red bricks seen through the pit a7 and cut by it. [Input: ZG127ms.j] |
3. STRATIGRAPHY
Recovery/Assignment
| Roster | Date | Author | Record |
|---|---|---|---|
| Daily notes about recovery of elements | 1999-07-13 | jo | by the removal of the filling of a7, S of f96, we were able to look at the pavement f96 from the side where we found out that the pavement was built of 6 courses of bricks on top of what there is possibly the continuation of f146; otherwise it sets directly on top of f172. [Input: J724AB.j] |
| Strategy (projected or implemented) | 1999-07-03 | gb | The brick paving is limited to the east and the west, and it slopes slightly to the west. We consider the possibility of cutting the deposit to the east, in order to reach the stone "paving" at the base of the foundations of the two walls f199 and f168. But for now we will wait, since it seems important to understand better the relationship between the paving and the walls. [Input: J718OKK.j] |
Volumetric Localization
| Roster | Date | Author | Record |
|---|---|---|---|
| Locus | 1999-06-28 | jo | k6 [Input: J716JO.j] |
| Height @top | 1999-06-28 | jo | line of bricks seen throw section of pit a7 [Input: J716JO.j] |
Contact Association
| Roster | Date | Author | Record |
|---|---|---|---|
| Type of contact: latest events | 1999-06-29 | jo | f78 (pit cut) cuts f96 (isolated individual brick) [Input: ZG127ms.j] |
| 1999-06-29 | jo | f79 (fill) abuts f96 (isolated individual brick) [Input: ZG127ms.j] | |
| 1999-07-05 | ab | f103 (accumulation C) covers f96 (isolated individual brick) [Input: J718AB.j] |
Spatial Aggregation
| Roster | Date | Author | Record |
|---|---|---|---|
| Aggregate (to which element belongs) | 1999-06-26 | jo | a17 (pavement), a21 (pavement) [Input: J718JO.j] |
Time Sequencing
| Roster | Date | Author | Record |
|---|---|---|---|
| Notes on time sequencing | 1999-07-03 | gb | see under f110. [Input: J718OKK.j] |
4. TYPOLOGY
Manufacturing
| Roster | Date | Author | Record |
|---|---|---|---|
| Assumption | 1999-07-03 | gb | A possible configuration of the paving might be as a series of wide steps, going down towards the east. This seems on the whole rather unlikely, but it might explain the loss of the bricks to the east -they would have been sheared near the top by the later accumulation. It will appear soon enough whether this hypothesis may be borne out or not by excavating to the west. [Input: J718OKK.j] |
Function
| Roster | Date | Author | Record |
|---|---|---|---|
| Generic function (1st degree of specificity) | 1999-07-02 | gb | A large new building seems to be lurking in the ground. For now, we have not assigned any label toit, but a clarification ought to emerge from the current excavations. At this point the following observations are of interest. (1) The baked brick paving in k6 links AK with the new building(as possibly does the stone "paving" below"). (2)The stones f109 in k9, even though very high, are suspiciously aligned with the general orientation of AK walls. Do they belong together? (3)We might have here the monumental entrance to a more proper "palace" than AK as currently known. If so, there may be a passage directly from sector C to the new building. [Input: J718OKK.j] |