Thanks for your kind comment. The standardised use cases of NUM (currently contact data, images [gravatar for domains] and some others) would allow you as a sm

Thanks for your kind comment. The standardised use cases of NUM (currently contact data, images [gravatar for domains] and some others) would allow you as a small website operator to publish any public data that you wanted to be machine-readable. I think your question might be how to use NUM to serve out your small text-file snippets? If so, NUM could be used for that. NUM lookups are based on URIs, eg: num://numexample.com:1 In this example module 1 is contact data and lookups for this uri involve a query to the dns for: dig 1._num.numexample.com TXT If instead of publishing contact data you wanted to publish general purpose data you can do this using “module zero”. For example data could be published form the NUM URI num://numexample.com:0/foo The DNS location is: foo.0._num.numexample.com