Renaming proposal (for v.Next)

[cmsmcq]

In mail to the community group on 27 October, Steven Pemberton (@spemberton) made the following proposal, which I transcribe here to get it into the issue tracking system.

Working further on my tutorial. I give examples of how to rename an element:

start: -date.

so a <start> element has the same content structure as a <date>.

But it would be handy to go in the other direction too.

date: day, " ", month, " ", year.
day: d, d?.
month: "January"; "February"; etc.
year: d, d, d, d.

iso: year, "-", nmonth, "-", day.
nmonth: d, d.

The month and nmonth elements have to have different names, because they have different syntaxes.

Strawperson proposal:

iso: year, "-", nmonth^month, "-", day.

Read "an nmonth serialised as <month>", and by extension, used in a rule definition:

nmonth^month: d, d.

[cmsmcq]

For discussion, see also

• mail from Tomos Hillman on 27 October showing a pragma for renaming.

• mail from Michael Sperberg-McQueen on 8 November showing another case where renaming could be applied (but worrying about the effect on schema generation and on re-serialization of parsed data).

[ndw]

Steven proposed: https://lists.w3.org/Archives/Public/public-ixml/2023Jun/0030.html

But the formatting of that message is awful. The proposal is "name>rename : ...".

[ndw]

Resolved by #191