2 ms·
Thinking about this a little more -- I'm not sure anyone is asking for something "more efficient" than html - at least in the USA, we're no longer bandwidth str
by bfung 5y ago
Thinking about this a little more -- I'm not sure anyone is asking for something "more efficient" than html - at least in the USA, we're no longer bandwidth strapped. I thought the internet in UK was decent enough - at least when I visited in 2016 it was good enough to load google maps on 4G.
For semantic parsing, probably went too far down semantic web tags. A simple "tel:" link works for most people and there's phone integration already. ex:
<!DOCTYPE html>
<title>My co</title>
<a href="tel:123-456-7890">123-456-7890</a>
(not well-formed, but it works!) - no js, no json required - good ole' html.
- elliottinvent 5y agoThanks for coming back to this. Internet speeds in the UK are comparable with the US. Many parts of the world are not as fortunate, with bandwidth severely limited and extortionate data charges (unless it’s Facebook data, then it’s free?!). However, NUM doesn’t exist because the world has a bandwidth problem. You’re right of course that it’s possible to provide machine readable contact data on the web. NUM doesn’t exist because it’s not technically possible to do the same thing with data on the web. NUM exists because after 15 years of the semantic web, this data simply isn’t available for most businesses on the web. Even large businesses - take any example from the homepage of the demo site CompanyDirectory.uk, and see how they’ve implemented semweb standards. How they list their phone numbers for example. It’s an utter mess. Good luck to anyone trying to build a reliable service on top of that data.