C’est pourquoi je vous propose ici une sélection. The following examples indicate the range of possibilities: It can be difficult to draw a clear distinction between aspects of a manuscript which are purely physical and those which form part of its intellectual content. Within three years, an aisled nave had been added to the stone church, and the first permanent claustral buildings built in stone and roofed in tile had been completed. Entry for Bodleian MS. Cette classe définit l’ensemble des éléments de niveau fragment et de niveau intermédiaire ; de nombreux modèles de contenu y font appel, y compris ceux qui sont relatifs aux divisions textuelles.

Nom: painterly pack 1.4.2
Format: Fichier D’archive
Système d’exploitation: Windows, Mac, Android, iOS
Licence: Usage Personnel Seulement
Taille: 42.69 MBytes

However, it is often also convenient to record information such as negative numbers or digital identifiers for unpublished collections of manuscript images maintained within the holding institution, as well as to provide more detailed descriptive information about the surrogate itself. Il y a d’autres photos dans mon site jeandhugues. Il y a eu une rencontre entre mes « photos à grain » et leur procédé dit « au charbon ». Bought from the rev. Firstly, several unwanted elements are deleted.

This Reference Guide defines an XML format for the structure of the data which all ENRICH partners will contribute to the Manuscriptorium, either directly or indirectly by means of a harvester or transformation process.

The format is formally expressed by a schema which is generated from the XML source of this guide. The guide itself is a conformant subset of Release 1. Within Manuscriptorium, only the first two are required.

However, the schema documented here also provides for the third, in the interest of completeness and for the assistance of ENRICH partners wishing to provide richer access facilities to their holdings.

The remainder of this Guide describes each of these aspects in more detail, using material derived from the P5 release of the TEI Guidelines. Other header components, if present, will be ignored by Manuscriptorium; they will be retained for storage in the system and returned on request, but their content is not processed for any purpose, and they may not be visible for searching purposes.

The value for xml: It should however be prefixed by an identifier for the partner concerned, so as to avoid possible identifier collisions. If no value is supplied, the assumption is that the language of the description is English. The first of these components, msIdentifieris mandatory; it is described in more detail in 1. It is followed by either one or more paragraphs, marked up as a series of p elements, or one or more of the specialized elements msContents 1.

These elements are all optional, but if used they must appear in the order given here. Finally, in the case of a composite manuscript, a full description may also contain one or more msPart elements 1. The dimensions element will normally occur within the element describing the particular feature or aspect of a manuscript whose dimensions are being given; thus the size of the leaves would be specified within the support or extent element part of the physDesc element discussed in 1.

The type attribute on the dimensions element is used to specify more exactly the item being measured. Attributes minmaxand scope are used only when the measurement applies to several items, for example the size of many or all the leaves in a manuscript; attributes atLeast and atMost are used when the measurement applies to a single item, for example the size of a specific codex, but has had to be estimated.

The units in which dimensions are measured should always be specified using the unit attribute, which will normally be taken from a closed set of values appropriate to the project, using standard units of measurement wherever possible.

If the only data available for the measurement uses some other unit, or it is preferred to normalize it in some other way, then it may be supplied as a string value using the extent attribute.

The content of these elements, if present, simply copies the way that the measurement is presented in some source text; it may be omitted. The locus element is used to reference a single location within a paintdrly, typically to specify the location occupied by the element within which it appears. If for example 1.4. is used as the first component of an msItem element, or of any of the more specific elements appearing within one see further section 1. Alternatively, the key attribute may be used to supply an identifying code for the person referenced by the name independently of both the existence of a person element and the use of the standard URI reference mechanism.

Although such practices clearly reduce the interchangeability of the resulting encoded texts, they may be judged more convenient or practical in certain painterlyy. All the person elements referenced by a particular document set should be collected together within a listPerson element, located in the TEI Header.

Topic Liste des pack de texture pour la 1.4.2 – Page 2

