6
Deliverable 1 Schema Presentation Ryan Prins October 15 th , 2003 INFO 320 – Terry Brooks

Deliverable 1 Schema Presentation Ryan Prins October 15 th, 2003 INFO 320 – Terry Brooks

Embed Size (px)

Citation preview

Page 1: Deliverable 1 Schema Presentation Ryan Prins October 15 th, 2003 INFO 320 – Terry Brooks

Deliverable 1 Schema Presentation

Ryan PrinsOctober 15th, 2003

INFO 320 – Terry Brooks

Page 2: Deliverable 1 Schema Presentation Ryan Prins October 15 th, 2003 INFO 320 – Terry Brooks

XML Sources Store Information

Hours of Operation Location

Phone Number Address

Flower Information Type Price Quantity Description Product ID

Page 3: Deliverable 1 Schema Presentation Ryan Prins October 15 th, 2003 INFO 320 – Terry Brooks

Why only one source for flowers?

Maintains easy to follow file structure. Only calling data from one XML source

as opposed to many. It would be more beneficial to keep all

the flower data in one place, instead of many places (many sources).

Keeps the upkeep to only one file, not many.

Make the XSL style sheet do the work, not the XML source.

Page 4: Deliverable 1 Schema Presentation Ryan Prins October 15 th, 2003 INFO 320 – Terry Brooks

How this structure works

Roses

Daylilies

Daffodils

Tulips

XML Source

Roses

Daylilies

Daffodils

Tulips

XSL

Style sheet

Roses

Daylilies

Daffodils

Tulips

HTML Output

Page 5: Deliverable 1 Schema Presentation Ryan Prins October 15 th, 2003 INFO 320 – Terry Brooks

Ad Hoc Request Preparation Easy to find data within simple structure tree.

Roses Daylilies Daffodils Tulips

Very adaptable to the various types of requests that may be needed.

By Price By Name By Type And so on…

Easy to add various types of flower characteristics.

Page 6: Deliverable 1 Schema Presentation Ryan Prins October 15 th, 2003 INFO 320 – Terry Brooks

Data Reuse

One schema is used for all the flower types.

One schema is used for the store information.

This keeps the reuse level high while keeping the maintainability low.