I don't see more value switching from XML to the DSL. This is just a copy. We have more power idea to use PowerShell classes (Jason's PSMore).

@iSazonov Do you have any new information to share on the status of PSMore and an estimated completion date? The last update I saw was on PowerShell/PowerShell#7857 where Jason said there had been no progress since the last commit. The comment was over a year ago and the last commit he referred to was two years ago. If this is still the case, it’s a stale project with no one actively working on it.

I understand the desire to overhaul the formatting system but PSMore is a longer-term project. This RFC is to address the community desire to use the existing .NET classes to create formatting definitions. PowerShell’s built-in formatting definitions are a great example, they used to use XML files but have transitioned over to using C# classes. The same motivation in that move is here.

XML schema validation only gets you so far in ensuring that PowerShell will accept the ps1xml file. The error messages produced when importing a ps1xml file is difficult to troubleshoot at best and people just don’t have that patience so, most module authors just don’t ship ps1xml files at all.

The specification is built using the existing PSControl builder methods. The DSL implements all existing features. That is why the specification has similarities between the XML schema and .NET classes. This RFC does not propose overhauling the PSControl classes and as such any DSL design will not be revolutionary.

@ThomasNieto ps1xml files are not things that users do on every day basis. In contrast, they use console formatting continuously. Thus, investments in a project like PSMore are more justified.