This functions as a lack of prosopography for all the people referenced by the set of manuscripts being described, in much the same way as a listBibl element in the back matter may be painterl to hold bibliographic information for all the works referenced. Similar mechanisms are used to maintain and reference canonical lists of places or organizations. A manuscript’s actual physical location may occasionally be different from its place of ownership; at Cambridge University, for example, pxinterly owned by various colleges are kept in the central University Library.


Normally, it is the ownership of the manuscript which should be specified in the manuscript identifier, while additional or oack precise information on the physical location of the manuscript can be given within the adminInfo element, discussed in section 1. At least one of the elements listed above must be given within the msIdentifier and they must, if present, appear in the order given. Like namethese elements are all also members of the attribute class att.

As mentioned above, the smallest possible description is one that contains pck the element msIdentifier ; good practice in all but exceptional circumstances requires the presence within it of the three sub-elements settlementrepositoryand idnosince they provide what is, by common consent, the minimum amount of information necessary to identify a manuscript.

Phrase-level elements, such as titlenamedate paintedly, or the specialized elements origPlace and origDatepaniterly also be used within a head element, but it should be remembered that the head element is intended principally to contain a heading. More structured information concerning the contents, physical form, or history of the manuscript should be given within the specialized elements described below, msContentsphysDeschistoryetc.

However, in simple cases, the p element may also be used to supply an unstructured collection of such information, as in the example given above 1 Manuscript Description Metadata. Each discrete item in a manuscript or paintrely part can be described within a distinct msItem and may be classified using the class attribute. In addition, an msItem may painyerly nested msItem elements. Untagged running text is not permitted directly within an msItemunless it is given within a p element, in which case none of the other component elements listed above is permitted.

When used within a manuscript description, the title element should be used to supply a regularized form of the item’s title, as distinct from any rubric quoted from the manuscript. If the item concerned has a standardized distinctive title, e. Roman de la Rosepakc this should be the form given as content of the title element, with the value of the type attribute given as uniform. Similarly, if used within a manuscript description, the author element should always contain the normalized form of an author’s name, irrespective of how or whether this form of the name is cited in the manuscript.

If it is desired to retain the form of the author’s name as given in the manuscript, this should be given in the docAuthor element, or as a distinct name element, within the text at the point where it occurs. Note that the key or ref attributes can be used, on titles and on author names oainterly on names in general, to link the name to a more detailed description of the person or work concerned see further 1. The form and scope of language identifiers recommended by these Guidelines is based on the IANA standard described at http: Where additional detail is needed correctly to describe a language, or to discuss its deployment in a given text, this should be done using the langUsage element in the TEI Header, within which individual language elements document the languages used: Most manuscript descriptions touch on several of these categories of information though few include them all, and not all distinguish them as clearly as we propose here.

In particular, it is often the case that an existing description will include within a single paragraph, or even sentence, information for which we propose distinct elements. In this case, if rewriting is pzinterly an option, the existing prose paintery be marked up simply as a series of p elements, directly within the physDesc element.

The physDesc element may thus be used in either of two distinct ways. It may contain a series of paragraphs addressing topics listed above and similar ones. Alternatively, it may act as a container for any choice of the more specialized elements described in the remainder of this section, each of which itself contains a series of paragraphs, and may also have more specific attributes. If the two ways are combined in a single description, care should be taken to avoid duplication and all paragraphs of generic description must precede the first of the more specialised elements.

Each of these elements contains paragraphs relating to the topic concerned. Within these paragraphs, phrase-level elements in particular those discussed above at 1.

painterly pack 1.4.2

This example combines information which might alternatively be more precisely tagged using 11.4.2 more specific elements described in the following subsections. Where the layout element paci used, the layout oainterly often be sufficiently regular for the attributes on this element painterlg convey all that is necessary; more usually however a more detailed treatment will be required.

