And what would you recommend?
I am curious about what you mean in terms of websites.
I do understand what you mean for phone numbers, but I traditionally use
(xxx) xxx-xxxx
I only disagree with the last form of the website. The first two are somewhat difficult, I personally would prefer the former, however, some websites are only https://www and some are only http:// without the www. I guess the latter then would be the overall better option, though I would still dislike it =P.
I’m confused on which one you prefer for websites?
Sent from my iPhone using Tapatalk
Fred you have a good question and I think the bigger question will any of those not work. Both work for phone numbers I think I seen more (xxx) xxx-xxxx preferred but both work technically. The (xxx) is probably nicer since it better reflects area where you might still have to dial 7 digits bs 10 digits to make a call. Massachusetts you have to dial all 10 even if it is the same area code. I don’t know how many other areas are like that.
As for website I am just in favor of removing the http:// so a browser can detect of it is http vs https trivial and I am sure all versions work. Anyways as for national standards we will see but I don’t think it matters right now as long as the phone or link works.
(Also still waiting for clarification KTCAOP [emoji12])
Sent from my iPhone using Tapatalk
So phone numbers are not universal throughout the country and very much depend on the area code. The parentheses around the area code indicate that those digits may or may not have to be dialed, depending on where (with landlines) or what number (with cell phones) you’re calling from. Many area codes now require you to always dial the area code, even if it’s your own. Others do not not require the area code to be dialed if calling the same area code.
So for the former area codes, the double-hyphen format is correct, since all digits in the number must always be dialed. For the latter area codes, the parentheses format is correct since you may or may not need to dial the area code depending on where you’re calling from.
I have learned something today. Is there then a listing for which area codes should always need to be dialed?
And Mr. Ninja - there are a few websites that do matter whether you use http:// or https:// - though most websites are able to freely oscillate between the two and some websites do not have the www. prefix. Therefore while I dislike the “look” of the http:// or https:// for the websites, I do feel that it would be more appropriate to include them.
The app now clips the URL anyhow so if you enter [i]http://www.walmart.com/store/12345[/i] it’s going to only show walmart.com so I don’t see any reason to really worry about URL standardization.
It is also standardizing phone numbers so all of this may be a moot point and one less thing to worry about.
Area Codes Requiring 10 Digit Dialing:
https://www.nationalnanpa.com/enas/npasRequiring10DigitReport.do
This list will grow over time, for instance I know that 315 will get 10 digit dialing !soon
Cell phones are rapidly outnumbering landlines, and almost always require 10 digit dialing. The xxx-xxx-xxxx format is the easiest not only to read, but to use and validate in software applications.
As for URLs, any properly designed and implemented website and browser will properly respond to the simple domain.tld format. If they are SSL only, they should redirect without issue.
I have to agree. If we have to choose one format for practicality, use the double hyphen format. It definitely scales better into the future.
I will have to agree the double hyphen format is probably the easiest to read and most cell phones recognize this and can dial from it.
The web addresses are usually based upon servers and the sites they are from. So as long you get it from the site itself, there should be no issues or preferences.
I dump whatever’s on the website into the slots and hit the ‘Run WMEPH’ button. Good enough for me.
I think part of the issue is that there is no technical standard and a preference, a couple of locations have indicated in their wiki the allowed formats which are either (xxx) xxx-xxxx or xxx-xxx-xxxx but the more this discussion goes the more people sounds like xxx-xxx-xxxx makes more sense with increase usage of needing to dial 10 digits even locally and the fact that many cell phones will need to regardless, while ultimately a small issue as either functionally works for a new editor they could benefit from the guidance. I am a HUGE fan of WMEPH script, but that is restricted to rank 2 and above and the script should not be the way the decision is made, it should reflect the agreed upon practice and then act as a tool to help with the harmonization and formatting.
So maybe it is time to take this discussion and pursue it being added to the wiki
It seams there are stronger arguements for the xxx-xxx-xxxx format, with the understanding that in communities that still use 7 digit numbers they can utilize (xxx) xxx-xxxx if that is the desire of the state manager
as for webpage, I think that the guidance should be that the “http://” should be removed with the encouragement that www.waze.com format be the preferred (include the “www.” to help best identify it as a webpage)
I would have to agree with Johnsninja58. I think it would be best to take to the state manager’s to get this standardized and added to the wiki. This would allow for a more prompt action to this matter then to keep discussing this, since it seems there are more that are in agreement with the 10 digit format.
Also, the website’s should have a more common format. Unless there is a call for a HTTPS at the beginning. Some websites will not show unless this is present. So, with that being said, we should formalize all the rest unless it is a secure website.
Do not include www unless it is on the official site. it is a remnant of ancient internet history that is redundant. More and more network administrators are getting away from the www. Any site built by a competent hostmaster/webmaster will not need it. There are also more and more sites that use a different 3rd level, such as help.domain.tld or store.domain.tld. adding the www in front of these will generally not work.
Isn’t www meant for like a general public website, vs. other more-specialized services? www = World Wide Web, right?
It used to, before the internet was widely and publicly available. Internet access has become so pervasive in society that www has lost its value as a descriptor.
There used to be competing services like Archie and Gopher that are now long-defunct. In that day, a www subdomain made sense. Now it’s just an archaic holdover.
shakes cane get off my digital lawn!
This may be true in a good many cases, but there are times where it is required.
If you’re going to drop the “www.”, make sure it works without the “www.” before adding it to the place. If it doesn’t work without, but works with, ensure you keep the www. when putting it in.
Also, don’t add it without testing it. For instance “editor.waze.com” works to redirect you, but “www.editor.waze.com” does not (generates an SSL error).
Most sites will work the same with/without it, particularly small business. That’s not to say that ALL will, however.