Re: [WSG] META tag standards?

2005-09-11 Thread Patricia Jack




Best to use lowercase when you are not sure, but there is not realy a
standard for it so far I know.. ;)

check also the 
Meta Tag Analyzer
http://www.widexl.com/remote/search-engines/metatag-analyzer.html

Its more for keywords and stuff but they have a view tips

Also a list of best meta tags to use and taken in by spiders writen by
Ben Wiggy:

Part1:
http://www.benwiggy.com/webdev/metatagtutorial.php

Part2:
http://www.benwiggy.com/webdev/metatagtutorial_2.php

Greetings,
Jack




Gene Falck wrote:
Hi
everyone,
  
  
I've been prowling around in our resources and in
  
Google but I haven't found this. (As usual, I may
  
just not know what to call my question.)
  
  
I understand about using lower case for tags and
  
attributes in XHTML (leaving content capitalization
  
unspecified to accommodate a wide range of strings)
  
but haven't seen anything on those value items that
  
seem to be relatively frequent and "standard" items.
  
  
For instance, I see the following variants in the
  
capitalization of values:
  
  
meta http-equiv="Content-Type" ...
  
meta http-equiv="Content-type" ...
  
meta http-equiv="content-type" ...
  
  
The Content-Type entry, even though it's a value,
  
certainly looks standard enough to have a right way
  
to write it.
  
  
Is one of the above a standard or a best practice?
  
  
Regards,
  
  
Gene Falck
  
[EMAIL PROTECTED]
  
  
  
**
  
The discussion list for http://webstandardsgroup.org/
  
  
See http://webstandardsgroup.org/mail/guidelines.cfm
  
for some hints on posting to the list  getting help
  
**
  
  
  




**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
**



Re: [WSG] META tag standards?

2005-09-11 Thread Hassan Schroeder

Gene Falck wrote:


I understand about using lower case for tags and
attributes in XHTML (leaving content capitalization
unspecified to accommodate a wide range of strings)
but haven't seen anything on those value items that
seem to be relatively frequent and standard items.

For instance, I see the following variants in the
capitalization of values:

meta http-equiv=Content-Type ...
meta http-equiv=Content-type ...
meta http-equiv=content-type ...

The Content-Type entry, even though it's a value,
certainly looks standard enough to have a right way
to write it.


Since 'http-equiv' indicates this represents HTTP header information,
you should consult RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1

Specifically,
   http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2

quote
4.2 Message Headers

HTTP header fields, which include general-header (section 4.5), 
request-header (section 5.3), response-header (section 6.2), and 
entity-header (section 7.1) fields, follow the same generic format as 
that given in Section 3.1 of RFC 822 [9]. Each header field consists of 
a name followed by a colon (:) and the field value. Field names are 
case-insensitive.

/quote

So it doesn't matter, but as far as best practice -- dunno, but my
personal preference would be 'Content-Type'; I just prefer the way it
looks :-)  YMMV!

HTH,
--
Hassan Schroeder - [EMAIL PROTECTED]
Webtuitive Design ===  (+1) 408-938-0567   === http://webtuitive.com

  dream.  code.


**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**



[WSG] META tag standards?

2005-09-10 Thread Gene Falck

Hi everyone,

I've been prowling around in our resources and in
Google but I haven't found this. (As usual, I may
just not know what to call my question.)

I understand about using lower case for tags and
attributes in XHTML (leaving content capitalization
unspecified to accommodate a wide range of strings)
but haven't seen anything on those value items that
seem to be relatively frequent and standard items.

For instance, I see the following variants in the
capitalization of values:

meta http-equiv=Content-Type ...
meta http-equiv=Content-type ...
meta http-equiv=content-type ...

The Content-Type entry, even though it's a value,
certainly looks standard enough to have a right way
to write it.

Is one of the above a standard or a best practice?

Regards,

Gene Falck
[EMAIL PROTECTED]


**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**



[WSG] meta tag standards

2005-01-20 Thread Phil Baines








Hello List, 



