Re: [w3ctag/design-reviews] Early review for adding a new value to the standard list of `name`s for a meta tag (Issue #819)

@plinss, @hober, and I took another look at this in a breakout today.

If there is a problem here, and this is almost certainly true, that problem has not been articulated clearly. Instead, this is adding another thing to the pile of problems in this area.
  
There are costs to making this sort of change.  While it isn't obviously a big deal to add another `<meta name>` type to the already large pile of `<meta name>` types, there are ongoing costs that this will incur.  Extra bytes to transfer, maintenance, and the possibility that integrating this into a more rigorous model of titling could become more cumbersome.
  
It is usually at this point that the TAG recommends that you develop some more complete model of what it is you are changing from and changing to.  There is a lot of structure that is common.

For instance, consider the contents of `<title>` on a typical GitHub issue:
  
> Title of Issue · #Number of Issue · org/repo

Or Google docs:
  
> Title of Document - Google Docs
  
Or Facebook:
  
> (Badge Number+) Title of Post - Author of Post | Facebook
  
Or Fastmail:
  
> Number of unread · Folder – Title of email | Fastmail
  
Or Slack:
  
> Name of Channel - Name of space - Number of new items - Slack
  
There are a number of vocabularies that already encode this sort of metadata (Dublin Core, OpenGraph, whatever Twitter Cards uses, Schema.org, etc...).  Reusing an existing vocabulary, even if it doesn't quite match your precise use case, is likely preferable to inventing a new thing.
  
We also don't see how this should be a different mechanism for an installed web app versus a regular web page. (The name you've chosen, `app-title`, seems to be specific to installed web apps.)


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/819#issuecomment-2187444891
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/819/2187444891@github.com>