W3C home > Mailing lists > Public > www-html@w3.org > August 2004

Re: [xhtml2] Questions

From: Anne van Kesteren <fora@annevankesteren.nl>
Date: Sun, 22 Aug 2004 23:07:55 +0200
Message-ID: <41290B2B.7050106@annevankesteren.nl>
To: Karl Dubost <karl@w3.org>
CC: Jens Meiert <jens.meiert@erde3.com>, W3C HTML <www-html@w3.org>

>> Well, can you please shed some light on some XHTML 2.0 issues
>> (though they're rather questions which concern former HTML
>> versions):
>> - For non-native English speakers, it's sometimes difficult to
>> understand the difference between <cite /> and <quote />, since
>> citations often seem to be quoted, too (this is a presentational
>> aspect, I know).
>> I must admit, what exactly is the semantic difference? I always
>> perceived the <quote /> and <blockquote /> elements as a more
>> general approach to represent citations, too.
> This (the examples given) could be *one* of the possibilities, the 
> precise content model is not completely defined; Some will say it's a
> feature, others will say it's a bug. It really depends on what you
> do and what kind of apps you developed, maybe the missing guide for
> XHTML is an official *Best Practices for XHTML*

Such a guide might be nice. Although I think that a tight specification 
should be enough. The above addressed questions should be clear from the 

> The class values (dc:title, dc:author) are my own and have nothing 
> official. if you want to style that in CSS, you have to do something
> like that:
> .dc\:title { color: black;}

Maybe some RDF attribute should be developed? So elements can be given
more specific semantics without the need for CLASS "hacks" or "ugly

> the value of the cite is a *URI*, so URN are possible if you think
> that in your system it's better. Unfortunately they are not
> implemented as a link in browsers.

Maybe because the specification doesn't define how a browser should
treat the attribute exactly? It doesn't sound really like good design
either to hide information that should be displayed inside an attribute.

> When there is for example an "http-like" URI. You may wish to have a
> contextual menu to go to the source.

Exactly. Or having elements so people can describe the source of quotation.

   <source href="http://example.org/">...</source>

Where SOURCE can have nested inline elements.

  Anne van Kesteren
Received on Sunday, 22 August 2004 21:08:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:06:09 UTC