Transcript No Slide Title

Ubiquitous Metainformation and the
W Y W W Y W I Principle
Michael Bieber*, Joe Catanio*, Li Zhang**
*Information Systems Department
**Computer Science Department
College of Computing Sciences
New Jersey Institute of Technology
http://web.njit.edu/~bieber
November 2003
Bieber, Catanio & Zhang, NJIT ©2003
This talk ties together much of our current research..
It also gives a vision of where the WWW is heading.
1
Thinking Exercise
• Close your eyes. Think about your favorite
Web site, or one that you rely on for
information...
• Focus on an element you’re interested in
– a text string, icon, element within a table or an
animation...
Bieber, Catanio & Zhang, NJIT ©2003
2
The W Y W W Y W I Principle
What you want, when you want it
Wanting to point to something and say:
–
–
–
–
–
–
Tell me more about this!
What is this?
How can I use this? What do I need to know to use it?
Can I modify this?
How does this differ from similar ones?
What is the next step?
This is all metainformation & people should get it!
Bieber, Catanio & Zhang, NJIT ©2003
3
Ubiquitous Metainformation
Goal: Metainformation widespread in everyday systems
How: provide tools for developers
• Relationship Analysis
– systematically determining metainformation
• Metainformation Engine
– automatically generating metainformation
• WYWWYWI
– widespread accepted design philosophy
Bieber, Catanio & Zhang, NJIT ©2003
4
Outline
•
•
•
•
•
•
•
Examples
Metainformation (what to provide)
Relationship Analysis (how to find metainformation)
Metainformation Engine (how to automate it)
Virtual Documents (many real world documents)
Related Work
WYWWYWI (what it will take)
Bieber, Catanio & Zhang, NJIT ©2003
5
Two Examples
• Purchasing System
• Digital Library
• screen shot of our prototype later...
Bieber, Catanio & Zhang, NJIT ©2003
6
251
Requisi tion H eader - Sh ippin g and Text
Screen :
Vend: V000 03043 90 PR : R010294 Inv:
Deliver -to A ddress
Name: MICHAEL B IEBER
Org:
NJIT, CIS DEPA RTMEN T
Addr: 323 ML KI NG BL VD
City: NEWARK
Zip:
07102
Phone : 973 596 2 681
STRAT EGIC SUPPL IES I NTERN 'L
71 UNION AVE
Line:
F OB:
Rte:
Deliv ery Se rvice : UPS
Deliv ery Da te: 0 3-12- 2000
St: NJ
Cou ntry: USA
Ext:
Requisi tion Codes :
58 128 PUX ZY2
Requis ition Text:
Sample Screen from Purchasing System:Documen t
All text with no links...
Bieber, Catanio & Zhang, NJIT ©2003
Notes: N
7
251
Requi sitio n Head er - Shipp ing a nd Te xt
Screen:
Vend: V000030 4390 PR: R010294 Inv:
Deliver -to A ddress
Name: MICHAEL BIEB ER
Org:
NJIT, C IS DE PARTME NT
Addr: 323 ML KING BLVD
City: NEWARK
Zip:
07102
Phone: 973 596 2681
STRATEG IC SU PPLIES INTE RN'L
71 UNION AVE
Line:
FOB:
Rte:
Deliver y Service: UPS
Deliver y Date: 03-12-2 000
St: NJ
Country : USA
Ext:
Requisi tion Codes :
58 128 PUX ZY2
Requisi tion Text:
But we could want metainformation
about almost any element...
Bieber, Catanio & Zhang, NJIT ©2003
Documen t Notes: N
8
251
Requi sitio n Head er - Shipp ing a nd Te xt
Screen:
Vend: V000030 4390 PR: R010294 Inv:
STRATEG IC SU PPLIES INTE RN'L
71 UNION AVE
Line:
V0000304390 {vendor}
Deliver -to A ddress
FOB:
Name: MICHAEL BIEB ER
Rte:
Vendor
Details
Org:
NJIT, C IS DE PARTME NT
Deliver y Service: UPS
{Vendor IS}
Addr: 323 ML KING BLVD
Deliver y Date: 03-12-2 000
Vendor Reliability
{Vendor IS}
City: NEWARK
St: NJ
Zip:
07102
Country
: USA
Vendor
Agreements
Phone: 973 596 2681
{VendorExt:
IS}
Requisi tion
Other Possible Vendors 58 128 PUX
Requisi tion Text:
{Purchasing Data Warehouse}
Your Purchasing History
{Purchasing IS}
All Screens with this Vendor
{CASE Workbench}
Codes :
ZY2
Documen t Notes: N
Bieber, Catanio & Zhang, NJIT ©2003
9
i
Here are some examples. The agricultural system is very
complex. It consistsof f armers in interaction w ith the envi
ronment (w eather, soil, pests), the economy
and society.
Deeply Underst
anding Complexit y
One problem currently receiving a lot of{document
attention
} is
Integrated Pest Management.
View
Peer
Review
Comments
Author
and
Document
Owner
{JESSE
Peer
Revi ew ser vice}
{Metadata
Repository}
The problem unf ortunately is being addressed separately
Enter Agronomy,
your own Peer Review
by experts in Plant Pathology, Entomology,
Bot
- Comment
{JESSEground
Peer Revi ew
ser vice}
any, and Soil Science, w ith no real common
(and
-lit
tle common understanding) to base ourSearch
decisions
on.el ated documents
for similar/r
Plant Pathology {concept }
Meetings and w orkshops tasked w ith integration
{Core Search service}
have taken
place, but these varioussubdisciplines could not seem to
Ask an exper t about this concept
Other collections with this document
orm
an Reference
integrated
view point. No real methodology
exists
{i nfthe
Virtual
Desk}
{DLSI Collection Registr y}
to discuss and analyze the systems, w hich each
Rel evant NASA Experiments i n Space
Create
a newdecisions
comment on document
subdiscipline has developed. In the end,
all IPM
{ Nati onal Space Science Data Center}
Annotati on service}
end up unintegrated and therefore only{Core
partially
ef fective. A
Relsystematic
ated jour nal artiapproach
cles
that w ould enableAdd
the
diff erent
document
to currpartici
ent Guided
Tour
{i npants
JESSE} to discuss, and determine all the {DLSI
interrelationships,
Guided Tour ser vi ce}
w hichthis
w concept
ould help researchers link their practices and derive
Search
Define for
this concept
Star t your own link from this document
their
ef
fects
on
each
others
area
and
the
environment,
{Core
Search
service}
{Agricultural Thesaurus}
{DLSI
Link servi ce}
Bieber, Catanio &w
Zhang,
NJIT
©2003
ould greatly help theIPM research and lead to better deci
10
View Comments on this concept
Metainformation
• The full
context about
and around an
element
relationships
metadata
element
• Provides a
fuller
understanding
Bieber, Catanio & Zhang, NJIT ©2003
11
Metainformation
• metadata (about selected element)
• content relationships (based on display content)
• structural relationships (based on element type or “class”)
• annotation relationships (user-declared, knowledge-sharing)
• metainformation-based navigation (user-directed)
Roberto Galnares’
dissertation
Bieber, Catanio & Zhang, NJIT ©2003
12
i
Here are some examples. The agricultural system is very
complex. It consistsof f armers in interaction w ith the envi
ronment (w eather, soil, pests), the economy
and society.
Deeply Underst
anding Complexit y
One problem currently receiving a lot of{document
attention
} is
Integrated Pest Management.
View
Peer
Review
Comments
Author
and
Document
Owner
{JESSE
Peer
Revi ew ser vice}
{Metadata
Repository}
The problem unf ortunately is being addressed separately
Enter Agronomy,
your own Peer Review
by experts in Plant Pathology, Entomology,
Bot
- Comment
{JESSEground
Peer Revi ew
ser vice}
any, and Soil Science, w ith no real common
(and
-lit
tle common understanding) to base ourSearch
decisions
on.el ated documents
for similar/r
Plant Pathology {concept }
Meetings and w orkshops tasked w ith integration
{Core Search service}
have taken
place, but these varioussubdisciplines could not seem to
Ask an exper t about this concept
Other collections with this document
orm
an Reference
integrated
view point. No real methodology
exists
{i nfthe
Virtual
Desk}
{DLSI Collection Registr y}
to discuss and analyze the systems, w hich each
Rel evant NASA Experiments i n Space
Create
a newdecisions
comment on document
subdiscipline has developed. In the end,
all IPM
{ Nati onal Space Science Data Center}
Annotati on service}
end up unintegrated and therefore only{Core
partially
ef fective. A
Relsystematic
ated jour nal artiapproach
cles
that w ould enableAdd
the
diff erent
document
to currpartici
ent Guided
Tour
{i npants
JESSE} to discuss, and determine all the {DLSI
interrelationships,
Guided Tour ser vi ce}
w hichthis
w concept
ould help researchers link their practices and derive
Search
Define for
this concept
Star t your own link from this document
their
ef
fects
on
each
others
area
and
the
environment,
{Core
Search
service}
{Agricultural Thesaurus}
{DLSI
Link servi ce}
Bieber, Catanio &w
Zhang,
NJIT
©2003
ould greatly help theIPM research and lead to better deci
13
View Comments on this concept
i
Here are some examples. The agricultural system is very
complex. It consistsof f armers in interaction w ith the envi
ronment (w eather, soil, pests), the economy
and society.
Deeply Underst
anding Complexit y
One problem currently receiving a lot of{document
attention
} is
Integrated Pest Management.
metadata
View
Peer
Review
Comments
Author
and
Document
Owner
{JESSE
Peer
Revi ew ser vice}
{Metadata
Repository}
The problem unf ortunately is being addressed separately
Enter Agronomy,
your own Peer Review
by experts in Plant Pathology, Entomology,
Bot
- Comment
{JESSEground
Peer Revi ew
ser vice}
relationship
any,
and Soil Science, content
w ith no real
common
(and
-lit
structural
relationships
tle common understanding) to base ourSearch
decisions
on.el ated documents
for similar/r
Plant Pathology {concept }
Meetings and w orkshops tasked w ith integration
{Core Search service}
have taken
place, but these varioussubdisciplines could not seem to
Ask an exper t about this concept
Other collections with this document
orm
an Reference
integrated
view point. No real methodology
exists
{i nfthe
Virtual
Desk}
{DLSI Collection Registr y}
to discuss and analyze the systems, w hich each
Rel evant NASA Experiments i n Space
Create
a newdecisions
comment on document
subdiscipline has developed. In the end,
all IPM
{ Nati onal Space Science Data Center}
Annotati on service}
end up unintegrated and therefore only{Core
partially
ef fective. A
Relsystematic
ated jour nal artiapproach
cles
that w ould enableAdd
the
diff erent
document
to currpartici
ent Guided
Tour
annotation
{i npants
JESSE} to discuss, and determine all the {DLSI
interrelationships,
Guided Tour ser vi ce}
w hichthis
w concept
ould help researchers link their practices and derive
Search
Define for
this concept
Star t your own link from this document
their
ef
fects
on
each
others
area
and
the
environment,
{Core
Search
service}
{Agricultural Thesaurus}
{DLSI
Link servi ce}
content
relationship
Bieber, Catanio &w
Zhang,
NJIT
©2003
ould greatly help theIPM research and lead to better deci
14
View Comments on this concept
251
Requi sitio n Head er - Shipp ing a nd Te xt
Screen:
Vend: V000030 4390 PR: R010294 Inv:
STRATEG IC SU PPLIES INTE RN'L
71 UNION AVE
Line:
all are structural
relationships
V0000304390 {vendor}
Deliver -to A ddress
FOB:
Name: MICHAEL BIEB ER
Rte:
Vendor
Details
Org:
NJIT, C IS DE PARTME NT
Deliver y Service: UPS
{Vendor IS}
Addr: 323 ML KING BLVD
Deliver y Date: 03-12-2 000
Vendor Reliability
{Vendor IS}
City: NEWARK
St: NJ
Zip:
07102
Country
: USA
Vendor
Agreements
Phone: 973 596 2681
{VendorExt:
IS}
Requisi tion
Other Possible Vendors 58 128 PUX
Requisi tion Text:
{Purchasing Data Warehouse}
Your Purchasing History
{Purchasing IS}
All Screens with this Vendor
{CASE Workbench}
Codes :
ZY2
Documen t Notes: N
Bieber, Catanio & Zhang, NJIT ©2003
15
Outline
•
•
•
•
•
•
•
Examples
Metainformation (what to provide)
Relationship Analysis (how to find metainformation)
Metainformation Engine (how to automate it)
Virtual Documents (many real world documents)
Related Work
WYWWYWI (what it will take)
Bieber, Catanio & Zhang, NJIT ©2003
16
Relationship Analysis (RA)
• What metainformation could we provide?
• RA: a systematic methodology to determine
relationships (& metadata and new destination elements)
–
–
–
–
–
New systems analysis technique
Fills a major hole in software engineering
Analysts gain deeper understanding of a system
Yields richer analyses and designs
Joe Catanio’s
Relationships become links
dissertation
Bieber, Catanio & Zhang, NJIT ©2003
17
Relationship Analysis (RA), cont.
• approach: brainstorming with domain experts
• for existing systems:
– pick elements from screen shots
• for new systems:
– pick entities from use cases
• Ask questions from RA taxonomy
Bieber, Catanio & Zhang, NJIT ©2003
18
RA Taxonomy
• based on Guilford’s Structure of Intellect
theory [1950]
– describing intellect and creativity
• refined by Rao & Turoff’s Hypertext
Morphology [1991]
– for systems analysis
Bieber, Catanio & Zhang, NJIT ©2003
19
RA Taxonomy
Item of Interest
Bieber, Catanio & Zhang, NJIT ©2003
Definition
Specification
Elaboration
Collection
Membership
Aggregation
Proposition
Association
Characteristic
Generalization
Path
Branch
Issue
Alternative
Deviation
Observation
Inference
Extrapolation
20
RA Taxonomy
Item of Interest
Bieber, Catanio & Zhang, NJIT ©2003
Definition
Specification
Elaboration
Collection
Membership
Aggregation
Proposition
Association
Characteristic
Generalization
Path
Branch
Issue
Alternative
Deviation
Observation
Inference
Extrapolation
21
RA: Brainstorming Questions
Item of Interest
Description
Node Type
Convergent
Relationship
Type
Generic Question(s)
(Optional)
Specific Question(s)
Results
Divergent
Relationship
Type
Generic Question(s)
(Optional)
Specific Question(s)
Bieber, Catanio & Zhang, NJIT ©2003
Results
Definition
Specification
RA Template
Does the item of interest have a description?
Does the item of interest have a definition?
Does the item of interest have an explanation?
Does the item of interest have a set of instructions?
Does the item of interest have an illustration?
Elaboration
Does the description fully describe the item of interest?
Does the definition fully encompass the item of interest?
Does the explanation make assumptions?
Are the set of instructions complete?
22
Outline
•
•
•
•
•
•
•
Examples
Metainformation (what to provide)
Relationship Analysis (how to find metainformation)
Metainformation Engine (how to automate it)
Virtual Documents (many real world documents)
Related Work
WYWWYWI (what it will take)
Bieber, Catanio & Zhang, NJIT ©2003
23
Metainformation Engine
• “Just in time” metainformation
– required for virtual documents (e.g., query results)
• Automatically:
– generates link anchors
– generates links to services providing
metainformation:
• metadata, content, structural, annotation relationships
– incorporates metainformation-based navigation
• Provides lightweight systems integration
through linking to everyday systems
Bieber, Catanio & Zhang, NJIT ©2003
Roberto Galnares’
dissertation
24
251
Requi sitio n Head er - Shipp ing a nd Te xt
Screen:
Vend: V000030 4390 PR: R010294 Inv:
STRATEG IC SU PPLIES INTE RN'L
71 UNION AVE
Line:
V0000304390 {vendor}
Deliver -to A ddress
FOB:
Name: MICHAEL BIEB ER
Rte:
Vendor
Details
Org:
NJIT, C IS DE PARTME NT
Deliver y Service: UPS
{Vendor IS}
Addr: 323 ML KING BLVD
Deliver y Date: 03-12-2 000
Vendor Reliability
{Vendor IS}
City: NEWARK
St: NJ
Zip:
07102
Country
: USA
Vendor
Agreements
Phone: 973 596 2681
{VendorExt:
IS}
Requisi tion
Other Possible Vendors 58 128 PUX
Requisi tion Text:
{Purchasing Data Warehouse}
Your Purchasing History
{Purchasing IS}
All Screens with this Vendor
{CASE Workbench}
Codes :
ZY2
Documen t Notes: N
Bieber, Catanio & Zhang, NJIT ©2003
25
To Integrate:
(1) wrapper: parses screens to identify elements
(2) provide metadata/structural rel’ship rules
(3) identify glossaries for content relationships
User’s Web
Browser
Metainformation
Engine
ME Desktop
ME Broker
ME Relationship
Engine
ME Lexical
Analysis
Vendor IS
Wrapper
Purchasing
D.W.
Wrapper
Purchasing
IS Wrapper
CASE
Workbench
Wrapper
Service
Wrapper (i)
Vendor
Information
System
Purchasing
Data
Warehouse
Purchasing
Information
System
CASE
Workbench
Service (i)
Bieber, Catanio & Zhang, NJIT ©2003
existing system
or Web service
uses
Java,
XML,
Xpath,
etc.
26
To Integrate:
(1) wrapper: parses screens to identify elements
(2) provide metadata/structural rel’ship rules
(3) identify glossaries for content relationships
User’s Web
Browser
Metainformation
Engine
ME Desktop
ME Broker
ME Relationship
Engine
ME Lexical
Analysis
Vendor IS
Wrapper
Purchasing
D.W.
Wrapper
Purchasing
IS Wrapper
CASE
Workbench
Wrapper
Service
Wrapper (i)
Vendor
Information
System
Purchasing
Data
Warehouse
Purchasing
Information
System
CASE
Workbench
Service (i)
Bieber, Catanio & Zhang, NJIT ©2003
existing system
or Web service
uses
Java,
XML,
Xpath,
etc.
27
Relationship Rules
•
•
•
•
•
V0000304390 {vendor}
Vendor Details
{Vendor IS}
element type (“vendor”)
Vendor Reliability
link display label (“Vendor Details”)
{Vendor IS}
Agreements
relationship metadata for filteringVendor
links
{Vendor IS}
Other Possible Vendors
– semantic relationship type (“elaboration”)
{Purchasing Data Warehouse}
– relationship keywords
Your Purchasing History
{Purchasing IS}
destination system (“Vendor Info System”)
All Screens with this Vendor
Workbench}
exact command(s) for destination{CASE
system
(“retrieve_full(ID, details)”)
• conditions
– user types and tasks, expertise required, access restrictions
Bieber, Catanio & Zhang, NJIT ©2003
28
Relationship Rules
• Mechanism for implementing access to:
–
–
–
–
–
Metadata
Structural relationships
Content relationships
Annotation relationships
Metainformation navigation
Bieber, Catanio & Zhang, NJIT ©2003
29
Metadatum Rule
• element type ( “vendor”)
• metadatum link display label (“Vendor Name”)
• metadatum’s metadata for filtering links
– semantic relationship type (“name”)
– metadatum keywords
• destination system (“Vendor Info System”)
• exact command(s) for destination system
(“select(vendor_table, vendor_ID, vendor_name)”)
• conditions
– user types and tasks, expertise required, access restrictions
Bieber, Catanio & Zhang, NJIT ©2003
30
Annotation Rule
(display comments)
• element type ( “generic_element”)
• link display label
(“view comments on this”, element_type)”)
• relationship metadata for filtering links
– semantic relationship type (“annotation”)
• destination system (“Annotation System”)
• exact command(s) for destination system
(“display_annotations(element_ID)”)
• conditions
check_condition(“Core Annotation Service”,
existence_check(“annotations”, element_ID)) = true)
Bieber, Catanio & Zhang, NJIT ©2003
31
Prototype:
Digital Library Integration
Bieber, Catanio & Zhang, NJIT ©2003
32
Interesting Issues
• Information overload!
– Must filter and rank order list of links
– Too many anchors
– Requires good user interface design
• Semantics
– Systems/services should use same element types
• Unique persistent identifiers
– For every screen, document, element of interest
Bieber, Catanio & Zhang, NJIT ©2003
33
Outline
•
•
•
•
•
•
•
Examples
Metainformation (what to provide)
Relationship Analysis (how to find metainformation)
Metainformation Engine (how to automate it)
Virtual Documents (many real world documents)
Related Work
WYWWYWI (what it will take)
Bieber, Catanio & Zhang, NJIT ©2003
34
Virtual Documents
• from user interaction, queries, customizations
• Metainformation must be added “just in time”
• Example
–
–
–
–
–
–
do a decision support analysis (“# vehicles needed”)
add comments to calculation results
bookmark screen (“make it a favorite”)
close screen
follow bookmark later (“system regenerates screen”)
system must re-locate comment anchors “just in time”
Bieber, Catanio & Zhang, NJIT ©2003
35
Virtual Documents
• Re-generate virtual documents
– without re-entering parameters
– then wrapper parses to add metainfo anchors
• Re-identify elements
– Location can shift
– content can change (e.g., stock price)
• Re-locate anchors
Bieber, Catanio & Zhang, NJIT ©2003
Li Zhang’s
dissertation
36
Outline
•
•
•
•
•
•
•
Examples
Metainformation (what to provide)
Relationship Analysis (how to find metainformation)
Metainformation Engine (how to automate it)
Virtual Documents (many real world documents)
Related Work
WYWWYWI (what it will take)
Bieber, Catanio & Zhang, NJIT ©2003
37
Related Work
• Web Services
• Semantic Web
• Microsoft SmartTags/NBC-Interactive’s
QuickClick, etc.
• Link Services and Hypermedia Engines
Bieber, Catanio & Zhang, NJIT ©2003
38
Web Services
• The Metainformation Engine (ME) is a kind of
Web service
– a metainformation/linking service
• ME can integrate with existing Web services
– include Web services in set of links
– supplement Web services with links
Bieber, Catanio & Zhang, NJIT ©2003
39
Semantic Web
• Advocates the use of ontologies (groups of related terms)
to define concepts and their relationships
• Goal: machine-readable semantic description / processing
• Recognizes the need to accommodate diverse knowledge
representations and conflicting definitions.
• The ME could use ontologies to:
– standardize element types
– Find related elements and provide links to their metainformation
Bieber, Catanio & Zhang, NJIT ©2003
40
Microsoft SmartTags /
NBC-Interactive’s QuickClick, etc.
• Set of links generated automatically
– Based on known keywords
– Can add additional links manually
• No structural linking
Bieber, Catanio & Zhang, NJIT ©2003
41
Microsoft Smart Tag critiques
• Users find too many links annoying
• Content providers do not want their
documents altered
• Manipulation: Companies can pay to have
competitors name recognized and linked to
their sites
• Provides content based links (word
recognition) not structural linkages (element
recognition)
Bieber, Catanio & Zhang, NJIT ©2003
42
Link Services
and Hypermedia Engines
• SFX (links to referenced articles)
• Link Services
– Chimera, Microcosm Distributed Link Service, DHM:
manual linking or automated through keyword search
requiring modifications for integration
• Hypermedia Engines with minimal modifications
– Microcosm Universal Viewer, Freckles: manual linking
– OO-Navigator: SmallTalk only
• Web Database Applications, e.g., e-shopping
– database queries only, normally single links
Bieber, Catanio & Zhang, NJIT ©2003
43
Outline
•
•
•
•
•
•
•
Examples
Metainformation (what to provide)
Relationship Analysis (how to find metainformation)
Metainformation Engine (how to automate it)
Virtual Documents (many real world documents)
Related Work
WYWWYWI (what it will take)
Bieber, Catanio & Zhang, NJIT ©2003
44
What you want, when you want it
What will it take?
• WYWWYWI mindset for developers & public
–
–
–
–
Allow metainformation (user-directed) navigation
a design philosophy for developers
demanded by the general public
this requires exposure!
• Developer Tools
• Ubiquitous Access
Bieber, Catanio & Zhang, NJIT ©2003
45
What you want, when you want it
What will it take?
• WYWWYWI mindset for developers & public
• Developer Tools
–
–
–
–
Relationship Analysis
Metainformation Engine
Wrappers for everyday systems
Annotation/knowledge-sharing services (linking,
comments, guided tours, etc.)
• Ubiquitous Access
Bieber, Catanio & Zhang, NJIT ©2003
46
What you want, when you want it:
What will it take?
• WYWWYWI mindset for developers & public
• Developer Tools
• Ubiquitous Access
– Repositories of relationship rules
– Thesauri and glossaries
Bieber, Catanio & Zhang, NJIT ©2003
47
Interesting Issues
• Access privileges to others’ metainformation
• Right to third party authoring/linking
• Quality of metainformation
– Rating metainformation
– Bogus metainformation (such as advertisements)
Bieber, Catanio & Zhang, NJIT ©2003
48
Research Contributions
• Metainformation
– broader conceptualization
• Relationship Analysis (how to find metainformation)
• Metainformation Engine (how to automate it)
– Lightweight systems integration through linking
• Virtual Documents
– Re-generation, re-identification, re-location
• WYWWYWI: a design philosophy
– What you want, when you want it
Thank you! Questions, please?
Bieber, Catanio & Zhang, NJIT ©2003
49