#joshnussWas wondering about adding a new mcroformat for receipts
#joshnusshow would I go about proposing it? or maybe it's something you've already considered
#[jgmac1106]Joshnuss the way to start with new properties is to first see if you can get it to fit into existing properties.. Then second consider any consumers... Who has a tool or need to read your h-receipts
#[jgmac1106]And a huge welcome joshnuss. What is your website?
#joshnussh-receipt could be like an aggregation of existing standard. h-product, h-geo h-address. Probably will be missing some props. It should work from anaything from airline tickets (containing media+calendar events) to e-commerce purchase, but also consumables where the receipt contains expiration data.
#joshnussI really wish credit card/payment processors to accept a standard format for receipts. There's a wealth of data that is being turned into PDFs (essentially bitmaps)
#[jgmac1106]I am pretty new too but I think the h level is a top level event, something to follow... There wouldn't be consumers for what you propose
#joshnussIf receipt data could be standardized, imagine buying fast food and have the receipt go to your expenses and nutrition data to a fitness app
#joshnussok, cool, thanks for the help, I will take a look
#[jgmac1106]... Yeah we find it way more sustainable to build small for ourselves rather than worry about bout masses
#[jgmac1106]Okay that is a bit different and some people do track food and nutrition
#[tantek]joshnuss welcome, and thanks for bringing up receipts! It certainly sounds like an interesting opportunity, and as others have brought up, there are folks publishing receipt-like things in the IndieWeb community so that might be a good place to start gathering existing online examples
#joshnussthanks @tankek, i will poke around a bit more, but yeah it sounds like a lot is already existing
#[tantek]It would be good to document some consuming code use-cases, so that there is a chance of an ecosystem actually forming for the data to be produced and consumed.
#joshnusstotally, i'm gonna put together a blog post with some examples/use-case
#[tantek]the problem was that Google implemented consuming code behind closed doors, and didn't really participate much in attempting to iterate on microformats (beyond some on hReview, and helping driving hReview-aggregate)
#[tantek]I expect that as microformats2 usage grows, Google will implement that too, since they generally pay attention to publishing patterns on the web. That's good, yet means we cannot depend / wait for them to collaborate to actually help create microformats or improve them.
nitot, [grantcodes], [sebsel], [Rose] and KartikPrabhu joined the channel
#joshnussZegnat: oh wow, that is super interesting, thx for sharing
KartikPrabhu joined the channel
#jamietanna[m]Are p-categories space separated? And is there a distinction between categories and tags?
#Zegnatp-category is not space separated, no. You could have categories/tags that include a space in their name.
#Zegnatmicroformats has no disctinction between categories and tags. The field name used by h-entry is `category`, and people tend to use that for tags on their posts
#Zegnatjoshnuss: there may be some spoken content about his ideas in some of the Berlin live streams, I can’t recall. I was there in person which is why I know about it.
#jamietanna[m]Thanks zegnat - so would it be comma separated? Or would you have multiple p-category elements, one per category?
#ZegnatYou would have multiples. The p-category contains a string, and that string is a single category. microformats does not define any postprocessing of any kind for it
#jamietanna[m]Cool, thanks! Wasn't 100% from reading the wiki, so wanted to check :)
KartikPrabhu, nitot, ben_thatmustbeme, [jgmac1106], [Rose], [grantcodes], [schmarty], dougbeal|mb1, [kevinmarks], jackjamieson, barpthewire, [eddie], [tantek], gRegorLove and chrisaldrich joined the channel; mblaney left the channel