Swash-S motif on button-and-loop fastener Wild's Class VIa, 2nd century AD Portable Antiquities Scheme, HAMP3302 |
Bronze driving-harness snaffle-bit decorated with red and yellow enamel Birrenswark, Dumfriesshire, Last half of the 1st cent AD (click to enlarge) |
That the snaffle-bit had a lot of wear and was repaired a few times is interesting. The Torrs Farm pony-cap had also been repaired, apparently in Ireland. That is interesting because Dumfriesshire is adjacent to Kirkcudbrightshire, where Torrs farm is located. The bit is not of an Irish style, though, and no bits of its type have been found in Ireland. Iron age sites are not thick on the ground in Dumfriesshire, the only one I know of has not been excavated at all. It seems most likely that the snaffle-bit had not travelled that far -- Roman soldiers seemed just to go for the trinkets, so Traprain Law is a slightly better possibility for the button-and- loop fastener. Traprain Law seems to mainly have objects with multi-coloured enamel within small cells, though and the fastener does not quite fit the profile.
I am defining the Swash-S motif as an implied S-shape with a keel at each of the four corners. Keeling does have an earlier history, but we have to take all of the elements of the motif into consideration. As Vincent Megaw says, "Similar is not the same as same".
A related motif, of course, is the Swash-N. While the Stitchill, Roxburghshire collar has a wildly elaborated form of this motif which includes two keels, and the Swash-N is a response to a large rectangular (Roman), space, I think a closer relative to the S-form on the fastener is the armlet which was found at Plunton Castle, Borgue, Kirkcudbrightshire.
Plunton Castle, Kirkcudbrightshire, armlet late 1st cent AD. (click to enlarge) |
Find spots do not give us a full picture, but at least it is better than imagining archaeologically excavated sites full of context and dateable associated finds. This is not the common pattern for Britain for this sort of material as a whole, but in this region, such is pure fantasy. Again, we return to one of the subjects of yesterday's post and realize that when political factors come into play, especially nationalistic archaeology and archaeologists who criticize the value of stray finds and public involvement from detectorists and collectors alike, even to the point of criticizing art-historical methodologies used on unprovenanced objects -- even if first published on Ebay! Then, we have to take into consideration the man as well as what he writes. It is the postmodern thing to do. Neglecting comparative typology means that you will be able to write very little about the subject, and what you do write will not be very good. This could even lead condemnations of the subject itself! Before I go onto the next topic, here are few more Swash-S links that you might find useful:
http://finds.org.uk/database/artefacts/record/id/86014
http://finds.org.uk/database/artefacts/record/id/55925
http://finds.org.uk/database/artefacts/record/id/148466
http://finds.org.uk/database/artefacts/record/id/275719
Printed literature can make tracking motifs and elements very difficult. Those who do have the sort of intellectual powers that are not very common. Others who lack such abilities might start applying The Fox and the Grapes phenomenon to the task. The databases we see are often not wide enough in their scope (apart from those like the Celtic Coin Index which includes archaeological excavated, stray find, collection and trade examples). Databases also suffer from designs too slanted to certain types of interests, mix and match terminology, and human inadequacies of all sorts. If you enter a term like "bronze", the interface should ask you if an analysis has defined the object as such and if not, should list all such variations as "copper or copper alloy". It might even ask you about brass. You cannot have identical things scattered all over the place. Clean the data before you build the database and base its design on clean data.
My idea for the database of the future, has at its core, three qualities:
Object; Attributes; Subsidiary ObjectsThese are all "nested": an attribute can become an object in its own right, and have its own attributes, and subsidiary objects, and so can a subsidiary object. I will give you a simple example: A Ford Pinto is the object. Its steering wheel is a subsidiary object -- if someone has removed the steering wheel, it is still a subsidiary object that is designated as "missing". Cars are also an object, and in that case, the Ford Pinto is an attribute: cars can, but do not have to always include Ford Pintos. A parking lot is an object and cars are one of its attributes, as are marked parking spaces. Parking lots might also contain other objects that are usually found in such places: trucks, vans, even tanks and troop carriers.
All of these are attributes -- we are not that surprised to find them there and we might even expect to do so (depending on what sort of parking lot we are looking at). A box of oranges on the back seat of a Ford Pinto is a subsidiary object, not an attribute. If you see a Ford Pinto, you do not think of boxes of oranges. If the Ford Pinto is engulfed in flames, then the fire is a subsidiary object. However if there are enough Ford Pintos recorded as being in flames, then the subsidiary object will automatically be promoted to an attribute!
The box of oranges on the back seat of our burning Pinto also has sets of attributes and subsidiary objects --which might include flames, too, in this case, but will likely include oranges, even if it is an empty orange box. The oranges have skins, or they might have been peeled, they might have seeds and so on -- everything is nested.
They connect via "fluid nodes" This is a very crude brain model, nowhere near as good as the one in our skulls, but one that can be programmed to rearrange the data both as it is entered into the database and as the database is queried at certain times. While behaving a bit like a search engine in some cases, it would be far more sophisticated as it is constantly altering our perceptions of reality. Each database would be used for specific sorts of tasks -- It might be a museum database, or it might be a police database. It could be used for any interest. Each database would be linked through networks to similar databases used for other things, but it would not connect the data unless it "spotted" certain associative patterns. For example, a stolen museum object on a police database would alert its original museum automatically. Or a stolen object might later show up in a museum, and it would alert the police database. Data is being sent back and forth all the time. We do not yet have the technology to build and operate such things. Until that time, we must muddle along as best we can, and always be on the lookout for things in places we do not think about, or like.
Have a good weekend!
No comments:
Post a Comment