REML Recipe Manager 0.8.0.0 Beta

REML Recipe Manager 0.8.0.0 Beta is regarded as a helpful and convenient to use XML schema that describes a file format for recipe exchange.

The general notion is that an REML file contains menus (such as used in a restaurant, not a software menu).  Menus contain meals, which contain meal items, which contain ingredients and other data. For example, a menu might represent a cookbook with REML meals for chapters and REML meal items for recipes.  Or, a menu might represent a restaurant menu. A software package might offer a "customer" display mode with general comments and retail prices, and a "chef" display mode with full cooking instructions. REML is flexible; all you need is the right presentation tier for your needs.

Possible additions to the REML standard (not just the application) would be inventory support (are the ingredients on the shelf or should a shopping list be generated?) and ID tags that are intended to be unique. The problem with uniqueness is that given an XML structure, it's hard to determine uniqueness, especially in a multi-file-multi-user enterprise application. Unique IDs could be represented with vendorData elements, but vendorData is intended to be application specific, and not generic to the recipe exchange paradigm. The question is, would one application's IDs be usable by other applications, both at run-time and between runs, and is it worth trying to standardize this?