- From: Arpita Bahuguna <arpitabahuguna@gmail.com>
- Date: Wed, 16 Jul 2014 15:01:37 +0530
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: whatwg@whatwg.org, Arpita Bahuguna <a.bah@samsung.com>
Hi Julian, Thank-you for your views. Are you suggesting that we instead introduce a new link relation (perhaps "contact") with tel:/mailto: types for specifying these parameters? This would involve spec modification. Not sure how developers or browser vendors take to it. Was looking for a simpler solution that's quickly implementable. Regards, Arpita On Tue, Jul 15, 2014 at 6:14 PM, Julian Reschke <julian.reschke@gmx.de> wrote: > On 2014-07-15 12:11, Arpita Bahuguna wrote: > >> Hi, >> >> I would like to propose addition of the following three meta extensions: >> website-mail, website-number and website-address. >> >> Please find below a detailed description for each. >> >> ------------------- x ------------------------- x >> --------------------------- x -------------------------- >> >> Overview: >> >> The website-mail meta extension defines a suggested e-mail ID, such as the >> customer support mail ID, specified by the vendor. >> >> The website-number meta extension defines a proposed phone number, such as >> the customer support number, specified by the vendor. >> >> The website-address meta extension defines a given address (or geolocation >> tag), such as the vendor's office address or billing address. >> >> >> >> UA's displaying a page containing any or all of these meta extensions >> could >> then make this information directly available for the user's perusal. >> >> >> >> Oft times visitors have to hunt through a vendor's site for obtaining the >> customer support mail ID, phone number etc. which is mostly hidden behind >> a >> not so prominently displayed "Help" or "Contact Us" link. >> >> Vendor's specifying their registered mail ID, phone number and/or their >> address via these meta extensions can thus expect supporting UA's to >> present >> this information to the user in an easily accessible format, either by way >> of a browser menu option (such as "mail", "call", "map") or via the URL >> bar >> scheme handler or in another similar format. >> >> Selecting these menu options, if available, should launch the default mail >> application with the specified mail ID, the dialer application with the >> given contact number or, the default maps application loaded with the >> specified address/location tag respectively. >> >> No known existing meta extensions with a similar name/intention exist. >> >> Syntax: >> >> <meta name="website-mail" content="abc@xyz.com"> >> > > This should be a link relation, using by default a "mailto:" URI. > > > The content attribute for the website-mail meta extension can take any >> valid >> email ID. >> >> <meta name="website-number" content="+1-555-555-5555"> >> > > This should have a better name, and also be a link relation, using a > "tel:" URI. > > The content attribute for the website-number meta extension can take any >> valid phone number. >> >> <meta name="website-address" content="Jane Doe, 5844 South Oak Street, >> Chicago, Illinois 60667"> or >> >> <meta name="website-address" content="20.593684;78.96288"> >> >> The content attribute for the website-address meta extension can be any >> string or latitude and longitude separated by a semi-colon. >> >> Note: >> >> . In case multiple instances are found of the same meta extension, >> the last specified one should take precedence. >> ... >> > > In general, a single link to a URI having contact information seems to be > much simpler to me... > > Best regards, Julian >
Received on Wednesday, 16 July 2014 09:32:06 UTC