Blog Tools
Edit your Blog
Build a Blog
View Profile
« November 2011 »
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
You are not logged in. Log in
Entries by Topic
All topics  «
Apple Fritters
Calamity
Chinadotcom and VCSY
DD to da RR
Endorsements
Facebook
GLOSSARY
Gurgle
HP and VCSY
Integroty
Microsoft and VCSY
Nobody Can Be That Stupid
Notable Opinions
Off the Wall Speculation
Panama
Pervasive Computing
Reference
SaaS
SOA
The DISCLAIMER
The Sneaky Runarounds
TIMELINE
VCSY
VCSY / Baseline
VCSY / Bashed
VCSY / Infotech
VCSY / MLE (Emily)
VCSY / NOW Solutions
VCSY - A Laughing Place #2
Sunday, 20 November 2011
Microsoft Jupiter and Apollo
Now Playing: Opinions and Speculations
Topic: Microsoft and VCSY
A little deeper:

Remember the complaint of the Microsoft MVP's about the ADO.net data entity framework? They said that it was unnecessarily confined to handling only data representation (see below) at the expense of expanded incorporation of many other behaviors into the data object namely that of "governance (govern business rules) and business logic". They saw the linkages possible yet being ignored and sandbagged by Microsoft management and decided to say so publicly. Oddly they did so one month before the VCSY v MSFT Markman hearing.

Here is what they said:
==================================
Entity Framework
http://efvote.wufoo.com/forms/z7x3p9/
While entities are data objects from the perspective of data storage and data storage technologies, entities are more significantly behavioral objects from the perspective of entity-oriented applications.

The Entity Framework’s focus is on the support the data storage aspects of entity objects at the expense of the primary use case for entities in software applications, which is to govern business rules and business logic. Without recognizing this key architectural enabler and distinction, the ADO .NET Entity Framework team has built only half of the story into the framework, and has over-produced the features and functionality for the aspect of the framework that a data storage product team might be predisposed to.
====================================

This was the case before the settlement. Jupiter being a framework for using so many different languages together along with linkages to the COM OS environment plus cherry-picking dll functionality using P/Invoke makes the idea of developing applications without governance a dangerous proposition. Therefore I conclude Microsoft has solved the prime complaint the MVP's had in June 2008 above and Jupiter is able to provide business rules and business logic to the behavioral entities within the applications built.

That means Microsoft Jupiter is able to treat data objects as full fledged entity objects meaning they may be used to build applications under a managed process that may be automated. Very good. Very encouraging. Looking forward to picking apart what Microsoft says at BUILD. It's increasingly more difficult to hide how a development environment works at this kind of level because the patent claims are quite clear and the marketing claims will have to be specific enough to educate those developers currently in shock because they believe Microsoft is crazy for putting so much emphasis on HTML/Javascript and denegrating their established culture and legacy.

Posted by Portuno Diamo at 2:56 PM EST
Post Comment | Permalink

View Latest Entries