 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| • |
This
architecture is already a little problematical in many
|
|
|
systems
|
|
|
|
– |
E.g.
if I import PowerPoint into XYZ LMS and it integrates as a
|
|
lecture;
adds decorations/metadata – can I edit PowerPoint and
|
|
|
preserve
“decorations/metadata”?
|
|
|
|
– |
Can
I change number of pages in Presentation?
|
|
|
| • |
Several
Content Models
|
|
|
|
– |
1)
Faculty writes a set of Web Pages
|
|
|
|
– |
2)
Faculty uses an initial template to start Web Pages
|
|
|
|
– |
3,4)
Some sort of Template specifies page layout of metadata,
|
|
|
decorations
and content. Content is authored elsewhere. LMS
|
|
|
stores
all this in database or flat (XML) files
|
|
|
|
• |
3)
Actual Content generated by batch process
|
|
|
|
• |
4)
Actual Content generated by dynamic process
|
|
