Common Platform Basis: Difference between revisions
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
<br> | <br> | ||
Our core platform services are made available in bindings for all of the above and our initial buildout will create a generic vertical for each distinct enterprise domain set or '[[dominion]]' using same. You can see this illustrated in our space with our 3 regular IPV4 domains. | Our core platform services are made available in bindings for all of the above and our initial buildout will create a generic vertical for each distinct enterprise domain set or '[[dominion]]' using same. You can see this illustrated in our space with our 3 regular IPV4 domains. | ||
<br> | <br><blockquote> | ||
<blockquote> | |||
You can see an example of what of vertical application based on the above is like with the name wik-cso.meansofproduction.biz which is the vertical application supporting the Public Job Shop and our overall enterprise application service. | You can see an example of what of vertical application based on the above is like with the name wik-cso.meansofproduction.biz which is the vertical application supporting the Public Job Shop and our overall enterprise application service. | ||
</blockquote> | </blockquote><br>Some people focus on one or another of these packages as the basis of their enterprise implementation. This focus is not without consequences but it cannot be helped because shopping for what you think you need instead of what you actually need is a buyer's prerogative. | ||
What you actually want, and may not know it, is a system that achieves your functional goals (assuming these are reasonable and feasible) and has the properties highlighted in the Value Prop(osition). In general what you may have think is the 'platform' choice or package du Jour generally has little to do with the attainment (except possibly to hinder it) of there properties. Nonetheless, unless such a choice presents a full blown conflict with the attainment of our | What you actually want, and may not know it, is a system that achieves your functional goals (assuming these are reasonable and feasible) and has the properties highlighted in the Value Prop(osition). In general what you may have think is the 'platform' choice or package du Jour generally has little to do with the attainment (except possibly to hinder it) of there properties. Nonetheless, unless such a choice presents a full blown conflict with the attainment of our | ||
<html><a href=/everything/index.pl?node=total+quality+management>Total Quality Management</a></html> goals, we can accomodate it. | <html><a href=/everything/index.pl?node=total+quality+management>Total Quality Management</a></html> goals, we can accomodate it. | ||
<hr> | <hr> | ||
¹ Among others. | ¹ Among others. | ||
Revision as of 03:18, 7 June 2007
Domain Content Mgt. System (DCMS) integrates the following packages ¹ for the indicated standard purposes and can be for key milestones in the to initialization of your dominion (enterprise domain(s)):
- dojo (js,AJAX)
- Drupal (Organic Groups)
- JBoss (Hibernate, Java, JMX, etc.)
- Joomla (default Front End CMS)
- LAMP (DCMS core, -E, -W, etc.)
- osCommerce (carting, product catalog, and e-commerce/COA interface)
- SQL-Ledger (i18n COA )
- TYPO3 (Site Templating/Backend CMS)
Our core platform services are made available in bindings for all of the above and our initial buildout will create a generic vertical for each distinct enterprise domain set or 'dominion' using same. You can see this illustrated in our space with our 3 regular IPV4 domains.
You can see an example of what of vertical application based on the above is like with the name wik-cso.meansofproduction.biz which is the vertical application supporting the Public Job Shop and our overall enterprise application service.
Some people focus on one or another of these packages as the basis of their enterprise implementation. This focus is not without consequences but it cannot be helped because shopping for what you think you need instead of what you actually need is a buyer's prerogative.
What you actually want, and may not know it, is a system that achieves your functional goals (assuming these are reasonable and feasible) and has the properties highlighted in the Value Prop(osition). In general what you may have think is the 'platform' choice or package du Jour generally has little to do with the attainment (except possibly to hinder it) of there properties. Nonetheless, unless such a choice presents a full blown conflict with the attainment of our Total Quality Management goals, we can accomodate it.
¹ Among others.
