|
|
-
Why MRL?
-
That could be one of two different questions. (At least.)
-
Why MRL instead of RecipeML?
-
RecipeML
is an XML markup
language for recipes that has been around for at least three years. The results
of a
Google search
suggest that RecipeML enjoys at least use in the real world. So why come up
with another markup language?
-
The RecipeML web site appears to be stagnant. The most recent
news item
was posted on
2001-07-01.
-
Development on RecipeML appears to have gone dormant. The most recent version
of the specification is 0.5,
released 2000-12-05
.
Usually, version numbers less than 1.0 indicate that the software or
specification is pre-release and is still being developed. However, when three
years pass without a bump in the version number (even to 1.0), it suggests that
development has been abandoned.
-
The
license
under
which RecipeML is available does not appear to be open-source friendly. To
quote from the RecipeML
home page
:
RecipeML is free to use as long as the license is followed. This is the gist of
it:
-
Use RecipeML as
it is specified in this site—no unauthorized changes!
-
Mention that your site/software uses RecipeML by name.
(If it is software, you need to get permission first.)
(Emphasis mine.)
Maybe I'm wrong. Maybe all of these conclusions I've drawn about RecipeML are
wrong; maybe RecipeML is alive and well and serving as the
de facto
standard for recipe markup for many open-source projects. If so, then I'll
admit my mistake and close up shop here.
Maybe. :-)
-
Why "Markup Recipe Language"? Why not "Recipe Markup Language"?
-
For one thing, that's awfully similar to RecipeML. For another, "MRL" is
pronounced "em-err-ell", which should remind you of someone. Who cooks.
On TV
.
|
Home
Project Info
Project Reports