[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Relating to XML

• To: Baiss Magnusson <cascades@e...>
• Subject: Re: Relating to XML
• From: Jim Ancona <jim@a...>
• Date: Fri, 21 Nov 2003 19:53:30 -0500
• Cc: XML-DEV <xml-dev@l...>
• In-reply-to: <009B3DBF-1C7A-11D8-B8A7-003065BF41DE@e...>
• References: <FB4F95390166B14C90E4DD950D69D6E21A811B@E...> <009B3DBF-1C7A-11D8-B8A7-003065BF41DE@e...>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007

Baiss Magnusson wrote:
> My problem with <RecipeML> is, IMO, that it violates 
> Model-View-Controller (MVC) programming in that it combines data 
> description and data display in one document.

I'm not sure why you think this is the case. Looking at the RecipeML 
example at http://www.formatdata.com/recipeml/examples/hoax.xml, the XML 
file deswcibes the recipe data (title, ingredients, directions), while 
the CSS stylesheet dessert1.css describes how to format a recipe in a 
browser. That seems like Model-View separation to me.

> I have no interest in the CSS or the display criteria of a recipeML 
> recipe, I just want the data.

Note that the XML processing instruction "<?xml-stylesheet ... ?>" is 
only a hint for applications processing the application that the 
referenced stylesheet may be useful. It's not mandatory, and if it is 
present, applications are free to ignore it.

> I'm willing to acknowledge that there is a use for RecipeML, I just 
> don't see it as apropos to a XML definition for recipes.

Perhaps you can explain the shortcomings you see in a little more detail.

Jim

• References:
  • RE: Relating to XML
    • From: "Chris Wilper" <cwilper@c...>
  • Re: Relating to XML
    • From: Baiss Magnusson <cascades@e...>

• Prev by Date: Re: Microsoft FUD on binary XML...
• Next by Date: Re: Microsoft FUD on binary XML...
• Previous by thread: Re: Relating to XML
• Next by thread: RE: Relating to XML
• Index(es):
  • Date
  • Thread