Is there anything wrong with closing meta tags like so:



 meta name=keywords content=Web, Development, Design, Hosting, Ecommerce, IT, Consultancy, Logos, Logo, Websites /metaThe reason that I ask is that I am developing our new company website (http://dev.netring.co.uk/netring2004 - I started it in 2004) and I am using XML and XSLT as the backend template system. The problem is that I cant get XSLT to close my Meta tag (meta /) in the way that I wish it to be.I was wondering if there was actually anything wrong with closing it in a separate closing tag. Thanks for any advice,Phil Baines







Netring media and
technology

website: www.netring.co.uk

telephone: 01239 711 471













The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.



--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19/01/2005
 


Re: [WSG] meta tag standards

2005-01-20 Thread Lea de Groot
On Thu, 20 Jan 2005 11:57:02 -, Phil Baines wrote:
 meta name=keywords content=Web, Development, Design, Hosting,
 Ecommerce, IT, Consultancy, Logos, Logo, Websites
 /meta

The correct syntax would be
meta name=keywords content=Web, Development, Design, Hosting, 
Ecommerce, IT, Consultancy, Logos, Logo, Websites /

Note the slash inside the meta tag!
See http://www.w3.org/TR/xhtml1/#h-4.6

HIH
Lea
-- 
Lea de Groot
Elysian Systems - I Understand the Internet http://elysiansystems.com/
Search Engine Optimisation, Usability, Information Architecture, Web 
Design
Brisbane, Australia
**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



Re: [WSG] meta tag standards

2005-01-20 Thread Kornel Lesinski

Is there anything wrong with closing meta tags like so:

meta name=keywords content=Web, Development, Design, Hosting,
Ecommerce, IT, Consultancy, Logos, Logo, Websites
/meta
In XML probably not, but tag-soup browsers/robots may try to fix your  
code
and assume that /meta is ment to be /head or something like that.

My XSLT knowledge is tiny, but I think that it is quite possible to
make meta / tag, check XSLT FAQ:
http://dpawson.co.uk/xsl/sect2/sect21.html
--
regards, Kornel Lesiski
**
The discussion list for  http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**


Re: [WSG] meta tag standards

2005-01-20 Thread Bert Doorn
G'day
Is there anything wrong with closing meta tags like so:
meta name=keywords content=Web, Development, Design, Hosting, Ecommerce, IT, Consultancy, Logos, Logo, Websites
/meta
I was wondering if there was actually anything wrong with closing it in a separate closing tag. 
http://www.w3.org/TR/html4/index/elements.html
Scroll down to META.  Look at the third column (which is for End 
Tag).  It says F, which means FORBIDDEN.  It is also an empty 
element, just like IMG, INPUT, BR, HR (to mention a few obvious 
ones).

http://www.w3.org/TR/xhtml1/#C_2 says:
Include a space before the trailing / and  of empty elements, 
e.g. br /, hr / and img src=karen.jpg alt=Karen /. 
Also, use the minimized tag syntax for empty elements, e.g. br 
/, as the alternative syntax br/br allowed by XML gives 
uncertain results in many existing user agents.

So yes, I'd say there is something wrong with meta ... /meta, 
just like there is with br/br and img .../img

HTH
--
Bert Doorn, Better Web Design
http://www.betterwebdesign.com.au/
Fast-loading, user-friendly websites
**
The discussion list for  http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**


RE: [WSG] meta tag standards

2005-01-20 Thread Phil Baines








Hello again list!



Okay, thanks for all
the feedback! Especially Kornel Lesinski for the link to (http://dpawson.co.uk/xsl/sect2/sect21.html)
where I found (http://dpawson.co.uk/xsl/sect2/N4622.html),
and this piece of code:



xsl:template match=ImageInfo img src="">/xsl:template



I have never seen that done before with the XPath
_expression_ in curly brackets. Its not very widely documented at all! 



So now, instead of using this XSL:



meta name=description

xsl:attribute
name=content

xsl:value-of
select=base/[EMAIL PROTECTED]'description'] /

/xsl:attribute

/meta



Producing this HTML:



meta name=description content=Netring Media and Technology are a/metaI can use this: meta name=description content={base/[EMAIL PROTECTED]'description']} / To produce this: meta name=description content=Netring Media and Technology are a  /Also, thanks to Bert Doorn for showing me where it says that a separate closing tag is forbidden for Meta tags. Its always good when someone can point to a reference rather than just saying so.I think that I will right a short entry on my site about this. Thanks all again for the help.Regards,Phil Baines







Netring media and
technology

website: www.netring.co.uk

telephone: 01239 711 471











From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phil Baines
Sent: 20 January 2005 11:57
To: wsg@webstandardsgroup.org
Subject: [WSG] meta tag standards





Hello List, 



Is there anything wrong with closing meta tags like so:



 meta name=keywords content=Web, Development, Design, Hosting, Ecommerce, IT, Consultancy, Logos, Logo, Websites /metaThe reason that I ask is that I am developing our new company website (http://dev.netring.co.uk/netring2004 - I started it in 2004) and I am using XML and XSLT as the backend template system. The problem is that I cant get XSLT to close my Meta tag (meta /) in the way that I wish it to be.I was wondering if there was actually anything wrong with closing it in a separate closing tag. Thanks for any advice,Phil Baines







Netring media and
technology

website: www.netring.co.uk

telephone: 01239 711 471













The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.


The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.



--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19/01/2005
 


--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19/01/2005
 

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19/01/2005