31–40 of 115 posts
Regardless of the format of the content, I think that it'd be nice if files like this would be placed in /.well-known/[standard] in accordance with http://tools.ietf.org/html/rfc5785 There are already too many magical files cluttering up the root.
Regardless of the format of the content, I think that it'd be nice if files like this would be placed in /.well-known/[standard] in accordance with http://tools.ietf.org/html/rfc5785 There are already too many magical files cluttering up the root.
Is it being implemented? I mean, I can find http://www.ietf.org/robots.txt but not http://www.ietf.org/.well-known/robots.txt
Great idea. Added one for our company. It took just a couple of minutes. http://pierlis.com/business.txt
My browser is failing to render the address properly, it reads as "Poissonnière" so the diaresis is breaking. Probably need to double-check how you serve the file, and make sure the charset and encoding match.
Great idea. Added one for our company. It took just a couple of minutes. http://pierlis.com/business.txt
This is why I like the business.txt idea. Microformats or microdata, however appropriate and simple, are still one level of abstraction above this idea.
I came to this post 45 seconds ago, looked at GH, and could explain what this is for and how it works. That's saying something.
Wouldn't it be easier if this were XML instead of plain text? I assume the goal is that software can easily interpret the data.
We want to be a human friendly file. If we had a JSON or XML file, it would be too complicated for a non-developer to write or read it. On this way, I think it doesn't matter if the website is done in wordpress, drupla, static files, flash, etc. It's just a simple file. Also, we are following the same pattern as the robots.txt file.
I propose:
[company/product name] (URL)
score: X/Y
[review text]
--
[next review...]
Frank's Pizza Place (http://franks.geocities.com)
score: 8/10
Good service and food. Doesn't accept credit cards.Earlier quoted context omitted.
My browser is failing to render the address properly, it reads as "Poissonnière" so the diaresis is breaking. Probably need to double-check how you serve the file, and make sure the charset and encoding match.
Yeah, '; charset=utf-8' has to be appended to the Content-Type header.
i'd prefer schema.org (or json equivalent). and a gui editor for less technical person.
I think this usecase is already covered very well by microformats and the various metadata standards that already exist and are supported by Google, Facebook et al. I'm not sure the argument that these are too complicated for non-developers really works here, after all uploading a file to the root of a web directory is likely also too complicated...
Wouldn't it be easier if this were XML instead of plain text? I assume the goal is that software can easily interpret the data.