The documentation for id says "uniquely identify" but not the scope - within a single model, universally?
And for humanID (sic) it's also vague: "the uniqueness of this identifier within a model or relative to some other context."

The intended usage is unclear - calling it "human" does not seem helpful since it's presumably not for human consumption e.g. for display on a diagram?
And "human" is also wrong if the model was generated by a tool, i.e. the "modeler" is not a human.

Without further rules, or a compliance point, interoperability becomes unnecessarily hard.

id is not an acronym but short for identifier. So for consistency with the "id" property, and camelcase rules, they should be humanId and aliasId

Though Vocabulary in SCE would correspond to Dictionary in MVF, since SemanticElement in SCE corresponds with MVFEntry in MVF.

The current SCE XSDs were developed with a faulty translation of UML class relationships to the XSD elements.
To resolve this issue we need to specify the XSD patterns that correspond to the UML class relationships and then update the XSDs.

Name is odd if it's meant to represent a specific version. For example OWL uses versionIRI for this.