The attributes are provided as a convenient shorthand for commonly occurring cases, and should not be used except where the layout is regular. The value NA not-applicable should be used for cases where the layout is either very irregular, or where it cannot be characterized simply in terms of lines and columns, for example, where blocks of commentary and text are arranged in a regular but complex pattern on each page.

Note the use of the term element to mark specific technical terms within the context of the handDesc element. As the above example shows, the attributes script and scope are both required on handNote. The locus element, discussed in section 1. In addition, when a full or partial transcription of a manuscript is available in addition to the manuscript description, the handShift element described in http: It can be difficult to draw a clear distinction between aspects of a manuscript which are purely physical and those which form part of its intellectual content.


This is particularly true of illuminations and other forms of decoration in a manuscript. We propose the following elements for the purpose of delimiting discussion of these aspects within a manuscript description, and for convenience locate them all within the physical description, despite the fact that the illustrative features of a manuscript will in many cases also be seen as constitutiing part of its intellectual content.

Information about the origins of the manuscript, its place and date of writing, should be given as one or more paragraphs contained by a single origin element; following this, any available information on distinct stages in the history of the manuscript before its acquisition by its current holding institution should be included as paragraphs within one or more provenance elements. Finally, any information specific to the means by which the manuscript was acquired by its present owners should be given as paragraphs within the acquisition element.

The surrogates element should not be used to describe digital images of the manuscript since the facsimile element described in 2 Metadata about digital facsimiles is provided for this purpose. None of the constituent elements of additional is required.

Painterly texture pack télécharger

If any is supplied, it may appear once only; furthermore, the order in which elements are supplied should be as specified above. The status attribute of availability must take one of the following values: The change element within the revisionDesc element of painterlt TEI Header should be used to document the revision history of the record.

It should not be given within the recordHist element. For ENRICH purposes, information about digital images of the manuscript being described should be provided within the facsimile element discussed in section 2 Metadata about digital facsimiles below rather than within the surrogates element.

painterly pack 1.4.2

The facsimile element is used to describe the digital images of the manuscript being made available to the Paack project. It contains, as a psinterly, one surface element for each distinct page image, which in turn specifies one or more graphic element.

These elements are used as described in the TEI Guidelines, section This example defines only two pages. Painterlly are panterly images associated paijterly the first page, which is represented by the surface element with unique identifier LSB-1rand two with the second, which has no identifier. Each image is represented by means of a TEI graphic element.

As well as acting as a container for the various images associated with a page, the surface element defines paci abstract co-ordinate system which may be used when defining additional zones of interest on the page. In this example, the location of an initial letter on the page is defined, since we have a graphic representing this detail.

The zone within which the initial letter falls is in the box defined by the co-ordinates 20,20,70,70 within a grid defined by the co-ordinates 0,0, Thus, if the surface depicted actually measured by mm, the initial letter would occupy a 50 X 50 mm square, with its upper left corner located 20 mm from the left and 20 mm from the top edges of the surface.

Note however that the numbers used to express co-ordinates are not measurements in any specific units and should not be used to determine the actual image size, since these may in any case vary greatly: The painterlh attribute is used to indicate the format of the graphic file itself, and may be any valid MIME type, oack defined by the IANA, for example jpegpngbmptiff etc. The decls attribute is used to indicate an external URI from which further metadata applicable to this image may be found.

In this case we are assuming that there is a definition which can be used to indicate characteristics of a thumbnail image at the address indicated. Note that this must be given in full, since it would otherwise be interpreted as an address relative to the value 14.2 the xml: We include in the schema the four basic key TEI modules headercoreteiand textstructure.

We also include five specialized modules: All the elements and attributes defined by these modules are included in the ENRICH schema, with the following modifications. Firstly, several unwanted elements are deleted. Secondly, some optional attributes have been made compulsory, and their range of possible values are constrained.

Finally, the content model for a small number of elements has been simplified to paihterly unwanted alternatives. The following elements are deleted: On the altIdentifier element, the type attribute is compulsory, and must take one of the following values: On the availability element, the status attribute is compulsory, and must take one of the following values: