Traditionality in synchronic reperformances Sample Clauses

Traditionality in synchronic reperformances. In the conceptualisation of folklore and folksong, the category of ‘tradition’ has played a significant role. The ‘traditional’ aspect of folklore and folksong – since its intellectual roots in the nineteenth century, from which the two concepts emerged, up until recent times – has generally pointed to an undefined cultural primitivism, which proves however to be in most cases groundless and misleading (cf. §1.1.2.iv). Interestingly, we also find in antiquity a similar generalisation, especially in the perception of songs that are regularly performed in a religious context and that are described (often misleadingly) as vaguely ‘ancient’ (cf. §1.2.4). Likewise, even Xxxxxxxx’s hymn, though not attested before Xxxxxxxx, is referred to by Xxxxxxx of Tyre (Or. 7.1) as an ‘ancient song’ (ἀρχαῖον ᾆσμα). In order to better understand the reasons for similar (ancient and modern) generalisations and misperceptions, we should go beyond the strict and unilateral relation between tradition and the past, by primarily reflecting on what has been said above about the ‘synchronicity’ element in the performance of folk songs. Those songs that are constantly reperformed in a recurring event (synchronic reperformances) can be considered ‘traditional’ not in the sense of being ‘old-fashioned’ or ‘primitive’, but as being part of a habitual – in some cases even daily – routine. This kind of traditionality does not look at how ancient a song actually is, but takes into account the fact that songs, old and new, can become part of a traditional event, and within it assume a cultural value. This interpretative view is consistent with the most innovative approaches adopted in the analysis of the category of ‘tradition’. ‘Tradition’ still indicates the transmission of knowledge, but this transmission, as is now recognised, may not only establish a line of communication from the past to the present (cf. the nineteenth-century interpretation), but also extend a line of cultural communication from the present to the past.246 On this view, even what is new can assume a symbolic value that marks it as traditional. A society can acknowledge the 246 For an overview on this approach, with particular regard to the Homeric ‘tradition’, see Cantilena 2012. cultural value of certain phenomena and accordingly attribute to them a characteristic of antiquity that they often do not possess. In some cases, this cultural acknowledgement is less spontaneous but can be traced back to a constructed and ...
AutoNDA by SimpleDocs

Related to Traditionality in synchronic reperformances

  • Supplier Diversity Seller shall comply with Xxxxx’s Supplier Diversity Program in accordance with Appendix V.

  • Registry Performance Specifications Registry Performance Specifications for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Required Coverages For Generation Resources Of 20 Megawatts Or Less Each Constructing Entity shall maintain the types of insurance as described in section 11.1 paragraphs (a) through (e) above in an amount sufficient to insure against all reasonably foreseeable direct liabilities given the size and nature of the generating equipment being interconnected, the interconnection itself, and the characteristics of the system to which the interconnection is made. Additional insurance may be required by the Interconnection Customer, as a function of owning and operating a Generating Facility. All insurance shall be procured from insurance companies rated “A-,” VII or better by AM Best and authorized to do business in a state or states in which the Interconnection Facilities are located. Failure to maintain required insurance shall be a Breach of the Interconnection Construction Service Agreement.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Standards for Network Elements 1.8.1 BellSouth shall comply with the requirements set forth in the technical references, as well as any performance or other requirements identified in this Agreement, to the extent that they are consistent with the greater of BellSouth’s actual performance or applicable industry standards.

  • HOOSIER HEALTHWISE SCOPE OF WORK  Requirements for Reinsurance Companies  The Contractor shall submit documentation that the reinsurer follows the National Association of Insurance Commissioners' (NAIC) Reinsurance Accounting Standards.  The Contractor shall be required to obtain reinsurance from insurance organizations that have Standard and Poor's claims- paying ability ratings of "AA" or higher and a Xxxxx’x bond rating of “A1” or higher, unless otherwise approved by OMPP.  Subcontractors  Subcontractors’ reinsurance coverage requirements must be clearly defined in the reinsurance agreement.  Subcontractors should be encouraged to obtain their own stop-loss coverage with the above-mentioned terms.  If subcontractors do not obtain reinsurance on their own, the Contractor is required to forward appropriate recoveries from stop- loss coverage to applicable subcontractors.

  • Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:

Time is Money Join Law Insider Premium to draft better contracts faster.