|
|
| Service Oriented Enterprise |
|
|
Friday, January 09, 2004 [BlogService] [BlogService] public class HelloWorldService { public String HelloWorld(String data) { return "Hello World! You sent the string '" + data + "'."; } } ===================== Here is what I want to do: 1. Post source code (java, c#, etc.) on a new kind of blogging engine 2. Have the blogging engine compile my code and turn it into a web service 3. Host the service for execution (with wsdl retrieval) Done. Think Apache Axis (with .jws features) meets a blogging engine. posted by jeff | 9:37 AM Thursday, January 08, 2004 Automated Contextual and Conceptual Engineering I just ran across something I wrote a few years ago... always interesting to look back at old notes... Automated Contextual and Conceptual Engineering I am attempting to convey a difficult concept to readers - right now. As I write this, my Microsoft Office is checking the spelling and grammar. It is putting my words and sentences into a context and using pre-defined rules to suggest areas of syntactic improvement. Dare I say it is using simple artificial intelligence (heuristics and a knowledge base) to improve my writing. Visionaries have been promoting the concept of the Semantic Web for some time. By putting my words, sentences and paragraphs into context, the author is able to work with the software in a more advanced manner. If my word processor knew that I was writing a research paper on 'Automated Contextual and Conceptual Engineering', it could begin acting like an automated research assistant, scanning the web for applicable articles or illustrations, followed by suggestions on document structure, content, automated bibliographies, and footnotes. The more my software knows about what I am trying to write the more help it can offer. Pushing context engineering to the next level takes us to conceptual engineering. Here, software not only understands the context of what I write, but understands the base concepts via conceptual ontologies. Once the software understands a concept it is able to look at the attributes of the concept and begin substituting alternative values suggesting related concepts. We would probably refer to this process as the elicitation of cross-domain metaphors or analogies. Have you ever met someone that was good at connecting the dots in a business, scientific or personal problem? Typically these people are good at applying metaphors to problems. The goal of automated contextual and conceptual engineering is to create better content in less time while educating the author as he or she develops the content. The Web has made it easy for anyone, anywhere to publish information. Browsers, cell phones and web pads are making it easy for anyone to read published information anywhere. I believe that the progress that we have made in mass-authoring content, cross-site syndication and ubiquitous rendering has made the world better. I now believe that the time has come to begin making the content better. This is still an interesting concept. With the advances in web services, MS Office using XML and gains in the semantic web, this kind of stuff may be closer than I originally thought. posted by jeff | 6:05 PM Wednesday, January 07, 2004 Things I'm Reading... I'm in the middle of reading a few things. Here are the ones that seem interesting: Short reads: Steve Cook and Stuart Kent's OOPSLA report: The Tool Factory Long reads: Joe Armstrong's thesis: "Making reliable distributed systems in the presence of software errors" Peter Van Roy's yet-to-be published book: "Concepts, Techniques, and Models of Computer Programming" posted by jeff | 12:42 PM Tuesday, January 06, 2004 Blogging Terms I'm going to break my number one rule about blogging: NEVER TALK ABOUT BLOGGING! But, I read blogs - and there are a couple of things I've noticed... BlogNosing A variant of brown-nosing, this is the practice of always saying nice things about other people on your blog. Example: Bill did a great job of blah blah blah.. Bill always is right... blah, blah, blah. Don't get me wrong, often people will do good work and it should be acknowledged, but you know when you're BlogNosing... Tightly Coupled Blogs This is the practice of assuming that everyone reads your blog (and all of your friends blogs) every day and that in effect they have tuned into your mini-soap opera. I believe that Tightly Coupled Blogs were invented by Microsoft employees. Example: Don farted, then Gudge laughed, but that was cool because Tim and Dave from the Sicily project were walking by (in building 42) and it really didn't smell that bad... A person should be able to read a single entry in your blog - and it should be able to stand on its own. Long Running Conversations that carry Session and Identity between posts is a bad practice... don't worry, I won't do a Blog Coupling Index. BlogSlapping Although I didn't invent this... I do feel that I've mastered it ;-) This is the practice of calling someone out on something stupid that they've said/written. Quite frankly, I don't think there is enough BlogSlapping in the world today. In the near future, I'm considering having a special "BlogSlap Schneider Day", (one free pop shot) just to give everyone a little practice. :-) Damn, That will be FUN! And no, these aren't 'blogging patterns' posted by jeff | 7:22 PM Sunday, January 04, 2004 LinkedIn I'm now "LinkedIn" - feel free to create a 'connection'. https://www.linkedin.com/ I don't know how to post a link to myself, so for now, use my name and email from the main search page. posted by jeff | 6:36 PM Bob Martin Demonstrates His Knowledge on Web Services Bob Martin, from Object Mentor decided to slam web services. The reason I bring this up is because of how poorly he did it. Sure, there are plenty of ways to cut up web services, but unfortunately, many people still don't even have the basic concepts down. Even seasoned people like Bob Martin have such little knowledge on the subject that tend to confuse people, rather than actually making a valid point. Bob says stuff like: - it is rpc - it is attached to http and we use it to get past firewalls - it has a negative effect on coupling :-) - it uses xml, which is "big, ugly and slow" Ok, for those of you who are new to web services. It isn't rpc, it isn't attached to http, it has a positive effect on coupling and yes it uses xml as a typing system, which trades some performance for interoperability. You know, I love when people have valid complaints against web services. There are plenty of them too. I'm reminded of the movie Roxanne with Steve Martin.  Do you remember the scene where he was in the bar and some big drunk called him, "Big Nose". And Steve Martin came back asking, "Big Nose? Is that the best you can do?" Then, Steve Martin went on to find 20 names for his big nose... Hmm. Interesting. Maybe I should post "20 valid complaints about web services"... but, as always, I'll need your help! (valid complaints only, please... ) posted by jeff | 2:57 PM |
|
|
|
|
||||||||||||
|
 |
|||||||||||||||
|
||||||||||||||||
