mark up for restaurant menu

[Brian]

I have to markup a couple of restaurant menus. Two examples follow:

Clam Chowder Cup 3.25 / Bowl 6.95
Thick New England-style clam chowder with
clams, diced onion and celery, bacon, red
bell pepper, but no potatoes!

Mixed Greens Starter 3.50 / Entrée 6.25
Tossed-to-order with your choice of any of
our House dressings: Blue Cheese, Creamy
Herb or Ballymaloe. Garnished with
hazelnuts and red onion.

I'm thinking of using a dl list.

<DL CLASS="menu" ID="soups">

<DT>clam chowder</DT>
<DD>cup 3.25 / bowl 6.95</DD>
<DD>Thick New England-style clam chowder ...</DD>

<!-- etc. -->
</DL>

Any thoughts about this? It seems to make more sense than a table to me.

--
Brian
follow the directions in my address to email me

[Jukka K. Korpela]

Brian <us*****@mangym utt.com.invalid-remove-this-part> wrote:

I have to markup a couple of restaurant menus.
The name of a dish is logically a heading (of some level). The rest can
be marked up using just <div>, since we haven't got markup for prices
or other types of text that you have there.

<h2>Clam Chowder</h2>
<div class="price">C up $3.25 / Bowl $6.95</div>
<div> Thick New England-style clam chowder with
clams, diced onion and celery, bacon, red
bell pepper, but no potatoes!</div>

(I would put a currency name or symbol into the prices, if only to make
it clear that they are prices and not codes or quantities.)

The class attribute is not needed but it makes it possible to style the
appearance easily in CSS.

Alternatively, you could make the menu a table, with the different
parts (name, price info, description) as cells in a row. But you
probably wouldn't like the default presentation of a table element in
this case.
I'm thinking of using a dl list.
Are you really presenting a _definition_ list?
<DT>clam chowder</DT>

Do you provide a _definition_ for the term "clam chowder", i.e.
describe what something needs to be in order to be called "clam
chowder"? No. And besides, the default rendering of <dl> elements is
not very good, _and_ it is difficult if not currently impossible to
tune the rendering well in CSS.

--
Yucca, http://www.cs.tut.fi/~jkorpela/
Pages about Web authoring: http://www.cs.tut.fi/~jkorpela/www.html

[Brian]

Jukka K. Korpela wrote:

Brian <us*****@mangym utt.com.invalid-remove-this-part> wrote:

The name of a dish is logically a heading (of some level). The rest can
be marked up using just <div>, since we haven't got markup for prices
or other types of text that you have there.

<h2>Clam Chowder</h2>
<div class="price">C up $3.25 / Bowl $6.95</div>
<div> Thick New England-style clam chowder with
clams, diced onion and celery, bacon, red
bell pepper, but no potatoes!</div>
Simple, and therefore an good idea.
(I would put a currency name or symbol into the prices, if only to make
it clear that they are prices and not codes or quantities.)
I copied that from the menu .pdf file I received, but have inserted the
dollar symbol ($) in the html. There is no reason not to include it there.
The class attribute is not needed but it makes it possible to style the
appearance easily in CSS.
Of course.
Alternatively, you could make the menu a table, with the different
parts (name, price info, description) as cells in a row. But you
probably wouldn't like the default presentation of a table element in
this case.
That is one reason I wanted to avoid that. Another is that some items
have addional price information. Here's an example:

Classic Caesar (item)
Starter 3.75 / Entrée 6.75 (price as starter / main dish)

The house rendition of Caesar Cardini’s classic. Crisp romaine tossed
with grated
Parmesan cheese, homemade croutons and our own Caesar dressing. Served
with
anchovy upon request. (item description)

Starter Salad & Cup of Soup 6.95 (additional price information)
Starter Salad & Cup of Chowder 7.50 (additional price information)

I didn't come across this until after I'd posted my first message.
Otherwise, I would
have noted it then. Your solution of <h?> and <div> can handle this
quite easily.
Are you really presenting a _definition_ list?

