Inconsistent definition of field name constrains

[char0n]

Specification sometimes defines constrains for field names like ^[a-zA-Z0-9\.\-_]+$, other times like [A-Za-z0-9_\-]+. We should unify the format, unless there is a reason for inconsistency which I'm currently missing.