<제 3장 메타데이터>

★ 72

DC-dot: Dublin Core metadata editor

- Andy Powell이 created하였고 UKLON에서 maintained 한다.

- 이 서비스는 웹 페이지를 검색하여 그 웹페이지의 <head> ... </head>섹션에 embedding 하기 적합하도록, HTML <meta> tags나 RDF/XML로, 자동적으로 Dublin Core metadata를 생산하는 서비스이다.

-  생산된 메타데이터는 다양한 포맷으로 변형하거나 제공할 수 있도록 편집될 수 있다( USMARC, SOIF, IAFA/ROADS, TEI headers, GILS, IMS or RDF

)

= SOIF:

= IAFA/ROADS

- ROAD templates는 ROADS 소프트웨어를 사용하는 the subjects services에 의해 사용된다.

- 이 템플릿들은 1994년의 the Internet Anonymous FTP Archive(IAFA) templates를 발전시킨 것이다. Dublin Core를 이들 템플릿으로 mapping하는 것은 메타데이터 타입들 사이에 교환가능한 포맷으로 사용하려는 Dublin Core의 잠재적 역할에 대하여 관심을 갖고 조사하도록 한다.

= TEI headers: Text Encoding Initiative

- 디지털 형태로된 텍스트의 표현을 위한 표준을 collectively하게 개발하고 유지관리하기 위한 a consortium.

- 주요 목적은 인문학, 사회과학, 그리고 언어학에 초점을 맞추어 기계가독형 텍스트를 encoding하는 방법을 규정하는 Electronic Text Encoding and Interchange를 위한 가이드라인의 제공

- 모든 TEI-conformant text에 prefixed된 전자 타이틀 페이지를 만드는 descritptive and declarative information을 제공한다.

= GILS:Global Information Locator Service

- 사람들이 자신이 필요로 하는 모든 정보를 보다 쉽게 찾도록 하는 서비스

- 도서관 이용 경험이 있는 사람이면 누구나 이 서비스를 이용할 수 있으며, ISO 23950 search standard를 근거로, title, author, publish, date and place와 같은 도서관의 개념을 도입하여 전세계 누구나 정보자원을 찾는데 가장 쉽게 이해할 수 있는 개념을 포함하고 있다. GILS record는 도서관의 목록 레코드의 일종의 souped-up version 이다.

= IMS: IP Multimedia Subsystem or IP Multimedia Core Network subsystem

- Internet Protocal(IP) multimedia services를 delivering하기 위한 an architectural framework이다.

- 3세대 이동통신망의 IP 멀티미디어 서비스를 위하여 개발된 기술.

= RDF: Resource Description Framework

- The Resource Description Framework (RDF) is a W3C standard for describing Web resources, such as the title, author, modification date, content, and copyright information of a Web page.

- RDF is a standard model for data interchange on the Web.

- RDF has features that facilitate data merging even if the underlying schemas differ, and it specifically supports the evolution of schemas over time without requiring all the data consumers to be changed.

- RDF extends the linking structure of the Web to use URIs to name the relationship between things as well as the two ends of the link (this is usually referred to as a “triple”).

- Using this simple model, it allows structured and semi-structured data to be mixed, exposed, and shared across different applications.

- What is RDF?

•RDF stands for Resource Description Framework

•RDF is a framework for describing resources on the web

•RDF is designed to be read and understood by computers

•RDF is not designed for being displayed to people

•RDF is written in XML

•RDF is a part of the W3C's Semantic Web Activity

•RDF is a W3C Recommendation

- RDF-- Examples of Use

•Describing properties for shopping items, such as price and availability

•Describing time schedules for web events

•Describing information about web pages (content, author, created and modified date)

•Describing content and rating for web pictures

•Describing content for search engines

•Describing electronic libraries

= PDF: Portable Document Format

- 사용자가 보거나 탐색하거나 프린트하거나 또는 다른 사람에게 전달할 수 있도록 만들어진 이미지로서 프린트 출력된 문성의 모든 요소를 갖추고 있는 파일 형식이다(Adobe Reader)

= TIFF(Tag Image File Format)

- 이미지 저장 포맷으로 사용자가 고쳐서 쓸 수 있는 유연함이 특징이며, 1980년대 스캐너 제조사들이 일반적인 파일 형식을 사용하기 위하여 개발되었다. 확장자가 .tiff 나 .tif이다.

