What are /r/semanticweb's favorite Products & Services?

From 3.5 billion Reddit comments

Take a look at this guide. It gives a good overview of what an ontology is, and an example of how to build one using Protege (which is a great open source tool for building ontologies).

I previously installed Protege, but as can be seen from this screenshot, it's way too complicated and requires deep knowledge of the standards.

http://protege.stanford.edu/assets/img/screenshots/desktopprotege-screenshot-1.jpg

The two big ones will be DCAT and PROV-O. DCAT will help provide the description of the systems and services that originally held the data and PROV-O will describe how that data was used to create other data as it passed from system to system. Don't assume this will be a quick thing though - PROV-O in particular is quite rich and capable of describing a huge amount of lineage metadata when it is used right and with rigor. I recommend this book and some time to digest it all.

Swi-Prolog is a version of prolog that is free and open source. If you have not programmed in Prolog before it is a bit of mind bender. But it is very powerful and very good for the semantic web. Swi-prolog includes a number of ways to reason with RDF data.

http://www.swi-prolog.org/web/index.txt

Oh I see, thanks for the quick reply!
The conceptual distinction I was making was food processor = tool, baking sheet = supply, rolled oats = ingredient.

Here it is with your suggestions:

"tool": [ { "@type": "HowToTool", "name": "food processor", "requiredQuantity": 1 }, { "@type": "HowToTool", "name": "baking sheet", "requiredQuantity": 1 } ], "supply": [ { "@type": "HowToSupply", "name": "rolled oats", "requiredQuantity": { "@type": "QuantitativeValue", "value": 100, "unitCode": "GRM" } } ], "recipeIngredient": [ "100g rolled oats" ]

> trade-off

IMHO ease of authoring should be handled by building tools such as integrations with IDEs. People shouldn't have to write this kind of stuff without helper features like code intelligence (autocomplete, inline docs etc. – check out Sourcegraph and Tudor Gîrba's Glamorous Toolkit). Capturing reality is the whole point of having these standards. Sites and plugins are writing their own custom code to handle unit conversion for these dumb text strings. Unit conversion is not an edge case. /rant

heya, quick tip - remove `.../ref=......` from that URL, you're just publishing your own private amazon tracking data.

https://www.amazon.co.uk/Programming-Semantic-Web-Flexible-Applications-ebook/dp/B002L4EXE2 .