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

Show HN: An API for scraping recipe web pages

choppingboard.recipes

Post reply on HN
Print view View original

21–30 of 113 posts

Re: Show HN: An API for scraping recipe web pages

#21

Post by Ariana454 »

cbcoutinho wrote: post #9
simooooo wrote: post #7

Earlier quoted context omitted.

MyFitnessPal has the same issue where the quantity values mixed between different units, but also between volume(cup) vs weight(grams). So its a pain in the neck to know how heavy a cup of pasta is. I can see the same issue arising with this tool.

That's the beauty of 'user-generated content'. You can scan whatever you want, and if it's not in their system you can just put the details in yourself. That includes choosing what a portion is

I have created $18376 in one month by merely doing simple on-line work from home. everybody needs to become loaded presently and wishes to live a life that we've an inclination to ascertain in barely dreams. This job can fulfil your dreams just like ME. everybody ought to do that job presently and start earning from home directly. merely open this electronic computer in your browser by copy and paste then follow the instruction to urge started presently...... « Back

⇝⇝⇝http://www.joinmate2.com

Re: Show HN: An API for scraping recipe web pages

#22

Post by blackskad »

philbarr wrote: post #16
Freak_NL wrote: post #6

Earlier quoted context omitted.

Whenever I read a recipe online I get this nagging feeling that there should be some widely used open standard for describing recipes that can do all sorts of awesome stuff (like a web crawler such as DuckDuckGo being able to answer "I have a pineapple, cream, and the usual pantry basics, what can I cook?"), but this seems to go directly against the business models of the big recipe sites, so it will not likely see m…

I thought once about doing a "flavour graph" where people could go on and add what they thought were good flavours to mix together. The more people added the same flavours, the stronger the edges between nodes would get. I'd probably have to separate it somehow by geographic region, as tastes vary, but in the end you should have a good approximation of "what goes with what".

There's a Belgian startup that matches flavors with a scientific method. https://www.foodpairing.com/en/home

Re: Show HN: An API for scraping recipe web pages

#23

Post by askvictor »

oneeyedpigeon wrote: post #4

