It looks like you're new here. If you want to get involved, click one of these buttons!
Karsten Luecke has a PDF with some helpful tips regarding font (family) naming: http://www.kltf.de/kltf_otproduction.htm
I've been thinking about easy ways to push updates into the name check tool instead of pulling updates from every foundry/type designer website.
All available (common) techniques of publishing machine-readable data (RSS, RDF, microformats, XML and so on) require specific software or a developer to implement it.
humans.txt uses a simple text file located on the server which can be created using a simple text editor, but it isn't structured since it's meant to be read by humans not software.
Nevertheless having a simple text file like this in a CSV (comma separated) manner could be one approach. Such a file can be easily created even without installing specific software on the server or requiring a developer. Basically you could create a list of all faces available from your foundry in any OpenOffice or Google Docs and export it to csv and upload it to your web server root directory.
Regarding the structure I would suggest having only basic meta information included like:
Font nameFoundry nameDesigner(s) namePublication dateWeb font available yes/noLicense (Libre or not)
The foundry name would be required even the »feed« (file) is located on your domain name and the foundry name can be easily guessed, but distributors sell fonts from various foundries. Also the foundry name cannot always be determined from the foundry's website domain name/URL.
Besides the name check tool other web sites could of course consume this feed to gather information about new type face releases.What do you think? Anyone wants to join by publishing such a feed?Suggestions for a name: fontfeed.txt Ha, no, better something like fontlist.txt?