Support for libraries and standard model snippets in Umple

[GoogleCodeExporter]

Part 1. Build some standard pieces of model that could be imported into other 
models. For example, a standard core of a transportation system with legs, 
bookings, scheduled and actual etc. 

Part 2. Add to the 'use' clause a capability that would allow renaming of 
certain elements from the reused components, so for example Trip could become 
Flight. There may be other ways of doing this other than adjusting the use 
clause.

Part 3. Allow any Umple model to declare it will use any of the built-in 
standard models. In other words, adjust the search path to do the following. 
First look in the local directory, then look in a standard place in the 
compiler release, and finally look on the web in a standard place. In addition, 
it should be possible to specify a URL in the use clause to refer to a model 
snippet on the web.

See also issue 324 since some existing repositories might have good examples 
for a standard model library.

The RoutesAndLocations example could be part of a standard.

See also the work on VML done by Jenya Levin 

Original issue reported on code.google.com by TimothyCLethbridge on 16 Aug 2012 at 5:21

[GoogleCodeExporter]

See also issue 340

Original comment by TimothyCLethbridge on 30 Sep 2012 at 10:30

[GoogleCodeExporter]

Original comment by TimothyCLethbridge on 31 Dec 2012 at 6:08

• Changed state: Accepted

[GoogleCodeExporter]

This is part of the broader work on separation of concerns

Original comment by TimothyCLethbridge on 8 Jul 2013 at 3:13

[GoogleCodeExporter]

Original comment by TimothyCLethbridge on 17 Sep 2013 at 1:12

• Added labels: Type-ResearchGrad
• Removed labels: Type-ProjectUG