attribute-name in XSD may contain integers, which is wrong

[yegor256]

In XMIR.xsd, if I change the attribute-name type by removing the [0-9]+ from its regular expression, UnphiMojoTest fails. Looks like we use this attribute (o/@name) incorrectly, holding their numbers when necessary. Let's get rid of this hack.

[yegor256]

@maxonfjvipon need your help here

[maxonfjvipon]

@yegor256 I believe @volodya-lombrozo won't like it since he uses numbers in attributes in jeo a lot

[yegor256]

@maxonfjvipon we'll ask JEO to use something else, maybe same numbers but with a letter as a prefix

[maxonfjvipon]

@yegor256 one of the problem here is that attribute-name is used as type for @as attribute which may be an integer number.

string
  01-02:0
  03-04:1

I tried to solve the problem by introducing new type attribute-binding specially for @as attribute and remove [0-9]+ from attribute-name. Here I'm facing a new problem while getting from XMIR from phi:

⟦ α65536 ↦ Φ.r ⟧

In phi-calculus, formation may contain attributes which name starts from α. While parsing phi we ignore α and get 65536. When this number goes to @as attribute - it's ok, but when it goes to @name - it's wrong.
What do you think? How would you suggest to resolve this properly?

[yegor256]

@maxonfjvipon maybe let's allow α0 in the @as attribute?

[maxonfjvipon]

@yegor256 then we should catch it when we print XMIR to EO and remove α, or add α when we parse the next EO: string 01-02:0

[maxonfjvipon]

@yegor256 but how to deal with this: ⟦ α65536 ↦ Φ.r ⟧. Here α65536 goes to @name attribute and there's no way it can be converted to EO properly

[yegor256]

@maxonfjvipon indeed, this

⟦ α65536 ↦ Φ.r ⟧

Can't be converted to XMIR/EO anyhow. We must throw an exception in this case, since it's not a valid phi-expression either. All α-prefixed attributes in a formation must start with zero and go one after another without any gaps. Maybe, we should create a lint for this too.

[maxonfjvipon]

@yegor256 so the result attribute-name pattern would be: α[0-9]+|@|[a-z][^ \n\t\r]*?

[yegor256]

@maxonfjvipon correct