Comments on: Feature requests for a vocabulary editor http://www.peterkrantz.com/2008/feature-requests-for-a-vocabulary-editor/ A blog about technology, visualization, music and unmanned vehicle experiments Wed, 17 Feb 2010 23:48:37 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Peter http://www.peterkrantz.com/2008/feature-requests-for-a-vocabulary-editor/comment-page-1/#comment-2536 Peter Sun, 10 May 2009 15:46:39 +0000 http://www.peterkrantz.com/?p=160#comment-2536 The <a href="http://drupal.org/project/neologism" rel="nofollow">Neologism Drupal module</a> makes some of the things that you describe already possible: you can create vocabularies, classes and properties in the same way as creating pages, blog posts etc, and the vocabulary will be instantly online. It is implemented for Drupal and using CCK, which gives you a lot of freedom in extending this, and in creating a nice workflow for the vocabulary author/editor. The Neologism Drupal module makes some of the things that you describe already possible: you can create vocabularies, classes and properties in the same way as creating pages, blog posts etc, and the vocabulary will be instantly online. It is implemented for Drupal and using CCK, which gives you a lot of freedom in extending this, and in creating a nice workflow for the vocabulary author/editor.

]]> By: Bryan http://www.peterkrantz.com/2008/feature-requests-for-a-vocabulary-editor/comment-page-1/#comment-2294 Bryan Wed, 23 Jul 2008 05:50:18 +0000 http://www.peterkrantz.com/?p=160#comment-2294 A key part of maintaining a vocabulary is some sort of version control. I want to know what has changed in the vocabulary since last time I looked at it. For me, that's a key component of the tool you describe. A key part of maintaining a vocabulary is some sort of version control. I want to know what has changed in the vocabulary since last time I looked at it. For me, that’s a key component of the tool you describe.

]]> By: Richard Cyganiak http://www.peterkrantz.com/2008/feature-requests-for-a-vocabulary-editor/comment-page-1/#comment-2285 Richard Cyganiak Mon, 30 Jun 2008 09:48:18 +0000 http://www.peterkrantz.com/?p=160#comment-2285 Peter, have a look at <a href="http://code.google.com/p/neologism/" rel="nofollow">Neologism</a>. It's designed to do exactly what you asked for. It's still very much in alpha, but already supports all your requirements except #4 and PDF export. We currently aim mostly at users who already have some RDF background, but if that free time in August comes along for you, please get in touch and tell us how we can improve the learning curve! Peter, have a look at Neologism. It’s designed to do exactly what you asked for. It’s still very much in alpha, but already supports all your requirements except #4 and PDF export. We currently aim mostly at users who already have some RDF background, but if that free time in August comes along for you, please get in touch and tell us how we can improve the learning curve!

]]> By: Erik Wilde http://www.peterkrantz.com/2008/feature-requests-for-a-vocabulary-editor/comment-page-1/#comment-2283 Erik Wilde Wed, 25 Jun 2008 05:44:07 +0000 http://www.peterkrantz.com/?p=160#comment-2283 i like the way the question is phrased. it talks explicitly about "controlled vocabularies", so there really is no need to refer to RDF (you can if you want to, but that's a much bigger and more complicated gun than you will ever need). in the world of vocabularies, there are controlled vocabularies, taxonomies, thesauri, and ontologies. most people don't really need anything more complicated than taxonomies, anything beyond that not only is very hard to build, it is even even harder to maintain and to understand. we just looked a bit at the state of affairs when it comes to defining vocabularies (<a href="http://dret.typepad.com/dretblog/2008/06/xml-fever.html" rel="nofollow">here is my blog post advertising our article</a>), and it's true that there is a lack of tools, so people often fallback to the few tools available, which are complex and complicated. i do agree that there is a lack of good support for the humble vocabularies most users want to create. have you looked at the available tools for topic maps? i don't know a lot about these, but maybe they offer some of these features. but then again, they're probably not free... building something according to you wish list really should not be too hard, i guess the hard part in a way would be to just stick to these and not to say "and while we're at it, let's add all these semantic web things as well." that being said, such a tool of course could and should easily export everything as RDF/XML, N3, DTD, XML Schema, CSV, PDF, HTML, and many other formats - there are only few data formats that can not somehow represent controlled vocabularies, i guess. i like the way the question is phrased. it talks explicitly about “controlled vocabularies”, so there really is no need to refer to RDF (you can if you want to, but that’s a much bigger and more complicated gun than you will ever need). in the world of vocabularies, there are controlled vocabularies, taxonomies, thesauri, and ontologies. most people don’t really need anything more complicated than taxonomies, anything beyond that not only is very hard to build, it is even even harder to maintain and to understand.

we just looked a bit at the state of affairs when it comes to defining vocabularies (here is my blog post advertising our article), and it’s true that there is a lack of tools, so people often fallback to the few tools available, which are complex and complicated.

i do agree that there is a lack of good support for the humble vocabularies most users want to create. have you looked at the available tools for topic maps? i don’t know a lot about these, but maybe they offer some of these features. but then again, they’re probably not free…

building something according to you wish list really should not be too hard, i guess the hard part in a way would be to just stick to these and not to say “and while we’re at it, let’s add all these semantic web things as well.” that being said, such a tool of course could and should easily export everything as RDF/XML, N3, DTD, XML Schema, CSV, PDF, HTML, and many other formats – there are only few data formats that can not somehow represent controlled vocabularies, i guess.

]]> By: William Vambenepe http://www.peterkrantz.com/2008/feature-requests-for-a-vocabulary-editor/comment-page-1/#comment-2282 William Vambenepe Wed, 25 Jun 2008 04:22:01 +0000 http://www.peterkrantz.com/?p=160#comment-2282 I want it too! I'll come back to check on this entry later, in the hope that someone enters a comment that points to an answer. I want it too! I’ll come back to check on this entry later, in the hope that someone enters a comment that points to an answer.

]]> By: Bill de hOra http://www.peterkrantz.com/2008/feature-requests-for-a-vocabulary-editor/comment-page-1/#comment-2281 Bill de hOra Tue, 24 Jun 2008 22:36:51 +0000 http://www.peterkrantz.com/?p=160#comment-2281 Peter, PloneOntology: http://www.dehora.net/journal/2008/06/24/controlled-semantic-vocabularies-tool Peter,

PloneOntology: http://www.dehora.net/journal/2008/06/24/controlled-semantic-vocabularies-tool

]]>