Tuesday, November 11, 2008
Friday, November 7, 2008
Muddiest Point for Nov. 11
In terms of a search engine, is indexing and "crawling" the same thing? Please explain.
Reading Notes for Week 10: Nov. 11
Web Search Engines: Part 1 and Part 2 by David Hawking
The main point of these two articles are the nature and infrastructure of a search engine. Oddly enough the author believes that search engines should not index every web page. From what I understood indexing every page slows down the search and the probability of fetching "low-value" pages happens continuously, however, indexing has proven to be an effective strategy to find information. I did not find his arguments convincing and crawling sounds a lot like indexing to me, which leads me to Part 2 of his article.
In Part 2 he feebly attempts to explain indexing alogrithim , I got to the second paragraph and reread it over and over again. This was difficult to comprehend.
Current Developments and Future Trends for the OAI Protocol for Metadata Harvesting by Sarah L. Shreeves, Thomas G. Habing, Kat Hagerdorn, and Jeffrey A. Young
An interesting article that discusses current developments in the Open Archives Institute and its projects. For example, the Protocol for Metadata Harvesting is a tool developed by the center to facilitate interoperability between different collection standards in XML, HTTP, and Dublin Core.
The main point of these two articles are the nature and infrastructure of a search engine. Oddly enough the author believes that search engines should not index every web page. From what I understood indexing every page slows down the search and the probability of fetching "low-value" pages happens continuously, however, indexing has proven to be an effective strategy to find information. I did not find his arguments convincing and crawling sounds a lot like indexing to me, which leads me to Part 2 of his article.
In Part 2 he feebly attempts to explain indexing alogrithim , I got to the second paragraph and reread it over and over again. This was difficult to comprehend.
Current Developments and Future Trends for the OAI Protocol for Metadata Harvesting by Sarah L. Shreeves, Thomas G. Habing, Kat Hagerdorn, and Jeffrey A. Young
An interesting article that discusses current developments in the Open Archives Institute and its projects. For example, the Protocol for Metadata Harvesting is a tool developed by the center to facilitate interoperability between different collection standards in XML, HTTP, and Dublin Core.
Friday, October 31, 2008
Muddiest Point for Week 9:
This may have a totally obvious answer but where is XML used? Is it in database design? Is XML currently used to create all new websites?
Reading Notes for Week 9: Nov. 2
The articles this week focused on extensible markup language XML. Compared to HTML, XML identifies the boundaries of every part of the document. HTML is primarily used for layout.
The Introduction to the Extensible Markup Language by Martin Bryan, provided an easy to understand overview of XML. The components of XML are believed to be its most desirable traits because it identifies the boundaries of every part of a document and can describe any logical text structure. The article also described how XML is used and this was where it became more difficult to follow.
A survey of XML standards:Part 1 by Uche Ogbuji, was more technical than I like and difficult to understand. Perhaps trying out XML first would clarify some confusion, I think the recommended introductions and tutorials for learning the new technology would also be helpful.
Extending Your Markup: An XML Tutorial by Andre Bergholz, points out that XML annotates text and with explicit information humans and computers can process XML easier. The structure of XML is described by the use of DTD, document type definitions. DTD lets users specify the set of tags, order of tags and attributes associated with each. The article also provided a helpful example of the markup language in a bibliography entry.
The Introduction to the Extensible Markup Language by Martin Bryan, provided an easy to understand overview of XML. The components of XML are believed to be its most desirable traits because it identifies the boundaries of every part of a document and can describe any logical text structure. The article also described how XML is used and this was where it became more difficult to follow.
A survey of XML standards:Part 1 by Uche Ogbuji, was more technical than I like and difficult to understand. Perhaps trying out XML first would clarify some confusion, I think the recommended introductions and tutorials for learning the new technology would also be helpful.
Extending Your Markup: An XML Tutorial by Andre Bergholz, points out that XML annotates text and with explicit information humans and computers can process XML easier. The structure of XML is described by the use of DTD, document type definitions. DTD lets users specify the set of tags, order of tags and attributes associated with each. The article also provided a helpful example of the markup language in a bibliography entry.
Subscribe to:
Posts (Atom)