Metadata elements for the Inscription physical objects Sample Clauses

Metadata elements for the Inscription physical objects. This set of metadata elements corresponds to the inscription as physical objects that may be carried by an information carrier object. Inscriptions are represented by E34 Inscription and related to E84 Information Carrier via P128 carries Inscriptions can also be represented in an independent document by indicating the identifier of the carrier object that bears it using property P128B is carried by. Object Title (mandatory, cardinality: 1) It contains a text to help identify the object. It can consist of a single field or the composition of several fields. Represented by E35 Title and related to E84 Information Carrier via P102 has title Corresponds in TEI/EpiDoc to /TEI/teiHeader/fileDesc/titleStmt/title Trismegistos number (not mandatory but recommended, cardinality: 1) It contains the Trismegistos identifier (TM_no or TM_id) associated to the Trismegistos document that represents the same epigraphic object being described. Represented by E42 Identifier and related via P1 is identified by Corresponds in TEI/EpiDoc to /TEI/teiHeader/fileDesc/publicationStmt/idno Type of inscription (not mandatory, cardinality: 1) It contains a vocabulary element that indicates the type of text inscribed on the monument. Represented by E55 Type related to E34 Inscription via P103 was intended for Corresponds in TEI/EpiDoc to /TEI/teiHeader/profileDesc/textClass/keywords/term This will be specified using a <term> element within a <keywords> element. The <term> element will use a @ref attribute to indicate the EAGLE vocabulary value corresponding to this particular type of inscription. All of this will be enclosed into a <textClass> element in the profileDesc section of the document. Engraving technique (not mandatory, cardinality: 1) It contains a vocabulary element that indicates the writing technique used for this inscription. (Common EAGLE vocabulary) Represented by E55 Type related to E34 Inscription via P2 has type Corresponds in TEI/EpiDoc to /TEI/teiHeader/fileDesc/sourceDesc/msDesc/physDesc/objectDesc/layoutDesc/layout/rs Metre (not mandatory, cardinality: 1) It contains a value that indicates whether the text of the inscription is metrical and possibly the type of metric. Free text. Represented by E62 String related to E34 Inscription via P3 has note Corresponds in TEI/EpiDoc to /TEI/teiHeader/fileDesc/sourceDesc/msDesc/physDesc/objectDesc/layoutDesc/layout/rs Size of Epigraphical Field (not mandatory, cardinality: *) It contains the dimensions (in centimeters) of...
Sample 1
AutoNDA by SimpleDocs

Related to Metadata elements for the Inscription physical objects

  • ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to Image Access via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one (1) dataset per workday per OCN. If BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.

  • Geological and Archeological Specimens If, during the execution of the Work, the Contractor, any Subcontractor, or any servant, employee, or agent of either should uncover any valuable material or materials, such as, but not limited to, treasure trove, geological specimens, archival material, archeological specimens, or ore, the Contractor acknowledges that title to the foregoing is vested in the Owner. The Contractor shall notify the Owner upon the discovery of any of the foregoing, shall take reasonable steps to safeguard it, and seek further instruction from the Design Professional. Any additional cost incurred by the Contractor shall be addressed under the provision for changed conditions. The Contractor agrees that the Geological and Water Resources Division and the Historic Preservation Division of the Georgia Department of Natural Resources may inspect the Work at reasonable times.

  • Exception Where Databases Contain Sufficient Information A Reporting Financial Institution is not required to perform the paper record search described in subparagraph D.2. of this section if the Reporting Financial Institution’s electronically searchable information includes the following:

  • Physical File Characteristics 6.2.1 The Optional Daily Usage File will be distributed to <<customer_name>> via an agreed medium with CONNECT:Direct being the preferred transport method. The Daily Usage Feed will be a variable block format (2476) with an LRECL of 2472. The data on the Daily Usage Feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Demographic, Classification and Wage Information XXXXXX agrees to coordinate the accumulation and distribution of demographic, classification and wage data, as specified in the Letter of Understanding dated December 14, 2011, to CUPE on behalf of Boards of Education. The data currently housed in the Employment Data and Analysis Systems (EDAS) will be the source of the requested information.

  • Minimum Customer Support Requirements for TIPS Sales Vendor shall provide timely and commercially reasonable support for TIPS Sales or as agreed to in the applicable Supplemental Agreement.

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

  • Certification of Meeting or Exceeding Tobacco-Free Workplace Policy Minimum Standards A. Grantee certifies that it has adopted and enforces a Tobacco-Free Workplace Policy that meets or exceeds all of the following minimum standards of:

  • Act Identifier Title Shoulder note Iron Ore (Robe River) Agreement Xxx 0000 First Schedule Iron Ore (Robe River) Agreement Second Schedule First variation agreement Third Schedule Second variation agreement [s. 3B] Fourth Schedule Third variation agreement [s. 2] Fifth Schedule Fourth variation agreement Sixth Schedule Fifth variation agreement

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