The colon in :coreid indicates an ID, which can then be handled with appropriate code, whereas events is ‘merely’ a URL to which you can navigate. (about 50% sure that’s correct ;))
events is not just a url which used for navigate, it will subscribe the properly events. ''events" will be identify as a coreid, if it be routed after “:coreid”, i suppose.
If you’re planning on using the core’s name to access it, then yes, I guess you could say there’s a conflict, in the unlikely event that someone would call their Core “events”. I personally would stick to the coreID to indentify my Core since that is not likely to change, whereas the name is.
Perhaps @dave can elaborate this in a bit more detail(?)