Vocabulary as a Central Concept in Information Science, Michael Buckland (1999)
The role of classification in knowledge representation and discovery, BH Kwasnik – Library Trends, 1999
One good point in the Buckland article was that vocabulary can differ between those who are doing the cataloging, the authors and the searcher, even if everyone is within the same field. I’ve read some about these differences before, but they almost always seem to take the form of novice searcher vocabulary vs. expert author vocabulary or natural searcher vocabulary vs. structured system vocab. Those are probably the most clear ways to look at these distinctionsâ€”to tell you the truth looking at subtle differences between five different vocabularies does not seem like that much fun to me.
This article gets back to some of the same points we’ve already discussed in class when talking about synonym rings and taxnomies. Even through the author comes at it from a vocabulary point of view, he’s saying the same things everyone else is. If your users want to search for â€œVietnam Warâ€ but your system uses â€œVietnam Conflict,â€ without pointing the user in the right direction, no purpose has been served. You can be as correct and specific in your phrasing as you want but that’s no guarantee you’ll have a usable system.
The Kwasinik reading was really good at pointing out the strengths and weaknesses of hierarchies, trees and other organization schemes. In doing the AG assignment I ran into the â€œLack of complete and comprehensive knowledgeâ€ barrier quite often. That’s one of the biggest problems with not just hierarchies, but any project like this where we have some knowledge of the domainâ€”everyone has seen greeting cardsâ€”but not of the entire body of AG’s product line or even a representative subset. I wouldn’t want to construct a taxonomy of content object before people started entering dataâ€”I would have it be built as the database grew, with specific people in charge of keeping it consistent.
Creating a Controlled Vocabulary
Â Fast, Karl, Fred Leise and Mike Steckel (2003)
This was a good rundown of the general process of creating a controlled vocabulary, but a lot of this seems pretty apparent to me. I guess I shouldn’t assume that this stuff is obvious, though, given how many companies make web sites or intranets without really bothering to find out how their users use vocabulary for their domain, or even establishing a vocabulary, for that matter.
The two most important points, to me, are number 5, â€œEstablish a record of the rules you are using if you are creating a large thesaurusâ€ and number 8, â€œGo back and refine. What can be improved?â€ In fact I think the whole notion of controlled vocabulary is misguided if there’s no clear rationale for it and attempts to update and maintain the terms at all times. Language in any field is constantly changing, and the pace of change is always accelerating. Anyone who was building a directory of Internet services would have left off the World Wide Web in 1989, and any list about self-publishing on the web would probably have left off the term â€œblogâ€ in 1998. How useful would those pick lists be today?
Controlled vocabulary can be damaging if there’s no mechanism for change, or that mechanism is left unused. I don’t know why, but humanity seems to have some undying urge to compile things around ourselves into grand lists and hierarchies that are supposed to encompass all of what is or ever has been, ignoring our complete ignorance of what the future will bring. It’s not that classification in and of itself is bad, it’s that there’s a tendency to get to the â€œendâ€ and say, â€œthere, it’s done, and set in stone forever.â€
ASP.NET and PHP
Virtually every medium or large web site now uses some kind of server-side scripting to generate web pages and interactive features instead of static html. A number of technologies are used for this purpose, including PHP, ASP.NET, Perl, ColdFusion, and JSP. This paper will look at Microsoft’s ASP.NET and an open-source alternative, PHP, and compare them in terms of cost, performance, support, features and ease of use for web development.
Comparing ASP and PHP can be difficult because they are not exactly the same class of software. PHP is simply a server-side scripting language. The PHP homepage describes it as â€œa widely-used general-purpose scripting language that is especially suited for Web development and can be embedded into HTML.â€1 ASP, more properly ASP.NET, is not a language per se, and allows users to program Microsoft Internet Information Services (IIS) in Jscript, Vbscript, and C#, among others. ASP.NET is a little harder to define than PHP. ASP stands for Active Server Pages, and .NET, according to Microsoft, â€œis a set of Microsoft software technologies for connecting information, people, systems, and devices. It enables a high level of software integration through the use of Web servicesâ€”small, discrete, building-block applications that connect to each other as well as to other, larger applications over the Internet.â€2
Despite major structural differences, the two can and should be compared because they can be used to create the same kinds of medium-to-large, dynamic, often database-driven web sites. Server-side scripting allows sites to easily edit and update information, offer interactive features like forums and personalization, and track user traffic.
Â Continue reading