ARHIVSKI VJESNIK 44. (ZAGREB, 2001.)

Strana - 120

J. Ivanović, Sheme metapodataka u upravljanju dokumentima, Arh. vjesn., god. 44 (2001), str. 103-121 držaj i koje kompetencije zahtijeva. O tome kako se ono definira, ovisi i koliko će, i da li će uopće ova tema o metapodacima biti relevantna za spisovodstvo. Vjerojatno su mogući različiti odgovori, no isto tako treba uzeti u obzir njihove posljedice. Summary METADATA SCHEMAS IN RECORDS MANAGEMENT Information and documents can be structured and organized in many ways, depending on the typology of information objects and their functions in the system they are contained in. In electronic systems, the structure and the organization of the content have to be indicated explicitly. With the Internet, and especially e-business applications, the attention is focused on documents, as a means for business communication and an element of business processes. Standards and technologies are developed that define formats and properties of the documents, actions, and the exchange of documents between systems in open environment. This is clearly illustrated by the development and even greater use of XML schémas and applications. Those technologies are today pretty mature, and can be implemented in the whole domain of traditional records management, by adding some functionality and determining technological and even conceptual framework of records management. Schemas are closely linked to the communication. In the open environment, schémas determine the way of communicating and exchanging the data and information, between people, institutions, and communication enabled machines. Each schema formalizes and describes some class of objects or a form of activity. What will be selected as a class of objects for a schema, and how it will be defined, depends on the 'holder' of the schema, his interests, and the functions expected from the schema. Schemas always reflect some particular perspective and understanding of the part of the world the holder of the schema is interested in. It cannot be expected that such a multi-purpose schema will be developed, that would be able to express and to encompass structures of different classes of objects, and effectively support functions of different systems. Even if it could be possible, a wider consent on a schema is not to be expected. In fact, there are more and more various schémas that are domain specific, often specific for some institution. Today, there are so many different standards, public and proprietary schémas, that the interoperability and standardization become a tough problem. Because wide implementation of unified and multi-purpose complex schémas is hardly to be expected, there is an effort to address the problem of the interoperability by specifying modular schémas and defining the rules for the interoperability. 120