<DT>clam chowder</DT>
Do you provide a _definition_ for the term "clam chowder", i.e.
describe what something needs to be in order to be called "clam
chowder"?

Well, yes, I think I am. ("...with clams, diced onions, and bacon...")
But I'm also providing a price, which is not a definition.
And besides, the default rendering of <dl> elements is
not very good, _and_ it is difficult if not currently impossible to
tune the rendering well in CSS.

I seems quite easy to me. Just by floating dt left, I get a good deal
of the way there.

--
Brian
follow the directions in my address to email me

[Barbara de Zoete]

Jukka K. Korpela schreef:

Brian <us*****@mangym utt.com.invalid-remove-this-part> wrote:

I have to markup a couple of restaurant menus.

The name of a dish is logically a heading (of some level). The rest can
be marked up using just <div>, since we haven't got markup for prices
or other types of text that you have there.

<h2>Clam Chowder</h2>
<div class="price">C up $3.25 / Bowl $6.95</div>
<div> Thick New England-style clam chowder with
clams, diced onion and celery, bacon, red
bell pepper, but no potatoes!</div>

Is there a special reason to prefer <div> over <p>?
--

Barbara

http://home.wanadoo.nl/b.de.zoete/html/weblog.html *Dagboek*
http://home.wanadoo.nl/b.de.zoete/html/vliegen.html *Zweefvliegen*?

[Peter Foti]

"Barbara de Zoete" <b_********@hot mail.com> wrote in message
news:bm******** ****@ID-52872.news.uni-berlin.de...

Jukka K. Korpela schreef:

Brian <us*****@mangym utt.com.invalid-remove-this-part> wrote:

I have to markup a couple of restaurant menus.

The name of a dish is logically a heading (of some level). The rest can
be marked up using just <div>, since we haven't got markup for prices
or other types of text that you have there.

<h2>Clam Chowder</h2>
<div class="price">C up $3.25 / Bowl $6.95</div>
<div> Thick New England-style clam chowder with
clams, diced onion and celery, bacon, red
bell pepper, but no potatoes!</div>

Is there a special reason to prefer <div> over <p>?

In the example given, is it really a paragraph? The first div obviously is
NOT a paragraph. The second div does not really contain a paragraph either
(it contains a fragment of a sentence). In addition, style can be applied
to <div> elements with better results than to <p> elements.

<div> looks correct to me. In fact, you might consider expanding the markup
slightly to something like this:

<div id="ClamChowder ">
<h2>Clam Chowder</h2>
<div class="price">C up $3.25 / Bowl $6.95</div>
<div class="desc">Th ick New England-style clam chowder with clams, diced
onion and celery, bacon, red bell pepper, but no potatoes!</div>
</div>

It's a slightly more flexible design. Just a thought. :)

Regards,
Peter Foti

--

Barbara

http://home.wanadoo.nl/b.de.zoete/html/weblog.html *Dagboek*
http://home.wanadoo.nl/b.de.zoete/html/vliegen.html *Zweefvliegen*?

[Barbara de Zoete]

Peter Foti schreef:

"Barbara de Zoete" <b_********@hot mail.com> wrote in message
news:bm******** ****@ID-52872.news.uni-berlin.de...

Jukka K. Korpela schreef:

Brian <us*****@mangym utt.com.invalid-remove-this-part> wrote:

I have to markup a couple of restaurant menus.

The name of a dish is logically a heading (of some level). The rest can
be marked up using just <div>, since we haven't got markup for prices
or other types of text that you have there.

<h2>Clam Chowder</h2>
<div class="price">C up $3.25 / Bowl $6.95</div>
<div> Thick New England-style clam chowder with
clams, diced onion and celery, bacon, red
bell pepper, but no potatoes!</div>
Is there a special reason to prefer <div> over <p>?

In the example given, is it really a paragraph?

If you ask it this straight forward: no, it isn't. But then I reply with
a question: is 'Clam Chowder' really a <h#>?

