<!DOCTYPE html><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /></head><body><div data-html-editor-font-wrapper="true" style="font-family: arial, sans-serif; font-size: 13px;">Hmm, my english skills leave me here;-) A kind of ontology is what I was aiming too. Not a date but data - in the sense of "information".<br>Did you get me wrong here or do I get you wrong...<br><br>Things like "audioInterfaceType" (jack, alsa...) and "audioPluginInterfaceType" (lv2, ladspa...) as well as applicationCategory (DAW, Effekt, Notation...) and all we find important would be extractable and searchable. (And Google and other search engines might make things more searchable as well...)<br><br>Holger<br><br>13. Januar 2017 14:40 Uhr, "Chris McKenzie" <<a target="_blank" tabindex="-1" href="mailto:%22Chris%20McKenzie%22%20<kristopolous@yahoo.com>">kristopolous@yahoo.com</a>> schrieb:<blockquote><div><div><div dir="auto">Also this is all arguably just props up anb insufficient solution.<div dir="auto"></div><div dir="auto">For me at least, the only reason I care about the date is that it's the best *indirect* indicator of whether something say, works with jack or lv2 or what have you.</div><div dir="auto"></div><div dir="auto">An ontology that would be far more useful than the indirect reporting of a date would be to (and some of this is done on the site)</div><div dir="auto"></div><div dir="auto">list the types of inputs (midi, jack, etc) and outputs of a program</div><div dir="auto"></div><div dir="auto">Whether they are meant for low latency "live" performances or not</div><div dir="auto"></div><div dir="auto">List what kind of plugin standards the thing works with</div><div dir="auto"></div><div dir="auto">Include, if possible, similar programs that may be more difficult or less difficult to learn, for people of various dedication and skill.</div><div dir="auto"></div><div dir="auto">The "ontology" part of this is important because ideally there could be a "web app" where you could string your stack together of different applications.</div><div dir="auto"></div><div dir="auto">These could also be used for demonstration purposes to help other people understand the various ways things can fit together.</div><div dir="auto"></div><div dir="auto">Because in practice, at least I have spent a lot of time in trying to learn what some software is good at, what it does for me, and how I could possibly connect it with everything else.</div><div dir="auto"></div><div dir="auto">These things are relatively simple to communicate but currently as far as I know, isn't happening.</div></div><div> <div>On Jan 13, 2017 5:19 AM, Chris McKenzie <<a target="_blank" href="mailto:kristopolous@yahoo.com">kristopolous@yahoo.com</a>> wrote:<br type="attribution"><br> <blockquote style="margin: 0 0 0 .8ex;border-left: 1px #ccc solid;padding-left: 1ex"><div dir="auto">Interesting idea. There's potentially a far quicker execution of it that doesn't need a buy in from everyone.<div dir="auto"></div><div dir="auto">You take all the repo links for the projects and then have a script that pulls them say twice a month. Then with a little git or svn magic you can find out if a newer release has been tagged and when it came out.</div><div dir="auto"></div><div dir="auto">Also you can piggy back on apt repos for other things</div><div dir="auto"></div><div dir="auto">apt-cache show Xxx</div><div dir="auto"></div><div dir="auto">Generally has a pretty good description if the wiki is lacking along with an up to date website.</div><div dir="auto"></div><div dir="auto">So I'm pretty sure some basic parts can be readily scripted within a few hours. There's various models I can think of so the autopopulation is useful and there when you need it but doesn't necessarily clobber human created content.</div></div></blockquote></div></div></div></div></blockquote></div></body></html>