Leo Sauermann explained that a generic RDF browser needs a different display definition for each RDF-schema. This makes a lot of sense. I would add that browser-style applications which truly take advantage of RDF out there will also require something along the lines of a "useage template" for each useage scenario.

Describing how an application interacts with multiple RDF stores can be accomplished with a simplified WSCDL or WSFL. What should definitely be included is how the data sources / aggregators are used and queried against in the application's data model.

My own applications accomplish this sort of data definition in 100 or 200 lines of text. At Boingo, I develop frameworks in perl which allow developers to quickly assemble internal database applications. My development style is to use data structures to describe what the Model, View, and Controller are to do (in response to an action called by the client).

Once the structure of the data store is known to an application, it is not very difficult to have entire applications defined in data.