Project name

[flotang-gtt]

After a few discussions, ThermML is the first proposed name for the project, but I'm very open to discuss this.

There are a few other suggestions worth discussing:

• XMLTDB: This may be the most obvious choice. However, I feel this name is too close to the 'TDB' origins and wouldn't do the presumed further reach of the markup language justice
• TDB: as the schema is planned to describe thermo(dynamic/chemical/physical) databases, this would be a nice and simple name. However, it clashes with the specific database format TDB, which woudl confuse users for a long time.
• XTDB / XDB: A relatively obvious synthesis of the above two names. I do not have strong objections to this.
• ThermML: This highlights the structural considerations that go into designing a markup language. I like the "ambiguity" of being able to cover all thermoXY datasets with this. It's also a nice switchup from the 'DB'.

Generally, to avoid bikeshedding the project by searching for a name, I just used ThermML.

[bocklund]

At risk of opening up bikeshedding, ThermoML is a NIST product also based on XML, and probably too close for us to use effectively. But I’m fine using the ThermML name here for now to be at least self-consistent

[johanzietsman-em]

After seeing the pycalphad-xml name, I thought that CalphadML may be an option. "Calphad" does not completely describe that we want to describe both thermodynamic and kinetic material behaviour. The name does, however, represent a strong "brand" and community, and it should be recognisable and non-threatening to most who we want to involve.

I don't think we should make a final decision on this in haste. It can simmer for a while.

[motobaben-gtt]

I am proposing CalphapML then. I think a big benefit will be that this structure will enable us as community to move from "Calculation of Phase Diagrams" to "Calculation of Phase Properties". As far as I know CalPhaP is not yet used. ThermML does not reflect sufficiently that we will (very soon) include e.g. crystal structure information. I also agree that this is not the most important point at this time.

[richardotis]

A few ideas (AI-assisted):

• CalphadXML (.cxml)
• CalXML (.calx)
• ThermoXML (.txml) - has the same name conflict problems as ThermoML
• PhaseDB (.pdbx)
• PhaseXML (.pxml) - my personal favorite