Show HN: Schema.org with GitHub and scripts: A tool to make data more useful
Hey guys, looking for feedback on the essential concept of the idea. I&#x27;d like to hear from real programmers whether they understand what DitaBase is and whether they think they would use, either now or in the future.<p>It&#x27;s been difficult to explain DitaBase, and I still don&#x27;t know if that&#x27;s because its actually a terrible idea, and much too complicated. If it is a good idea, then I think sometimes good ideas look complicated like this until people figure out how best to explain them. You wouldn&#x27;t have expected the internet, or say, object orientation, to be instantly and clearly obvious what it is when they were first being talked about, and that is how I see DitaBase.<p>Its basically that DitaBase is 4 essential concepts: schemas, validation scripts, conversion scripts, and public version control. If you take any single one out, then the really useful part, the dit file type, doesn&#x27;t work. But it&#x27;s also true that these concepts have never been applied in this way (that I have found), and so there isn&#x27;t any default, easy language to call upon to explain DitaBase to people readily and easily.<p>The answer to the question &quot;What is DitaBase?&quot; feels like it has to be &quot;1, 2, 3, 4&quot; where I list out the essential components. Perhaps, its a &quot;common language for data&quot;, or a &quot;general data accuracy system&quot;, but those concepts sound totally meaningless by themselves.<p>I really would love to hear some feedback on how you understand the idea and whether my thinking on this is sound, or if I am totally off base, being caught up too close to the idea.