This really seems to be an exercise in 'structuring recipe data' rather than the ins-and-outs of scraping. Seems like a much-needed task; is there anything approaching a 'standard' for recipe data already? "ingredients": [ "600g pineapple, peeled, chopped" ] This seems like a prime candidate for improvement; something like the following would seem to be more useful: "ingredients": [{ "ingredient": "pineapple", "quant…

Two things that would be so nice would be easy scaling, and unit conversion (even better if that's automatic)

Re: Show HN: An API for scraping recipe web pages

#24

Post by [deleted] »

blackskad wrote: post #22
philbarr wrote: post #16

Earlier quoted context omitted.

I thought once about doing a "flavour graph" where people could go on and add what they thought were good flavours to mix together. The more people added the same flavours, the stronger the edges between nodes would get. I'd probably have to separate it somehow by geographic region, as tastes vary, but in the end you should have a good approximation of "what goes with what".

There's a Belgian startup that matches flavors with a scientific method. https://www.foodpairing.com/en/home

[deleted]

Re: Show HN: An API for scraping recipe web pages

#25

Post by blackskad »

Jaruzel wrote: post #19
oneeyedpigeon wrote: post #4

This really seems to be an exercise in 'structuring recipe data' rather than the ins-and-outs of scraping. Seems like a much-needed task; is there anything approaching a 'standard' for recipe data already? "ingredients": [ "600g pineapple, peeled, chopped" ] This seems like a prime candidate for improvement; something like the following would seem to be more useful: "ingredients": [{ "ingredient": "pineapple", "quant…

There is a standard of sorts, if you trust Google: https://developers.google.com/search/docs/data-types/recipes

This standard is not unique to Google. It's part of the Schema.org initiative to add semantics to the web. The full definition is here:

http://schema.org/Recipe

The biggest problem with it, imho, is the lack of a proper definition of ingredients. An ingredient is just a plain string containing the unit, amount and name and sometimes an extra note. Having a quadruple instead of a string would make this standard a lot more useful.

Re: Show HN: An API for scraping recipe web pages

#26

Post by kozhevnikov »

oneeyedpigeon wrote: post #4

This really seems to be an exercise in 'structuring recipe data' rather than the ins-and-outs of scraping. Seems like a much-needed task; is there anything approaching a 'standard' for recipe data already? "ingredients": [ "600g pineapple, peeled, chopped" ] This seems like a prime candidate for improvement; something like the following would seem to be more useful: "ingredients": [{ "ingredient": "pineapple", "quant…

Back when microformats were all the rage there was h-recipe

http://microformats.org/wiki/hrecipe

Re: Show HN: An API for scraping recipe web pages

#27

Post by blackskad »

ygra wrote: post #8
oneeyedpigeon wrote: post #4

This really seems to be an exercise in 'structuring recipe data' rather than the ins-and-outs of scraping. Seems like a much-needed task; is there anything approaching a 'standard' for recipe data already? "ingredients": [ "600g pineapple, peeled, chopped" ] This seems like a prime candidate for improvement; something like the following would seem to be more useful: "ingredients": [{ "ingredient": "pineapple", "quant…

What I'm missing the most in this context is for how many people those ingredients actually are. That's necessary if you want to scale the recipe to fewer or more people.

It's kinda weird that it's not included yet. The schema.org spec has a field 'recipeYield' specifically for this purpose and it's present in the meatball example on the site. It should be quite easy for the author to add it.

Re: Show HN: An API for scraping recipe web pages

#28

Post by patrickdavey »

oneeyedpigeon wrote: post #4

This really seems to be an exercise in 'structuring recipe data' rather than the ins-and-outs of scraping. Seems like a much-needed task; is there anything approaching a 'standard' for recipe data already? "ingredients": [ "600g pineapple, peeled, chopped" ] This seems like a prime candidate for improvement; something like the following would seem to be more useful: "ingredients": [{ "ingredient": "pineapple", "quant…

Heh, I once tried to make a DSL to cope with recipes from cookingforengineers.com e.g. their lovely recipe cards [1] . I totally failed to make anything decent!. The combining of multiple steps etc. was just painful!. In the linked site above, that recipe is so straight forward, I'd love to see how it copes with [1] below.

[1] http://www.cookingforengineers.com/recipe/127/Shepherds-Pie-...

Re: Show HN: An API for scraping recipe web pages

#29

Post by rocannon »

Freak_NL wrote: post #6
oneeyedpigeon wrote: post #4

This really seems to be an exercise in 'structuring recipe data' rather than the ins-and-outs of scraping. Seems like a much-needed task; is there anything approaching a 'standard' for recipe data already? "ingredients": [ "600g pineapple, peeled, chopped" ] This seems like a prime candidate for improvement; something like the following would seem to be more useful: "ingredients": [{ "ingredient": "pineapple", "quant…

Whenever I read a recipe online I get this nagging feeling that there should be some widely used open standard for describing recipes that can do all sorts of awesome stuff (like a web crawler such as DuckDuckGo being able to answer "I have a pineapple, cream, and the usual pantry basics, what can I cook?"), but this seems to go directly against the business models of the big recipe sites, so it will not likely see m…

Try IBM's Chef Watson: https://www.ibmchefwatson.com/tupler

Re: Show HN: An API for scraping recipe web pages

#30

Post by JepZ »

askvictor wrote: post #23
oneeyedpigeon wrote: post #4

This really seems to be an exercise in 'structuring recipe data' rather than the ins-and-outs of scraping. Seems like a much-needed task; is there anything approaching a 'standard' for recipe data already? "ingredients": [ "600g pineapple, peeled, chopped" ] This seems like a prime candidate for improvement; something like the following would seem to be more useful: "ingredients": [{ "ingredient": "pineapple", "quant…

Two things that would be so nice would be easy scaling, and unit conversion (even better if that's automatic)

Well, as surprising as it might sound there seem to be many units in the kitchen which are not so easy to convert. One example: How many milliliters does a table spoon have? Google says 14.7868 (american table spoon). I have read from 6 to 25... I mean the problem is that the people who writes those recipes use different definitions of the same unit. And that is just one example. How should you convert units which are so different between different authors?
Post reply on HN