Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Business.txt - Standard Proposal

github.com

Post reply on HN
Print view View original

91–100 of 115 posts

Re: Show HN: Business.txt - Standard Proposal

#91

Post by icebraining »

aw3c2 wrote: post #82
Terretta wrote: post #49

hostname.com/business.txt is wrong. You are supposed to use the /.well-known/ subfolder. http://tools.ietf.org/html/rfc5785 If you plan to implement a "standard" please try to review the RFCs that have covered this ground before. There's probably already a standard which may fit. If not, there's probably one that's close you could propose a change to. And if you're trying something genuinely new, you'll at least be o…

Interesting RFC. Do you know of any implementations of it?

There's a registry hosted by IANA: http://www.iana.org/assignments/well-known-uris/well-known-u...

Re: Show HN: Business.txt - Standard Proposal

#92

Post by zacharyvoase »

becomevocal wrote: post #46
pilif wrote: post #26

So more senseless errors in my error log and more traffic caused by robots requesting a file that doesn't exist? While I applaud the idea, can we please, please have a meta-tag or header that points to the location of this file if it's available? We don't need another favicon.ico nor robots.txt

Second. A meta-tag would make it easier for services to add in mass as well.

It's probably better to use a than a meta tag.

Re: Show HN: Business.txt - Standard Proposal

#94

Post by dangayle »

buro9 wrote: post #15

The idea of a text file at the root isn't a bad one, but the format of the document should be far more descriptive. Have you looked at http://schema.org/docs/schemas.html and the examples there? Everything in the example given is encapsulated by schema.org and that would describe it in a way that was unambiguous. I know that schema.org has been dismissed because "The problem is that it's too complicated for a non-dev…

That format is perfectly valid YAML, easily parsed, and just as easily created. It needn't be any more complicated than it is. I could make a WP plugin to support it within a few hours.

Re: Show HN: Business.txt - Standard Proposal

#96

Post by reinhardt »

So just skimming through the comments here, the "standard" alternatives to the proposed business.txt include (but are probably not limited to):

• HTTP Headers

• Meta-tags

• tags

• RFC 5785 (/.well-known/ folder)

• Microdata

• Microformats

• RDF Schema

No wonder we are in http://xkcd.com/927/ territory...

Re: Show HN: Business.txt - Standard Proposal

#97

Post by lost-theory »

aw3c2 wrote: post #82
Terretta wrote: post #49

hostname.com/business.txt is wrong. You are supposed to use the /.well-known/ subfolder. http://tools.ietf.org/html/rfc5785 If you plan to implement a "standard" please try to review the RFCs that have covered this ground before. There's probably already a standard which may fit. If not, there's probably one that's close you could propose a change to. And if you're trying something genuinely new, you'll at least be o…

Interesting RFC. Do you know of any implementations of it?

http://code.google.com/p/webfinger/wiki/WebFingerProtocol

Re: Show HN: Business.txt - Standard Proposal

#98

Post by fesja »

dangayle wrote: post #94
buro9 wrote: post #15

The idea of a text file at the root isn't a bad one, but the format of the document should be far more descriptive. Have you looked at http://schema.org/docs/schemas.html and the examples there? Everything in the example given is encapsulated by schema.org and that would describe it in a way that was unambiguous. I know that schema.org has been dismissed because "The problem is that it's too complicated for a non-dev…

That format is perfectly valid YAML, easily parsed, and just as easily created. It needn't be any more complicated than it is. I could make a WP plugin to support it within a few hours.

let's work on that WP plugin dan! ping me if you want

Re: Show HN: Business.txt - Standard Proposal

#99

Post by fesja »

alttab wrote: post #86
fusiongyro wrote: post #84

Earlier quoted context omitted.

How does your parser handle malformed entries? How do you handle text encoding? What are the valid attributes, what constitutes valid text? XML is unsexy, but it's only complex because it addresses these issues up front. A clever one-liner doesn't make these issues go away, it just postpones them to an inopportune time later.

I see your point. The original post doesn't address these issues, and I'm not sure it is ever designed to. If someone wanted to create a globally accessed, multi-language, all-encoding supported fully validated business information XML-RPC protocol they certainly wouldn't have arrived at "business.txt". The main problem it was trying to solve is to prevent business owners from having to update their information every…

I couldn't have said better!

Re: Show HN: Business.txt - Standard Proposal

#100

Post by Terretta »

aw3c2 wrote: post #82
Terretta wrote: post #49

hostname.com/business.txt is wrong. You are supposed to use the /.well-known/ subfolder. http://tools.ietf.org/html/rfc5785 If you plan to implement a "standard" please try to review the RFCs that have covered this ground before. There's probably already a standard which may fit. If not, there's probably one that's close you could propose a change to. And if you're trying something genuinely new, you'll at least be o…

Interesting RFC. Do you know of any implementations of it?

We use /.well-known/host-meta for OpenID discovery.

Explanation:

https://sites.google.com/site/oauthgoog/fedlogininterp/openi...

Post reply on HN