I've created several ecore models over the years but never really been clear what the "nsuri" value should be set to. I think it's suppose to be something unique to my org such as "http://www.acme.com" or "http://www.acme.com/myecore" but does the URI given have to be resolvable?
Does the URI need to return something specific? I don't really want to publish my ecore models to the internet. The ecore files refer only to themselves on the local filesystem.
To avoid validation diagnostics, it must be non-null and a well-formed URI.
It should be unique since two 'different' models with the same nsURI may not be consistently different leading to the horrible X is not an X diagnostic.
You can choose any text, but to avoid a clash should your model every find itself in the same workspace as another similarly inspired name it is good practice to use your unique internet as part of the name, and since clashes with your colleagues are quite likely a distinctive project name too.
For stable released models, a year is quite a useful inclusion since you can change it when the model really evolves incompatibly.
One clarification: Does the URL have to be resolvable or return any data in any specific format? It sounds like it's really just used as a unique identifier and is not suppose to have any kind of data that is accessable.
Is it sufficient to use something like "http://www.acme.com/mymodel" where www.acme.com is resolvable but the actual URI returns 404 (Not Found)?