Our rules for identifier looks similar to C#/ECMA identifiers with the exception that we don't allow names starting with underscore. The underlying reason is that as part of the EF model we use EDM (up to v3), which has the same restriction.
This restriction feels rather arbitrary for EF and that seems to outweigh any real motivation for keeping our EDM standards compliant (e.g. the technologies that use the EDM produced by EF to create a v3 OData feed can easily alias any non-compliant identifiers if needed).
The issue was reported in the past in [StackOverflow](http://stackoverflow.com/questions/10853232/how-to-fix-error-name-the-specified-name-is-not-allowed-destroy) but it wasn't per se very high priority. Removing this restriction should unblock partner teams that want to use EF in this way.
This restriction feels rather arbitrary for EF and that seems to outweigh any real motivation for keeping our EDM standards compliant (e.g. the technologies that use the EDM produced by EF to create a v3 OData feed can easily alias any non-compliant identifiers if needed).
The issue was reported in the past in [StackOverflow](http://stackoverflow.com/questions/10853232/how-to-fix-error-name-the-specified-name-is-not-allowed-destroy) but it wasn't per se very high priority. Removing this restriction should unblock partner teams that want to use EF in this way.
