ecore.ecore in ecore-glsp

[GaryKopp]

The workspace directory within the client directory of ecore-glsp contains five separate models. Of these, "UML" and "statemachine," would appear to be sample instance models that might be edited by the user. "glsp-graph" might also fit in this category, but since it really define's GLSP's standard graph model, which is used by implication in the ecore-glsp application, I can't imagine it being edited, and thus I question its visibility to the application user in the workspace. So why is it there? Similarly, and more fundamentally, the fifth model in the workspace is named "ecore" and probably should not be presented to the application user as something that might be edited. Would I be correct in calling this "ecore" model in the workspace a meta-model for the other models in the workspace, and indeed for any new instance model a user might create and edit in this application? In the ecore-glsp code this model appears under the name "type schema," correct? It is fundamental to the functioning of the application. In fact, it seems to be used so much that a performance problem resulted and the JSON version of this model had to be hard-coded into the application. So, again, the "ecore" directory in the workspace in the distro should not really be presented to the user as a sample suitable for editing, right?