Orcmid's Lair |
||||
|
|
2004-03-13Augmented Plain Text (APT). This is a little scheme created by Murray Altheim as a way of doing text/plain with a kind of markup that that can be mapped to XHTML as part of a project he is doing. I am interested in this kind of markup for WikiText. Main Page - Wikipedia. I like this project and also how MediaWiki is used to operate the site. There are things I would tweak, and I will get an opportunity with nfoWare. Meanwhile, I will hang out here a bit. I find that I prefer to use <http://wikipedia.org/> for my link, even though I am refering to the English-language main page. One thing for me to work on is to have versioning and provenance work more smoothly. GNU Free Documentation License - Wikipedia. I just looked this over because it displeases some. I think there is a complaint about preservation of provenance and attribution. It is perhaps too specific on how attribution is to be preserved when, for example, adapting an article. I think it is worthy, and I don't see why I can't operate consistently with it in nfoWare and elsewhere. Searching below the TideACM News Service -- In Search of the Deep Web. This blurb about a 2004-03-09 Salon.com article by Alex Wright doesn't make clear, for me, how the use of deep web engines will improve the situation for electronic journal subscriptions that require some sort of access security to protect their content, and it being locatable via Deep Web searching. The blurb at 2004-03-11WikipediaUser talk:Orcmid - Wikipedia. Oh my, I had this craving to mash on the definition of algorithm, so I registered myself and then I looked and decided it would take more work than that, so I will desist. Now I have the prospect of editing myself, which is an interesting problem. So far, there is nothing here. Well, I will put a little link. After putting some introductory material about myself here, I learned that I had done it in the wrong place. User:Orcmid is where information goes, naturally, about user Orcmid. User_Talk:Orcmid is where discussion of the User:Orcmid (page) goes. Different thing, and interesting in that, to some degree, Wikipedia has found ways to deal with talking about a subject and talking about the talking about a subject. Because this is a Wiki and everything is a text, everything is "talking about." This discussion model works very simply. I would like it to be a little more formalized so that one could tell the discussants and who has said what a little more clearly. And in bootstrapping, that is probably not so necessary. The trick is to provide more automatic organization and indicators to readers without straight-jacketing the contributors. I suppose one discovers the proper balance by trying it out and correcting as we add and remove various approaches. The key thing on revisions is to preserve earlier work. These are all interesting things to deal with. Heuristic - Wikipedia. Well, I got distracted and while not being that pleased with how Wikipedia defines algorithm, I thought I would look at heuristic, and I find that more useful. I have some work to do here to clean things up. Meatball Wiki: MediaWikiThis article/wiki page on MediaWiki is interesting in terms of the discussion that is spread through it and some ideas about preferences. What I find interesting is that MediaWiki tends to be good for collaborative editing of reference material, which is the kind of thing I want on nfoWare. I also subscribe to the idea of not requiring CamelCase, and separating discussion and content in a clear way. Meatball Wiki: InternalTransclusion. Here's a little more about transcluding in a Wiki. Others use different styles, sometimes tying it to the scheme for links. Of more-than-passing interest is the reference to how MediaWiki uses this to incorporate boilerplate and, I suppose, templates. This seems to answer a question about something I noticed while editing a Wikipedia page. XML.com: Transclusion with XSLT 2.0 [Jul. 09, 2003]. Here's a Bob DuCharme column that illustrates transclusion of fragments of other documents and uses what I concur are the most valuable plaintext files on the Internet -- IETF RFCs. On the other hand, W3C specifications are pretty valuable, and I like this approach in their regard too. So far, I have found it necessary to mark up a separate copy myself, doing what I can to preserve its provenance. I need to come back to this. Meatball Wiki: TransClusion. A Wiki page about Transclusion, with more than I need and also some practical advice. What is activeRenderer ?. Well, OK, I think I have the idea. It is a Radio plug-in, but then what the heck. activeRenderer News. Hmm, curioser and curioser. This is like a blog, and it is at the root of the activeRenderer site. I shall nose around. Leverage Outline Transclusion. Hmm, more and more interesting with regard to the transclusion of outline into outlines, etc. Now we are getting into a series of things about building various things, and I am intrigued by the topics here and how they are presented. Transclusion in Nexist™. Here's Jack Park's page on Transclusion in his Nexist work. There is this need for some buttons or something for selecting material and transcluding it, as well as tying the transcluder and the transcludee together. Then there is other stuff, like downgrading when the transcluder doesn't support the transclusion, exactly, and also where more precision is wanted concerning versioning of the transcludee, how that is reflected (W3C or Stanford Encyclopedia style), etc. Jon Udell: Group-Forming Networks. That is not what the title of this page is, but it is the title of the article on this page (sigh). There is a link on the bottom of Udell's current Blog community cross links and goodies that says "how this works" and that got me here. 'Lo, it is about community formation, something that warms my heart and tells me that P2P discovery should work the same way. At least for my purposes, which is collaboration, not underground fencing of misappropriated IP or anything else unseemly. The principles here are valuable. Jon Udell: Exploring transclusion. I'm really looking up transclusion, but this is a cool site and there are some very nice things on the left and right margins too. I am not keen about the example here, but I think the idea of outliner tools that are essentially web/HTML/browser based is as nifty as the Blog This! gimmick. A different category of nfoWare activity. Transclusion - Wikipedia. I want to make sure that I use "transclusion" properly, and it seems I have the general idea. What is interesting is that it might be cached, and it could be client-sided, like using iframes, or it could be done server side using some form of active page serving, whether ASP, JSP, PHP, or server-side includes of another nature. The key to transclusion seems to be how one maintains linkage and identity and deals with referencing the transclusion presence and/or the "native" point of presence. A challenge for purple numbers for sure. Finding out that a place under scrutiny has been transcluded seems like a right-click function that should be kept out of the way. Chipmunk - Wikipedia. Wow, I actually corrected something in Wikipedia -- Chipmunk was misspelled in one place. I just clicked Edit this Page, found the place to change it (it is in HTML), and posted the change. Fascinating. I also need to think about whether or not it matters to do Wiki edits in HTML or not. An interesting challenge. Seriously MiscellaneousFor now.Report a Security Vulnerability. And here is close to what I am looking for. I don't know if it will help me report a vulnerability in a security procedure, but this is closer than I could get before. (It helps that I was on the phone to a friend who happens to have his desk at a Redmond location and he told me what to look for.) This page is still a little off for what I want to do, but I bet I am close enough to make the information known to someone to whom it will matter. I may never learn what was done, but it is valuable that there is a conduit for letting MS Security know about a security breakdown. Microsoft TechNet - Contact Us. A cool thing about this Contact Us page is that, instead of the "Suggestions for this Web site" there is a "Report a Vulnerability in a Microsoft Product" link. Not exactly why I am here (I saw a bad PGP signature on a Microsoft Security Bulletin update), but warmer than I have been able to get in the past. Microsoft TechNet Security: Trustworthy Computing for IT. This is an important page for learning about MS Security. One thing that I have had difficulty with is notifying MS when I detect something that is off, whether a questioned SSL certificate on one of their (partner's) servers at a MS URL, or something in MS security practices themselves (such as CD-ROMs with code having expired signatures, etc.) So, for those who would like to know how to alert Microsoft to a security problem, start on this page. Then go to the bottom and take the contact us link. ACM News Service - The Myths of Open Source. This blurb points to some fascinating observations about the appeal of open-source software outside of the hacker's perspective. Stability over time, absence of vendor churn, and marginal cost of scale are important factors for adoption in IT organizations. In addition, there is favorable contrast against dealing with vendors that provide poor support or discontinue support, since there are substitutions for open-source support in many cases, and having multiple sources of support can be an asset. ACM News Service - North American IPv6 Task Force Kicks Off Next Phase of Moonv6. This is a quick summary of the ramping up of some heavy-duty interoperability testing and confirmation in Moonv6 phase II. What becomes clear to mne is that (1) IPv6 is not soup yet, from a practical availability perspective and (2) transition mechanisms from IPv4 are last on the list and represent, to me, IPv6's dirty little secret. The IETF broke their own commitment to scalability and preservation of interoperability. There is no good way for IPv4 clients to access IPv6 end points, and vice versa. The transition efforts that were begun seem to be either moribund or have vanished into proprietary stealth mode, which suggests that transition is even farther away than the "next few years" for establishing a stable IPv6 backbone. Programmers So Far Underwhelmed by JSF. Here's Jim Wagner's 2004-03-08 Internet News article on the subject. There is more here of interest beyond the appeal of visual development tools. It is about the prospect of having web development and desktop (GUI) application development converge, as .NET is already demonstrating. There are open solutions, especially around forms, that are working to bring that about, so there is something promising in the simplification of the integration and processing model too. So, for me, if I take my attention off of toolkit and IDE questions and look at what the framework affords, there is something richer to dig into. I'm still betting on a model that doesn't have it all be forced into Java, though. ACM News Service - Programmers So Far Underwhelmed by JSF. The JavaServer Faces (JSF) specification has just emerged from the Java Community Process. This is designed to make programming of web sites more like the visual processes that .NET supports. This is an odd thing for me, along with the comment from one programmer: "Lets face it, graphical user interfaces should be designed (and implemented) using visual tools, not text editors. So, what I hope for in JSF is not an easier-to-read source file--it is not to have to read the source file at all." My conflict has to do with not knowing what is happening, and not even having specified behavior for it, yet it is clear that visual assembly approaches are very powerful. So I may stay conflicted. This makes an interesting contrast with regard to some work that says command-line interfaces are easier for instruction and for neophytes to computation. wonder, ponder, ponder, ponder ... Trouble on Silicon Valley's doorstep | Newsmakers |CNET News.com. This is Karen Southwick's 2004-03-09 C|Net News.com article and interview with Ray Lane. There is interesting information on Andy Grove's approach to deverticalizing the computer industry, but the result is not that satisfying to users. All of this innovation, in my words, has not served users in ways they want to be served. "It also unleashed a complex, nonintegrated and difficult-to-maintain stack of software specialization." Lane sees customers wanting simplicity, integration, and security along with any change. And, finally, "Knowledge work globalization is an intractable trend, no matter who's elected. The only question is: Do we participate in it?" ACM News Service - Trouble on Silicon Valley's Doorstep. This is a provocative blurb. It is less than the sort of changes that off-shoring bring, along with the commoditization of programming, as it is about changes in the model of delivery of software and services. I fancy the idea of "adoption of a service-based strategy for software provision and maintenance," though I have no idea whether I would enjoy working in such a world. The use of transparency always interests me, as in "a successful software company must expand or contract according to demand; be able to function anywhere, anytime, and in any situation; respond and deliver to uphold demand; make both internal and external operations transparent in real time; and keep asset and labor content per unit of production to a minimum." This is attributed to former Oracle President Ray Lane. [Here's the thing to watch out for in news blurbs. Lane didn't say that, and neither does the article. In the article, Lane is reported as saying that successful enterprises must expand or contract, etc., and that software companies must be attuned to that. It may be so of software companies as well, and that is a powerful enquiry, but that is not what Lane said.] Lingering Job Insecurity of Silicon Valley. Here's the Steve Lohr and Matt Richtel 2004-03-09 New York Times article. The commoditization of programming is an interesting one. ACM News Service - Lingering Job Insecurity of Silicon Valley. Here's an interesting article on the continuing employment slump. It is suggested that increased automation is as great a factor as other trends, such as outsourcing. There's more. 2004-03-10Information SystemsCollaboration and Cooperative ComputingYes, your WikishipPmWiki - PmWiki.PmWiki. Here's another PHP Wiki that is GPL's and rather tidy in how it appears. This came up in conjunction with questions about making the WikiServer into something that could run on a web site. Getting started with WikiServer. OK, it looks like I can start WikiServer on a different port and all will go well. It is an interesting situation. Eddies Wiki. This is the winner for tiny, self-installing Wiki. It apparently runs on localhost port80 so may need to fidget with that. It does, however, provide some thoughts on how to run off of a CD-ROM, which I like. PhpWiki WikiWikiWeb HomePage. I also notice that phpWiki works right out of the box, which means with no DBMS integration. I need to find out about that kind of scaling too. PhpWiki - Home Page.Some things I like here are the ways that pages can be locked and there is HTML caching of the wiki pages. There is more to learn about what I want to have work with a wiki too. PHP: Hypertext Preprocessor. Here's the site on all things PHP, where I can learn maybe just enough to get by. SourceForge.net: Project Info - PhpWiki. This is an interesting site. There is a PersonalWiki project based on it, that provides for a private Wiki, or Wiki as PIM. SourceForge.net: Project Info - Nexist. OK, here's the Nexist project. I see some kind of application of it on NexistWiki. This is something I am interested in as far as collaborative knowledge goes, though I am not sure I am aligned with the model here. It is time to educate myself about what it is. SourceForge.net: Project Info - xSiteable. This is an interesting project to generate web sites from XTM topic maps and a fast XSLT processor. It is not clear what some of the development methodologies are. This work seems to have been quiet since March, 2003. TM4J - Topic Maps For Java/ Also on SourceForge. It is all in Java, but it might provide for Topic Map processing off-line, especially with the In-memory Backend. SourceForge.net: Project Info - 3store. And here's 3store which is written in C and Lisp. It also uses MySQL. Still, it has awesome characteristics and it might be good to abstract this and preserve its potential usage. SourceForge.net: Project Info - Redfoot. This is the SourceForge.net page, and there is nothing here. It would seem that everything has moved to another server. Cogito Ergo XML. I am not sure about a site that has titles like "Cogitative Topic Map". I guess that is a legitimate topic for a topic map. There are some tempting links here, even cogitative ones. ISO/IEC SC 34/WG 3. Ah, the site for JTC1 SC34 WG3 on information association. Beside Topic Maps, that includes HyTime and other goodies. ISO Project 12350: Topic Maps - Syntax Draft. Here's a version done on 2004-01-25 and to be balloted. More interesting is the existence of a site for this work. The XML Topic Maps (XTM) Syntax 1.0. This is a draft for an ISO specification, dated 2002-07-22 so there might be more work here. The official ISO document won't be available except at a high price, I speculate. Cover Pages: (XML) Topic Maps. It was ISO that I had in mind. Won't go there -- too pricey. But the Cover Pages on XTM is very nice and a great listing of resources, as well a link to the specification. It would appear that there is a later one than I found on the XTM site. XML Topic Maps (XTM) 1.0. Here is the Topic Maps in XML specification. I thought this was also memorialized elsewhere, maybe at W3C or IETF. I need to keep looking. Browsing Nigel Shadbolt in AKT. This is a presentation of a browse on a particular resource (a URI), and how it shows up as a subject and as an object in various triples. This is an interesting presentation on several counts, including where the meaning I give the entries comes from. AKT Triplestore. Here's another Triplestore, based on 3store, with an HTTP API and other interesting qualities. I don't think I need an engine that does screaming inserts and retrievals. I don't think I would even consider organizing a Wiki under this structure, though you never know. It would be wise to have a scalable triple-store interface and access model that could be replaced with a high-performance engine though. triplestore.sourceforge.net. 3 store is a triplestore implementation from Southampton University. It is GPL'd and on SourceForge (which is not very reachable at the moment). java/classes/org/w3c/. There was some work on triplestore at W3C. What interests me here is the way that org.w3c classes are located in the development tree. I needed something like this to figure out how I store packages for development and for location on the web. Redfoot Documentation. The Redfoot scheme is rather interesting too. Although done in Python, it seems to be portable in lots of different schemes. It also seems to work nicely at the node level, whether in a directory system, on a CD-ROM, or on a web site folder point. It is the simplicity of the Redfoot node model that appeals to me. I need to verify that. RDFLib.net. I am looking for information on triplestores, and now I have this particular find. It was on SourceForge once and doesn't seem to be any longer. WebArch. I was looking for something else, and I ran across this cool page. Both for what it offers and also for what it says about itself below the horizontal rule. I would love to be able to have all of that at the bottom of my site pages, especially for nfoWare. This is such a simple page. It is embarassing. I am sitting here typing in a little browser-associated popup that lets me blog items I am looking at, sort of like clipping items from newspapers and magazines. I love this little Javascript widget. I would also love having it on my desktop as simply a way to make notes as they occur to me. The ability to grab links could remain, if I put the collector on IIS on my local machine. Also having local code might be more resilient than the fixture, which depends on the Blogger site, doesn't work with all web pages, and also simply fails to open properly sometimes. It is a very simple thing and I think it would be cool to reverse engineer as I work on coming up with locally-controlled blogger and wiki tools. This is also a good way to try out the HTMLarea script, and also see how that compares with what is done here. ACM News Service -- Rethinking Network Security. There are interesting observations about having security be deeper than the perimeter, especially with access to systems by partners and customers. Somehow, I don't get that the thrust is on resiliency, though. The idea of more interventions and safer code is great, but there is still the problem of what to do when the unthinkable happens. I do think there is much in "Organizations stand a much better chance of recovering from network disruptions with a solid network security incident and disaster response strategy in place--one that is updated regularly, is known to all affected parties, and is practiced to confirm feasibility and completeness." ACM News Service - Competing Technologies Shake Up E-Mail. This is from the RSA Conference, and doesn't reflect whatever happened at the IETF Conference in Seoul. I like the notion of "jostling" that will lead to convergence. It also looks like multiple schemes can be supported together. I like the ones that require PKI simply because it is useful for many other things. If we could arrange OpenPKI and have trustworthy authorities, I would like that even better. ACM News Service - What's Good About Computer Viruses. This article looks at how we are driven to understand the human immune system and other behaviors of biological systems to come up with systems and practices that provide for safety. The idea is that defenses like diversity and decentralization can lead to systems with greater scalability and robustness. There are two issues: being less vulnerable and also being able to mitigate attacks. The last aspect of ductility strikes me as the most difficult, because we are still dealing with what appear to be algorithmic processes at the level the virus interferes with a system. ACM News Service - Short-Lived PCs have Hidden Costs. This blurb is about the environmental, energy, and materials costs that go into the creation of a PC that need to be amortized over the life of the machine. The shorter the life, the worse the situation. The recommendation is to keep machines longer, and to sell them and buy used rather than recycle, which recovers little. The Command Line - The Best Newbie Interface? - OSNews.com. Here's the single-page printable version of the article. It reads well and has some tips about improved command-line interfaces. There are some other metaphors touched on too. The Command Line - The Best Newbie Interface? - OSNews.com. This is an interesting set of articles that should be important for CP4E and also nfoWare. 2004-03-09printing history. In the 70s, printing was rocked by technology -- the computer and electronic publishing. And we have the emergence of a global information society. It could not function without literacy. General: History. Into the 20th century, printing becomes, for example, the UK's 6th largest industry. There are breakthroughs in educational printing. General: History. Then stereotypes and steam-powered presses brought newspapers in quantity. Along with all of this, literacy must accompany. General: History. Although printing was expanding and there were improvements in availability, thanks to binding changes and mechanization, the biggest breathrough was at the end of the 18th century, the invention of lithography. The History of PrintingThe summary of this site has an amazing statement. That a major shift in consciousness that occured in the 16th century was the "rise of the notion that reality could be represented." The History of Printing. Printing with movable type began around 1450 in Europe. There were a number of prerequisite and companion technical developments, and this page goes into them. The expansion of printing was rapid, but literacy was yet to follow. United Nations Literacy Decade: UNESCO Education (3.01b)The United Nations Literacy Decade is from 2003-2012. There are assumed to be 860 million illiterate adults and over 100 million children with no access to school. The UN goal is universal literacy. What is not clear, from the position of today, is what the progression to today's levels of literacy was like. History of the International Literacy Day. September 8 has been International Literacy Day since the conference on the subject in 1966 (in Teheran). PERSONAL LITERACY HISTORY. An interesting paper on what it means to be and have become literate (except for math). The History of Writing - Title. Here's a paper for a course that goes into the history of writing. It is apparently the case that the alphabetic principal was invented only once, in the North Semitic area now including Palestine and Syria, of all the early writing systems, and it spread quite rapidly. So Sanskrit and other alphabetic systems appear to be adaptations from this one innovation. This was around 1700BC. Other forms go back to 3000BC, where as human speech began 30 - 50 thousand years before that. The writer notes that it was writing that made history possible. By 1990 figures, China had 75% literacy, the US 97%, and the UK 98%. Australia and NEw Zealand had 99%, with Canada near 98%. The literacy rate is around 95% in SPain, and 87% in Mexico and Central America. In India the overall literacy rate is around 40% in Hindi areas. Arabic has a 51% overall literacy. In Europe, Russia and Germany have 99% literacy, Portugal 83%. Other European countries also approach 98-99% literacy. There is more information, but this note is interesting. It would be very interesting to see when the boom in literacy began and how it proceeded. ICLC. I was wondering what the history of human literacy is, and how recent anything like wide-spread literacy might be. I found this site while searching for 'human literacy.' There is a very touching page about literacy in Pakistan and, I think, humane literacy. Some of the pages are in Engrish, so I am not so sure. But the message is clear. TomsNetworking: A Stacked Deck: THG's First Look At Notebook Network Cards - Introduction. This is an interesting article. I have a 3Com MegaHertz 10/100 LAN + 56k Modem combo PC-Card. That makes it 16-bit technology, I think, but I never notice, unless it is in file transfers on the local LAN. Otherwise, everything easily keeps up with my broadband connection, of course. This was a nice find by classmate Chérie Dodd. Augmented Story Telling with Topic Maps. The slide on "An Augmented Story Space" illustrates a topic map that points into a text. The Interactive Discourse Space (discussion area?) is not illustrated. But there's something, for me, in the topic map that is already "about the story" and it somehow fixes some things in the discussion. I suppose because it creates an ontological perspective by asserting some entities, relationships among them, and so on, and it expects there to be some ground for attributes like "wife," "marital relation", "husband" and so on. I think the diagram has more colors/flavors for arrows than are shown in the picture here. This seems like a big leap from making AIRs, the fragments of the story. Something else has happened. Augmented Story Telling with Topic Maps. On "IBIS View of a Question," Jack introduces the IBIS scheme. The diagram is too hard to read, and I am getting way out of my league here. Augmented Story Telling with Topic Maps. In the augmented story architecture, an AIR has an associated home page (maybe that is the resource) and I noticed it is a little weird when the AIR carries a fragment of text that refers to something in the overall text of which it is a fragment (e.g., "the above diagram ..."). I am looking at how I write for the web, and in those cases there are structures among the content that are part of the writing, and sometimes something about what is written, but it is all, for the most part, in the story, I think. I am not sure how to relate this to some extensional ground that carries these differentiations. I was just saying, on Blue oxen, that one might want to view editing a Wiki page as different than commenting on it, discussing it, and annotating it. I am not sure how much these are intentional distinctions and not revealed so much by their form. [Also, I need to find out what transclusion means.] Augmented Story Telling with Topic Maps. The "Towards Augmented Story Telling" proposes NexistWiki as a way to do that, with chunking of stories into AddressableInformationResources (as now seen on the NexistWiki site), and seamless integration of IBIS discussion for each AIR. Hmm, this can even be bidirectional and not have the discussion(s) interfere with the story (maybe). Perhaps there is a change of view that can be done smoothly when wanted. There is a lot of hypothetical here. I think one needs to write and discuss this way and see what works and what constitutes augmentation. Augmented Story Telling with Topic Maps. Jack splits into two things - the story - and a space where the story is discussed - dialog about the story, with hyperlinks between. That makes sense. I have even been doing that when I mark up W3C standards so that I can then annotate and discuss them and refer precisely to the parts I am discussing. I can also see that a wiki could benefit, perhaps, from this kind of separation, at least so all observers, including authors, can see what is going on and keep it all straight. Augmented Story Telling with Topic Maps. The "Focus Question" gest to the heart of it. (I would blog the individual slides, but the site is framed and I can't, I don't think. I'll try in a minute.) So, there are two parts: "If we wish to create an augmented story space, a software system with which users will write stories ... "Then, how do we structure that story space to serve as a context in which other people can think? The bolds are mine. I am not sure why it is even other people. Augmented Story Telling with Topic Maps. The "Why Stories?" slide features a quote from John Seely Brown as a powerful means to understand what happened (sequence of events) and why (the causes and effects). I can see attribution problems here. I'd better read on ... Augmented Story Telling with Topic Maps. On the "Augmented Story Telling rocks" is the idea that story telling augmentation is a good thing and markup languages are crucial to the technology of it. Augmented Story Telling with Topic Maps. I am on the slide with title "Towards a point of view," which includes the Edwin Schlossberg quotation, "The skill of writing is to create a context in which other people can think." Utne.com. This page is cited by Jack Park concerning a paper on on social change and how all social change arises from conversations (my words). I need to get the rest of the citation. Ah, it is Margaret J. Wheatley, "All Social Change beins with a conversation," 2002 July 28. TWiki - A Web Based Collaboration Platform. I stumble across this Perl-based wiki implementation from time to time. As much as I don't want to struggle with Perl, there is clearly much offered here as a benchmark and best-of-breed. I really am committed to JavaScript, though, and on my hosted sites, ASP as well. Oh well. 2004-03-08MSN Tech & Gadgets -- IBM Plans Profusion of New Blade Servers. This Stephen Shankland 2004-03-08 CNET News.com article points to an integration that is similar to something we were speculating about in the computer networking class earlier today! readyset.tigris.org. This is a site for Open Source Software Engineering Projects. It features ReadySET, Software Engineering Templates that are available for customization and adoption. This is an impressive effort and I like the style of the site, as well as the tabbed menu bar. Windows XP SP2 could break existing applications - Computerworld. Coverage on the impact of XP changes on developer methods and tools. This is something I must pay attention to as an user and as a developer on Windows XP. This article provides a good heads-up on what is involved. Bug #3426 - JabberStudio. I am not interested in this particular bug, but I am interested in this particular bug-reporting system and how it works. I will need to have support like this for nfoWare and also for Miser and eoWare. Exodus - Escape from Proprietary Instant Messaging. AnderBill and I are looking at Jabber clients as a way to improve our IM experience. I like MSN Messenger a lot, and this implementation of Jabber seems to be the most WinXP friendly of the open-source solutions that I have seen. MIT OpenCourseWare | OCW Home. I was looking at the videos from Knuth's Lectures on "Things a Computer Scientist Rarely Talks About" and it reminded me of what a great resource we are building for seeing the experts in their fields talk about their work and making it understandable for others. This initiative is a great place to see some of that in action, and I wanted to hold a current link to it.
|
|||
