« May 2008 »
S M T W T F S
1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31
You are not logged in. Log in
Entries by Topic
All topics  «
Announcements
Growth Charts
Memories
Prenatal Visits
Soundings
Technical Trading
The Squirts
Ultrasounds
Blog Tools
Edit your Blog
Build a Blog
RSS Feed
View Profile
Port's Pot
Saturday, 17 May 2008
Pieces
Mood:  bright
Topic: Ultrasounds

I will be taking the claims construction material (as poster intheend101 makes available on the Yahoo VCSY forum)  and leave excerpts from that here for a couple days (unless I feel very energetic) and let you think on the text.

Then I'll provide my interpretations and interpretation of what the claims construction says.

These are excerpts from the text in the previous post: 

And checkback at the edit date at the bottom of this post display. I may be adding excerpts to shepherd along the thinking exercises and you will be able to tell that if the edit timestamp is changed. Or, you can do an RSS subscription and you will get an update with every edit. Of course, all you may get is an update for a spelling correct. Diligence can be frustrating.

A critical distinction between the present invention and previous object oriented development systems is the need to know how a function can be called and what to expect it to return, rather than just knowing the function's name.  

An arbitrary object is simply a program piece that can be retrieved by using only its name.

Microsoft disregards this critical intrinsic evidence and instead selectively collects self-serving specific examples and language to improperly import them into the claims.

The specification includes a large number of examples, descriptions, and words of inclusion for “arbitrary objects:” Those examples include the following:

These arbitrary objects may include encapsulated legacy data, legacy systems and custom programming logic from essentially any source in which they may reside. Any language supported by the host system, or anylanguage that can be interfaced to by the host system, can be used to generate an object within the application. (Column 2, lines 29-34, Exhibit A.)
* * *
Arbitrary objects can include text file pointers, binary file pointers, compiled executables, scripts, data base queries, shell commands, remote procedure calls, global variables, and local variables.

Using arbitrary objects allows the independence and separation that is the central benefit of this invention.

For instance, if a company would like to roll out a  new look or syndicate  its content and functionality to another business, this  can be  easily accomplished using the present invention. Since  there is no application  code resident in a web page itself, the same data can be  repackaged in a  number of different ways across multiple sites.


Posted by Portuno Diamo at 2:25 AM EDT
Updated: Sunday, 18 May 2008 10:42 AM EDT

View Latest Entries