xrx: the metadata registry example 21 october 2008 jeremy sutton matt steele

XRX:The Metadata Registry Example

21 October 2008Jeremy Sutton

Matt Steele

2

Introduction

Both of us work for Genesis10’s CAP program and are currently consulting at a local financial services organization.

• Jeremy Sutton– Saint John’s University 2008 – Computer Science– Technical analyst working on Metadata Registry

• Matt Steele– Saint John’s University 2008 – International Relations /

Economics– Business/data analyst working on knowledge capture and

metadata for a data warehouse– Pushing to expand the use of the Metadata Registry

3

Metadata Registry

4

Standards-based design

Concepts:• Web-based• Semantics• Enterprise

vocabulary• REST & Persistent

URIs• Tree database• Every query as a

service• XML

interoperability with other systems

5

XForms: Screen Capture

6

XForms: Advanced interface features

• AJAXy features without the mess

• “Suggest” example:

7

XForms: Easy interface development

Example: Date picker is one line of code; no javascript

needed<xf:bind nodeset="instance('my-task')/Completion-Date" type="xs:date"/>

<xf:input ref="instance('my-task')/completion-date" bind="closed”>

<xf:label>Completion Date</xf:label>

</xf:input>

8

XQuery Example: Glossary report

9

Learning experience

• Resources

XForms

XQuery

10

First CRUD (create/read/update/delete)

• Deconstructed existing project (task manager) to base components to understand the architecture

• Built a blog application• Took one week

11

Limitations

• Browser support– Plugins are needed to work with current browsers

• Firefox add-in works elegantly• Internet Explorer 6 requires Picoforms• Client-side java-based interpreters exist but are bulky

• Not widely known– Standards are new– Pushes against conventional apps, relational

databases, etc

• Limited commercial examples

12

Advantages

• Simple to learn• See results very quickly• Very powerful searching with minimal code• Does not use RDB architecture• Open XML platform for data I/O• Easily adaptable to many tool needs• Logical organization of data (hierarchies,

URIs)• Easily de-buggable• Easy web apps

Thank you!