I think there are two different ways of looking at html mark-up. Page
structure versus logical text content structure (sorry if I'm not clear
at once; I'm not native speaking in English).

What I mean is, if Clam Chowder is considerred to be a heading, I think
that is not because of the textual content, but because of the mark-up
structure. If so, there is no reason not use <p> for whatever follows
the <h#>.
The first div obviously is
NOT a paragraph. The second div does not really contain a paragraph either
(it contains a fragment of a sentence). In addition, style can be applied
to <div> elements with better results than to <p> elements.
Well, this I consider a _good_ reason to use <div>! Keep it simple for
ourselves.

Thanks, question answered.
It's a slightly more flexible design. Just a thought. :)

I like the way you think.

--

Barbara

http://home.wanadoo.nl/b.de.zoete/html/weblog.html *Dagboek*
http://home.wanadoo.nl/b.de.zoete/html/vliegen.html *Zweefvliegen*?

[Thor Kottelin]

Barbara de Zoete wrote:

Peter Foti schreef:

"Barbara de Zoete" <b_********@hot mail.com> wrote in message
news:bm******** ****@ID-52872.news.uni-berlin.de...

Jukka K. Korpela schreef: <h2>Clam Chowder</h2>
<div class="price">C up $3.25 / Bowl $6.95</div>
<div> Thick New England-style clam chowder with
clams, diced onion and celery, bacon, red
bell pepper, but no potatoes!</div>

Is there a special reason to prefer <div> over <p>?

In the example given, is it really a paragraph?

If you ask it this straight forward: no, it isn't. But then I reply with
a question: is 'Clam Chowder' really a <h#>?

Yes, since it "briefly describes the topic of the section it introduces".

Thor

--
http://thorweb.anta.net/

[Barbara de Zoete]

Thor Kottelin schreef:

Barbara de Zoete wrote:

Peter Foti schreef:

"Barbara de Zoete" <b_********@hot mail.com> wrote in message
news:bm***** *******@ID-52872.news.uni-berlin.de...
Jukka K. Korpela schreef:
<h2>Clam Chowder</h2>
><div class="price">C up $3.25 / Bowl $6.95</div>
><div> Thick New England-style clam chowder with
>clams, diced onion and celery, bacon, red
>bell pepper, but no potatoes!</div>
>
Is there a special reason to prefer <div> over <p>?

In the example given, is it really a paragraph?

If you ask it this straight forward: no, it isn't. But then I reply with
a question: is 'Clam Chowder' really a <h#>?

Yes, since it "briefly describes the topic of the section it introduces".

According to you it does. According to me it is just an element of a
list of different foods.

--

Barbara

http://home.wanadoo.nl/b.de.zoete/html/weblog.html *Dagboek*
http://home.wanadoo.nl/b.de.zoete/html/vliegen.html *Zweefvliegen*?

[Thor Kottelin]

Barbara de Zoete wrote:

Thor Kottelin schreef:

Barbara de Zoete wrote:

is 'Clam Chowder' really a <h#>?

Yes, since it "briefly describes the topic of the section it introduces".

According to you it does. According to me it is just an element of a
list of different foods.

Where do we disagree - briefly, describes, topic, section, introduces?

Thor

--
http://thorweb.anta.net/

[Barbara de Zoete]

Thor Kottelin schreef:

Barbara de Zoete wrote:

Thor Kottelin schreef:

Barbara de Zoete wrote:is 'Clam Chowder' really a <h#>?Yes, since it "briefly describes the topic of the section it introduces".

According to you it does. According to me it is just an element of a
list of different foods.

Where do we disagree - briefly, describes, topic, section, introduces?

:-) I think we disagree as in the way we think, but narrowing that down:
topic and introduces. If I'm in a restaurant reading a menu, I don't
think of the listed food as topics. I just see listed food that gets
described so I can find out what I order (although I have no clue, not
even from the description, what Clam Chowder is ;-) ).

--

Barbara

http://home.wanadoo.nl/b.de.zoete/html/weblog.html *Dagboek*
http://home.wanadoo.nl/b.de.zoete/html/vliegen.html *Zweefvliegen*?