파일포맷 종류는 raster image(bit map style)이다.

도서관 2.0

-  라이브러리 2.0은 도서관이 오랫동안 추구해 온 이용자 중심의 서비스 제공을 위해서 참여, 공유, 개방, 소통을 모토로 하는 웹 2.0의 개념과 기술을 도서관에 접목한 개념이다. 2005년 Micheal Casey에 의해 처음으로 언급되었으며 이용자 위주의 서비스로 변화하고 있는 도서관의 트렌드를 반영하고 있다고 할 수 있다.

- 장점:

1. 정보 공유의 플랫폼으로서의 도서관

2. 학술,연구 커뮤니티의 중심으로서의 도서관

3. 개인별 맞춤 다이어리로서의 도서관 -SDI서비스, AJAX(Asynchronous JavaScript and XML, 아이아스: 대화식 웹 애플리케이션의 제작을 위해 아래와 같은 조합을 이용하는 웹 개발 기법이다 = 표현정보를 위한 HTML or XHTML과 CSS, 동적 화면출력 및 표시정보와의 상호작용을 위한 DOM, JavaScript, 웹서버와 비동기적으로 데이터를 교환하고 조작하기 위한 XML, XSLT, XMLHttpRequest)나 RSS feed(RDF Site Summary) Feed

4. 이용자와 소통하는 도서관 -  온라인 참고서비스( 실시간 메신저, 게시판, 이메일,

전화, SMS, PDA 등 다양한 커뮤니케이션 매체를 통해 가능)

5. 정보 활용 능력을 교육하는 도서관 - 온라인 튜토리얼을 통해 이용자의 정보활용능력

을 향상.

★ 74

MODS(Metadata Object Description Schema, Library of Congress)

-  The Library of Congress' Network Development and MARC Standards Office, with interested experts, developed the Metadata Object Description Schema (MODS) in 2002 for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications. As an XML schema it is intended to be able to carry selected data from existing MARC 21 records as well as to enable the creation of original resource description records. It includes a subset of MARC fields and uses language-based tags rather than numeric ones, in some cases regrouping elements from the MARC 21 bibliographic format. As of June 2009 this schema is in its third version (version 3.3). MODS is expressed using the XML schema language of the World Wide Web Consortium. The standard is maintained by the MODS Editorial Committee with support from the Network Development and MARC Standards Office of the Library of Congress .

MOA2 DTD

-  The Making of America II Testbed Project attempted to address many of these issues surrounding metadata for digital library objects through the development of a well-documented set of metadata elements needed for digital object management. This metadata set achieved its technological expression through an XML document type definition, the MOA2 DTD. While providing an excellent starting point for discussions around digital object metadata, the MOA2 DTD was only designed to allow for the encoding of a limited range of digital objects, including diaries, still images, ledgers, and letterpress books. As the DTD has been more widely applied, the limitations of its original design have become more apparent. The DTD as it stands lacks adequate provisions for encoding of descriptive metadata, only supports technical metadata for a narrow range of text- and image-based resources, provides no support for audio, video, and other time dependent media, and provides only very minimal internal and external linking facilities.

- Despite its shortcomings, the MOA2 DTD represents a significant step towards developing both a standard set of data elements for describing and managing digital library objects, and a technological mechanism for expressing that information. This workshop will provide an opportunity to build on and extend the MOA2 DTD to allow it to support a wider range of digital library objects and operations, and to discuss what further steps might be taken to further develop and maintain the DTD in the future.

