Delian League Tribute Assessment Lists Phoros Records
Resolve exact independently verified phoros inscription IDs, date, edition and assessment context; no fabricated full Delian League registry. Exact caller independently verified reference-registry lookup retaining source/edition/context. No built-in complete dataset, current status or attribution authority fabricated.
Description
Tribute lists record particular assessments and documentary contexts.
Tribute lists record particular assessments and documentary contexts.1
Source and edition metadata matter when distinguishing a transmitted record from a complete fiscal inventory. Use Delian League Tribute Assessment Lists Phoros Records to retrieve an exact caller-supplied reference entry.
When to use Delian League Tribute Assessment Lists Phoros Records
Use Delian League Tribute Assessment Lists Phoros Records to retrieve an exact caller-supplied reference entry. Choose the applicable source edition, preserve its identifier and supply the independently reviewed keys and reference texts.
How to use Delian League Tribute Assessment Lists Phoros Records and understand its results
- Choose the applicable source edition, preserve its identifier and supply the independently reviewed keys and reference texts.
- Enter Caller verified source edition, Caller verified reference keys, Caller verified reference texts, Query reference key using the field table and validation rules below, then run the tool.
- Read Matched Caller Reference, Reference Source Edition in the Result object; interpret the units, signs, ordering and unknown-value placeholders described below.
- Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerVerifiedSourceEdition | Caller verified source edition | string | Required; constraints below |
| callerVerifiedReferenceKeys | Caller verified reference keys | array of string | Required; constraints below |
| callerVerifiedReferenceTexts | Caller verified reference texts | array of string | Required; constraints below |
| queryReferenceKey | Query reference key | string | Required; constraints below |
Provide aligned, nonempty arrays of reference keys and independently verified notices, then enter the exact query key. Keys must be unique, nonblank and at most 128 UTF-16 code units long; notices must be nonblank. Matching is case sensitive and does not trim the query or returned text. The matching notice is returned unchanged; an unknown key is an input error. The reference contents and their applicability are supplied by the caller; the tool does not retrieve external records or verify source authority. Also supply a nonblank source/edition/context ID of at most 256 UTF-16 code units. It is returned unchanged as referenceSourceEdition without authenticity verification.
matched reference = suppliedTexts[indexOfExactQueryKey(suppliedKeys)] Use the field order, units and branch conditions described above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Object containing the named result fields below. | object |
| result.matchedCallerReference | Caller reference text matched exactly by key, unchanged. | string |
| result.referenceSourceEdition | Caller source/edition identifier, unchanged and unverified. | string |
{
"input": {
"callerVerifiedSourceEdition": "caller-reviewed-source-edition",
"callerVerifiedReferenceKeys": [
"verified-record-a",
"verified-record-b"
],
"callerVerifiedReferenceTexts": [
"Athenian tribute list source-qualified context a",
"Athenian tribute list source-qualified context b"
],
"queryReferenceKey": "verified-record-a"
},
"output": {
"result": {
"matchedCallerReference": "Athenian tribute list source-qualified context a",
"referenceSourceEdition": "caller-reviewed-source-edition"
}
}
}Limitations and assumptions
Source and edition metadata matter when distinguishing a transmitted record from a complete fiscal inventory. Apply the exact scope and assumptions explained above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.
Alternative or Complementary methods
Use Pliny Younger Vesuvius 79 AD Eyewitness Letter Chronology for a related task: Pliny's eruption letters combine accounts of his uncle with his own experiences.
Use Pompeii Graffiti Corpus Inscriptionum Latinarum Catalog Lookup for a related task: Graffiti cataloguing connects an inscription with a corpus entry and edition.
References
Similar or alternative tools
- Pliny Younger Vesuvius 79 AD Eyewitness Letter Chronology
Pliny's eruption letters combine accounts of his uncle with his own experiences.
- Pompeii Graffiti Corpus Inscriptionum Latinarum Catalog Lookup
Graffiti cataloguing connects an inscription with a corpus entry and edition.