Extensible Metadata Repository for Information Systems - RUN UNL ...

More documents

Recommendations

Info

Abstract Information Systems are, usually, systems that have a strong integration component and some of those systems rely on integration solutions that are based on metadata (data that describes data). In that situation, there’s a need to deal with metadata as if it were “normal” information. For that matter, the existence of a metadata repository that deals with the integrity, storage, validity and eases the processes of information integration in the information system is a wise choice. There are several metadata repositories available in the market, but none of them is prepared to deal with the needs of information systems or is generic enough to deal with the multitude of situations/domains of information and with the necessary integration features. In the SESS project (an European Space Agency project), a generic metadata repository was developed, based on XML technologies. This repository provided the tools for information integration, validity, storage, share, import, as well as system and data integration, but it required the use of fix syntactic rules that were stored in the content of the XML files. This situation causes severe problems when trying to import documents from external data sources (sources unaware of these syntactic rules). In this thesis a metadata repository that provided the same mechanisms of storage, integrity, validity, etc, but is specially focused on easy integration of metadata from any type of external source (in XML format) and provides an environment that simplifies the reuse of already existing types of metadata to build new types of metadata, all this without having to modify the documents it stores was developed. The repository stores XML documents (known as Instances), which are instances of a Concept, that Concept defines a XML structure that validates its Instances. To deal with reuse, a special unit named Fragment, which allows defining a XML structure (which can be created by composing other Fragments) that can be reused by Concepts when defining their own structure. Elements of the repository (Instances, Concepts and Fragment) have an identifier based on (and compatible with) URIs, named Metadata Repository Identifier (MRI). Those identifiers, as well as management information (including relations) are managed by the repository, without the need to use fix syntactic rules, easing integration. A set of tests using documents from the SESS project and from software-house ITDS was used to successfully validate the repository against the thesis objectives of easy integration and promotion of reuse.
Page 1: Universidade Nova de Lisboa Faculda
Page 7: Agradecimentos Quero agradecer a to
Page 10 and 11: 4.1. Metadata Repository Identifier
Page 12 and 13: Figure Index Figure 1.1 SESS projec
Page 14 and 15: Figure 6.4 Graph of captured relati
Page 17: Chapter 1 Introduction This chapter
Page 20 and 21: specification is stored as metadata
Page 22 and 23: meta-models. models. In the context
Page 25 and 26: Chapter 2 State of the Art This cha
Page 27 and 28: Metadata eases the search for infor
Page 29 and 30: spread in the market, as there are
Page 31 and 32: is, as of August 2008, a W3C candid
Page 33 and 34: Finally, the “Trust” layer is u
Page 35 and 36: In RDF, each predicate must be asso
Page 37 and 38: properties (transitivity, symmetry)
Page 39 and 40: OWA models well several normal infe
Page 41 and 42: objects (resources) and can share t
Page 43 and 44: instances of the ontology that are
Page 45 and 46: 2.4.4. Fedora The Fedora project is
Page 47 and 48: Fedora is primarily rily a document
Page 49 and 50: Figure 2.12 Instance processing and
Page 51 and 52: Schematron file (and thus if the Sc
Page 53: assists in the several phases (anal
Page 57 and 58:
This chapter introduces the design
Page 59 and 60:
communications, and is very easy to
Page 61 and 62:
3.5.1. Instance Versions Instances
Page 63 and 64:
Figure 3.8 Relation between two Ins
Page 65 and 66:
Figure 3.11 M1 Layer, Instances wit
Page 67 and 68:
• XSLT • Relations • Metadata
Page 69 and 70:
In Figure 3.14, Concept A allows re
Page 71 and 72:
Chapter 4 Functional Design This ch
Page 73 and 74:
Using the previous MRI example, ver
Page 75 and 76:
Figure 4.2 Fragment definition The
Page 77 and 78:
In the previous figure, there are t
Page 79 and 80:
Figure 4.8 Correspondence of a Frag
Page 81 and 82:
Figure 4.12 XSL code used in elemen
Page 83 and 84:
The XPath can contain namespace pre
Page 85 and 86:
Figure 4.20 Schematron element with
Page 87 and 88:
The general syntax of a Relations e
Page 89 and 90:
The LocalInstanceXPath element is w
Page 91 and 92:
Automatic relations based on MRIs h
Page 93 and 94:
eplaced). If the namespace exists a
Page 95 and 96:
• Block Update • Break Relation
Page 97 and 98:
Metadata Transforming allows the tr
Page 99 and 100:
A user defining a XSLT to process I
Page 101:
The process of building the Generic
Page 104 and 105:
This chapter describes the implemen
Page 106 and 107:
5.3. Choice for the Underlying Data
Page 108 and 109:
Sedna’s storage of XML documents,
Page 110 and 111:
Several studies around the performa
Page 112 and 113:
For this test, the X-Mark queries w
Page 114 and 115:
Query 8 - Analysis Query 8 is a que
Page 116 and 117:
eXist results Table 5.4 eXist XML D
Page 118 and 119:
The Concept storage model features
Page 120 and 121:
When, after that, a second Instance
Page 122 and 123:
Figure 5.12 ConceptList.xml structu
Page 124 and 125:
Each Fragment defines a XML structu
Page 126 and 127:
Instance Identification Information
Page 128 and 129:
Stored in the repository are two In
Page 130 and 131:
mdr:getRelations(MRI) function is r
Page 132 and 133:
Table 5.7 Implementation status of
Page 135 and 136:
Chapter 6 Validation This chapter p
Page 137 and 138:
S/C Event Types of temporal occurre
Page 139 and 140:
The example will feature the Spacec
Page 141 and 142:
Figure 6.4 Graph of captured relati
Page 143 and 144:
Each Fragment’s structure was def
Page 145 and 146:
Figure 6.8 Result of converting a C
Page 147:
Figure 6.10 xeoModel relation defin
Page 150 and 151:
This chapter draws final conclusion
Page 152 and 153:
order to achieve a higher degree of
Page 154 and 155:
30. XMLSpy, A. XML editor for model
Page 156 and 157:
90. What is protégé-frames? A Pro
show all

Extensible Metadata Repository for Information Systems - RUN UNL ...

Create successful ePaper yourself

Delete template?

Save as template?