Perfil de aplicação.

Apresentação em tema: "Perfil de aplicação."— Transcrição da apresentação:

1 Perfil de aplicação

2 Schema A Schema B Schema C Perfil de aplicação -- como aqueles esquemas que contém elementos de dados desenhados de um ou mais namespaces* -- Nunca take it or leave it, sempre take what you want, create what you need Application Profile Even within a particular information community, there are different user requirements and special local needs. The details provided in a particular schema may not meet the needs of all user groups. Therefore, based on the notion that metadata standards are necessarily localized and optimized for specific contents, the concept of "application profiles", a typical approach to accommodating individual needs, emerged (Johnston, 2003). While a particular existing schema or schemas are used as the basis for description in a particular digital library or repository, individual needs are met through a set of specific application guidelines or policies established for a particular interest or user group. An application profile selects elements from one or more namespaces schemas. * para definir o contexto de um termo em particular, garantindo assim que o termo tenha uma definição única nos limites do namespace declarado. (Duval et al., 2002)

3 Perfis de aplicação definições básicas
Um perfil de aplicação (PA) é um relatório onde os termos são utilizados por uma organização, um recurso informacional, uma aplicação ou uma comunidade de usuário para o metadado. --Baker, 2003 for Dublin Core Metadata Initiative (DCMI) Usage Board). Um perfil de aplicação é uma reunião de elementos dos metadados selecionados de um ou mais esquemas de metadados e combinados em um esquema composto. -- Duval, E., et al. Metadata Principles and Practicalities D-Lib Magazine, April 2002

4 Application profiles usually consist of metadata elements drawn from one or more metadata schemas (see Figure 3), combined into a compound schema by implementors, and optimized for a particular local application (Heery and Patel, 2000; Duval et al., 2002). For example, the Australasian Virtual Engineering Library's AVEL Metadata Set consists of nineteen elements. In addition to supporting 14 DC elements (excluding dc.source element), it also supports one AGLS (Australian Government Locator Service) metadata element (AGLS.Availability), one EDNA (Education Network Australia) element (EdNA.Review), and three Administrative elements (AC.Creator, AC.DateCreated, and AVEL.Comments).

5 AVEL METADATA ELEMENT LIST
Dublin Core elements supported by AVEL DC.Identifier DC.Title DC.Creator DC.Subject DC.Description DC.Publisher DC.Contributor DC.Date DC.Type DC.Format DC.Language DC.Coverage DC.Relation DC.Rights AGLS elements supported by AVEL AGLS.Availability EDNA elements supported by AVEL EdNA.Review Application profiles usually consist of metadata elements drawn from one or more metadata schemas (see Figure 3), combined into a compound schema by implementors, and optimized for a particular local application (Heery and Patel, 2000; Duval et al., 2002). For example, the Australasian Virtual Engineering Library's AVEL Metadata Set consists of nineteen elements. In addition to supporting 14 DC elements (excluding dc.source element), it also supports one AGLS (Australian Government Locator Service) metadata element (AGLS.Availability), one EDNA (Education Network Australia) element (EdNA.Review), and three Administrative elements (AC.Creator, AC.DateCreated, and AVEL.Comments). Administrative elements supported by AVEL AC.Creator AC.DateCreated AVEL.Comments

6

7 Projeto dos perfis de aplicação
Selecionar o namespace da “base” de metadados Selecionar os elementos de outros namespaces de metadados Definir elementos dos metadados locais Impor a aplicação dos elementos Imposição fundamental Restrição do espaço para o valor Especificação de relacionamento e dependência In practice, then, the implementation of an application profile often involves the following steps: (1) selecting a “base” metadata namespace, (2) selecting elements from other metadata namespaces, (3) defining local metadata elements and declaring new elements' namespaces, and (4) enforcing application of the elements (including cardinality enforcement, value space restriction, and relationship and dependency specification) (Zhang, 2004; Duval et al., 2002).

8 Perfis de aplicação Dublin Core
DC-Library Application Profile (DC-Lib) esclarece o uso do conjunto de elementos do metadado DC em bibliotecas e em aplicações e projetos relacionados com bibliotecas DC Government Application Profile esclarece o uso do DC no contexto governamental DC Collection Description Application Profile An application profile (AP) may also be based on one single schema but tailored to different user communities. For example, DC-Library Application Profile (DC-Lib) clarifies the use of the DC metadata element set in libraries and library-related applications and projects. The DC Government Application Profile clarifies the use of DC in a government context (Cumming et al., 2001).

9

10

11

12

13 arquivos Domínio-cruzado e arquivo de esquema-cruzado.
Por exemplo, o arquivo UKOLN (UK Office for Library Networking)'s SCHEMAS . Agora, intitulado arquivo CORES (1) Cross-domain and cross-schema registry. For example, UKOLN (UK Office for Library Networking)'s SCHEMAS Registry ( now used in the new CORES project, contains several metadata element sets and related documents. Through a web interface, one can search or browse according to agencies, element sets, elements, encoding schemes, application profiles, and element usages that are included in this registry. Currently the registry consists of 12 element sets from 10 institutions (

14 Source: CORES Registry. http://cores.dsd.sztaki.hu/
The SCHEMAS Registry maintained by the UK Office for Library and Information Networking (UKOLN) is a registry of application profiles. It contains several metadata element sets as well as a large number of activity reports which describe and comment on various metadata related activities and initiatives. Source: CORES Registry.

15 PricewaterhouseCoopers Fraunhofer Gesellschaft
(1) Cross-domain and cross-schema registry. For example, UKOLN (UK Office for Library Networking)'s SCHEMAS Registry ( now used in the new CORES project, contains several metadata element sets and related documents. Through a web interface, one can search or browse according to agencies, element sets, elements, encoding schemes, application profiles, and element usages that are included in this registry. Currently the registry consists of 12 element sets from 10 institutions ( Partners PricewaterhouseCoopers Fraunhofer Gesellschaft Computer and Automation Research Institute, Hungarian Academy of Sciences (MTA SZTAKI) UKOLN, University of Bath

16

17