-  consider a survey related standards work that might be incorporated into or influence a revised MOA2 DTD, including (Dublin Core, USMARC, Encoded Archival Description, Indecs Metadata Framework, VRA Core, NISO Technical Metadata for Digital Still Images, Library of Congress audio/visual technical metadata, National Library of Australia Preservation Metadata for Digital Collections, Resource Description Framework, Synchronized Multimedia Integration Language, MPEG-7;

- METS로 대체됨.

기술적 메타데이터(Technical Metadata)

- Technical metadata is used for recording the technical attributes of digital objects that include their production or creation information on the digital capture process, i.e., the hardware and software used to acquire the digital object, file formats for master and derivatives, resolutions, color profiles and so on, that enable the reproduction of digital resources in the future. For this reason technical metadata is categorized as administrative and preservation metadata.

- Technical metadata can be included in preservation metadata (PREMIS) or structural metadata (METS). The decision regarding where to add the technical metadata can be made based on the types of technical metadata that should be preserved since METS and PREMIS have different ways of incorporating technical metadata in its schema.

보존용 메타데이터(PREMIS)

- In June 2003, OCLC and RLG jointly sponsored the formation of the PREMIS (Preservation Metadata: Implementation Strategies) working group, comprised of international experts in the use of metadata to support digital preservation activities.

- The working group’'s membership included more than 30 participants, representing five different countries and a variety of domains, including libraries, museums, archives, government agencies, and the private sector.

- the working group’'s charge was to develop a core set of implementable preservation metadata, broadly applicable across a wide range of digital preservation contexts and supported by guidelines and recommendations for creation, management, and use.

★ 78

EAD(Encoded Archival Description)

- Development of the EAD DTD began with a project initiated by the University of California, Berkeley, Library in 1993. The goal of the Berkeley project was to investigate the desirability and feasibility of developing a nonproprietary encoding standard for machine-readable finding aids such as inventories, registers, indexes, and other documents created by archives, libraries, museums, and manuscript repositories to support the use of their holdings. The project directors recognized the growing role of networks in accessing information about holdings, and they were keen to include information beyond that which was provided by traditional machine-readable cataloging (MARC) records. The development of the EAD DTD was a cooperative venture from early on, with specialists at Berkeley working in consultation with experts at other institutions. Daniel Pitti, the principal investigator for the Berkeley Project, developed requirements for the encoding standard which included the following criteria: 1) ability to present extensive and interrelated descriptive information found in archival finding aids, 2) ability to preserve the hierarchical relationships existing between levels of description, 3) ability to represent descriptive information that is inherited by one hierarchical level from another, 4) ability to move within a hierarchical informational structure, and 5) support for element-specific indexing and retrieval.

★85

DOI

- A digital object identifier (DOI) is a character string (a "digital identifier") used to uniquely identify an object such as an electronic document. Metadata about the object is stored in association with the DOI name and this metadata may include a location, such as a URL, where the object can be found. The DOI for a document is permanent, whereas its location and other metadata may change. Referring to an online document by its DOI provides more stable linking than simply referring to it by its URL, because if its URL changes, the publisher need only update the metadata for the DOI to link to the new URL.

- Organizations that meet the contractual obligations of the DOI system and are willing to pay to become a member of the system can assign DOIs. The DOI system is implemented through a federation of registration agencies coordinated by the International DOI Foundation, which developed and controls the system. The DOI system has been developed and implemented in a range of publishing applications since 2000; by late April 2011 more than 50 million DOI names had been assigned by some 4,000 organizations. The DOI system is part of the larger Handle System.

- A DOI name takes the form of a character string divided into two parts, a prefix and a suffix, separated by a forward slash. The prefix identifies the registrant of the name, and the suffix is chosen by the registrant and identifies the specific object associated with that DOI. Most legal Unicode characters are allowed in these strings, which are interpreted in a case-insensitive manner.

- For example, in the DOI name 10.1000/182, the prefix is 10.1000 and the suffix is 182. The "10." part of the prefix identifies the DOI registry and the characters 1000 in the prefix identify the registrant; in this case the registrant is the International DOI Foundation itself. 182 is the suffix, or item ID, identifying a single object (in this case, the latest version of the DOI Handbook). Citations using DOI names should be printed as doi:10.1000/182. When the citation is a hypertext link, it is recommended to embed the link as a URL by concatenating "http://dx.doi.org/" to the DOI name, omitting its "doi:" prefix; e.g., the DOI name doi:10.1000/182 is linked as http://dx.doi.org/10.1000/182. This URL provides the location of an HTTP proxy server which will redirect web accesses to the correct online location of the linked item.

- DOI names can identify creative works (such as texts, images, audio or video items, and software) in both electronic and physical forms, performances, and abstract works[10] such as licenses, parties to a transaction, etc. The names can refer to objects at varying levels of detail: thus DOI names can identify a journal, an individual issue of a journal, an individual article in the journal, or a single table in that article. The choice of level of detail is left to the assigner, but in the DOI system it must be declared as part of the metadata that is associated to a DOI name, using a data dictionary based on the indecs Content Model.