I mean, of course, with respect to appropriately licensed (Creative Commons, Gnu Free Document License, etc) open educational resources specifically.

And though the question is not staggering, it may be taken for granted, even at the cost of the long-term success of the web project.

Linking

The link approach typically uses hyperlinks to the target source document, but may use iframes to embed the element within a locally-hosted web page.

Linking…

1. preserves integrity of the original source by maintaining all original qualities
2. respects original source by trajecting traffic to the host site
3. saves local hosting resources (storage & bandwith)
4. ensures that source updates are reflected in the current version
5. is, therefore, particularly well-suited for frequently updated or improved sources, like wikis
6. is much easier, particularly when numerous multimedia files are embedded, or multiple files are referenced
7. may provide learners with context and hyperlinks that lead to further, relevant exploration of the source site and the web
8. avoids problems with licenses or terms of use that restrict copying

Many of these arguments for linking presume that there is more to the information than the information itself, and that the source has some inherent value that may be passed on to the learners or should be maintained for its own sake.

Copying

The copy approach is similarly self-evident: a digital copy of the source file(s) is downloaded, then hosted on the local server.

Copying…

1. provides for adaptation or modification (if the license allows) of:
   • content (cut, insert, remix, extend)
   • presentation (e.g. surface design)
   • interactions
2. supports localization
3. captures and preserves a version that may be discarded or replaced in the future
4. allows designers to produce seamless learning experiences that support learner focus
5. respects original source host’s resources (storage & bandwith)
6. ensures technical availability of the resource is within local control (no dead links)
7. allows contextual indexing for site (or public) search engines
8. may improve reach and increase circulation of source information
9. may thereby enlarge original author’s prominence and visibility
10. avoids problems with licenses or terms of use that restrict leech-linking

A couple notable obstacles to copying:

• Server-generated content, markup, interactions, or hyperlinks may be difficult to acquire or reuse (e.g.
• While CC By-ND allows reproduction of works, it may restrict modification of presentation or interactions in addition to the more clear prohibition on modification of content

Dynamic Scraping and Importing

There are other approaches that fall somewhere in between. For instance, web scraping of the source file(s) on the fly, followed by parsing and processing of the data on the local host. This sounds complex, but it’s not too bad; Google Docs & Spreadsheets has implemented this functionality into it’s data importing spreadsheet formulae:

• =importHTML grabs the content of a TABLE or list (OL / UL [/DL?])
• =importXML uses xPath expressions to target XML/XHTML elements
• =importData takes structured data files, such as comma separated values (CSV)
• =GoogleReader intakes the RSS or Atom of a target URL, such as a blog post

Often used for mash-ups, this approach can also be useful for replicating and formatting data. And, though Tony Hirst has found numerous exemplary applications for this feature using Google Spreadsheets, a Google Spreadsheet is not required; anyone with some significant Javascript experience could tackle this task, and there are a number of web scraping software apps that deliver varying results.