ELAG Matei: PML1 Cataloguing the Romanian Cultural Heritage or yet another schema for heritage assets Dan Matei (CIMEC)

ELAG Matei: PML2 A new schema: why ? (CIMEC) the difficulty to manage many databases with overlapping content; limitations of MARC formats and the non- standard (but too simple) museum matadata; new insights via FRBR and CRM; the need for a data model for the (future) Romanian Shared Catalogue.

ELAG Matei: PML3 Why MARC is not enough ? ELAG 2004 (Trondheim) WS 10: the "1 to 1 principle" is not observed (i.e. matadata about about several resources in the same record); it is not too flexible, i.e. it is almost flat, it allows only 2 (let's say 3) hierarchical levels; no good control of the granularity of data; some tags (e.g. those for the headings) express two different things: a) the nature of the related resource, b) the kind of relationship; it does not allow (naturally) multilingual data within a record (for the fields with values in the language of the cataloguing).

ELAG Matei: PML4 Functions of the catalogue FRBR: the Frankfurt Principles (2003) [the Buenos Aires version (2004)] wording:... to enable a user: to find bibliographic resources in a collection (real or virtual) as the result of a search using attributes or relationships of the resources: –to locate a single resource –to locate sets of resources to identify a bibliographic resource or agent; to select a bibliographic resource that is appropriate to the user’s needs; to acquire or obtain access to an item described; to navigate a catalogue.

ELAG Matei: PML5 (Extra) functional requirements for the shared catalogues FR1: language neutrality, i.e. the textual elements could be expressed in several languages, and the language of en element could be detected automatically; FR2: traceability of changes, i.e. the modifications could be tracked, dated and attributed (thus, reversed); FR3: opinion neutrality, i.e. different opinions could coexist in the metadata, that is the elements could have alternative values, with clearly assigned intellectual responsibilities.

ELAG Matei: PML6 PML = Panizzi Markup Language sir Anthony Panizzi ( ) chief librarian of British Museum (1856 – 1867); the famous 91 cataloguing rules (1839).

ELAG Matei: PML7 Other XML-based formats marcxml (LC) – 2003; MODS : Metadata Object Description Schema (LC) – 2005; MADS : Metadata Authority Description Schema (LC) – 2005; BiblioML (French Ministry of Culture) – 1999; rdfs:frbr (Stefan Gradmann) – 2005.

ELAG Matei: PML8 PML: "design principles" P1: a data model based on FRBR & CRM, i.e. accommodating library and museum resources; P2: to observe the three (extra) functional requirements for the shared catalogues; P3: to enhance the (lexicographic and chronologic) browsing of the access points; P4: to make the simple easy and the complex possible (corollary: to accommodate a scalable granularity of data); P5: descriptions could include "elements not required for the stated objectives" (i.e. only half of Svenonius' "Principle of sufficiency and necessity").

ELAG Matei: PML9 two (contradictory) ambitions a)to have specific elements for the frequent resources (e.g. books, articles, paintings, coins), but also generic ones, for the many, less frequent types of resources (e.g. artifact) – a new element is imposed by the specific mixture of the resource's properties; b)to come up with an elegant language (i.e. with economy of means). a) much easier than b) !

ELAG Matei: PML10 PML: outline (the catalog)

ELAG Matei: PML11 PML: outline (the vocabulary) engleză English română Romanian

ELAG Matei: PML12 PML: a sample Gellu Naum Zenobia Humanitas Bucureşti Bucureşti Romanian p1 author

ELAG Matei: PML13 PML: a sample (cont.) Gellu Naum Romanian poet and playwright

ELAG Matei: PML14 PML: updates ancien nouveau en francais in English

ELAG Matei: PML15 Abstractions

ELAG Matei: PML16 Items

ELAG Matei: PML17 The index: problems (1)

ELAG Matei: PML18 The index: problems (2)

ELAG Matei: PML19 The index: problems (3)

ELAG Matei: PML20 The index: keys 1.alphaKey1 2.alphaKey1Type 3.numKey1 4.dateKey1 5.dateKey1Precision 6.alphaKey2 7.numKey2 8.dateKey2 9.dateKey2Precision

ELAG Matei: PML21 The index: keys types/ranks Terms1xx Temporal entities2xx Places3xx Corporate bodies4xx Persons5xx Titles6xx

ELAG Matei: PML22 The index: date precision ante, i.e. <-3 non post, i.e. <=-2 circa, i.e. ~ exact, i.e. =0 non ante, i.e. >=1 post, i.e. >2

ELAG Matei: PML23 PML-based database: a suggestion Tables: –resources: guid, XML document; –relations; guid, sourceId, targetId, XML document; –index: keys

ELAG Matei: PML24 Doubts and open problems how to handle multiple views (interfaces) ? how to handle an "original", i.e. an object which is work, expression, manifestation and item (e.g. Mona Lisa) ? how to handle a concept which is also an UDC class (e.g. 'hysteria') ? it is a sound approach ?