PyWacketPyWacket|
Main /
HomePageMain.HomePage HistoryHide minor edits - Show changes to output Changed lines 3-5 from:
Welcome to main public site for the PyWacket project. to:
Welcome to main public site for the PyWacket project. The purpose is to develop of a Python 'semwiki' to power Semantastic and its content. PyWacket is a technically-oriented integration framework used to build the semwiki. Changed line 7 from:
[[Project/PyWacket]] is a loosely-defined integration framework, primarily for desktops, but should be general enough to work for almost any application to:
[[Project/PyWacket]] is a loosely-defined integration framework, primarily for desktops, but should be general enough to work for almost any application that depends on a collection of existing Python packages ( plus some 'glue code'). Changed line 11 from:
Probably, the most visible distinction between this and other frameworks is a [[http://en.wikipedia.org/wiki/Knowledge-based_systems | knowledge-based]] approach to:
Probably, the most visible distinction between this and other frameworks is a [[http://en.wikipedia.org/wiki/Knowledge-based_systems | knowledge-based]] approach, or perhaps a [[http://en.wikipedia.org/wiki/Case-based_reasoning | case-based]] approach in some cases. Changed lines 7-9 from:
[[Project/PyWacket]] is a loosely-defined integration framework, primarily for desktops The integration architecture and supporting components are useful in building several types of applications, including a Semantic Web wiki ( in essence a knowledge base ) to be known as Semantastic. The underlying technology is as purely Python as possible, ideally no external dependencies, maybe with Java for the messaging backplane and message queue components, perhaps some PHP in a supporting role to:
[[Project/PyWacket]] is a loosely-defined integration framework, primarily for desktops, but should be general enough to work for almost any application depending on a collection of existing Python packages. The integration architecture and supporting components should be useful in building a [[http://en.wikipedia.org/wiki/Semantic_Web | Semantic Web]] wiki ( in essence a [[http://en.wikipedia.org/wiki/Knowledge_base | knowledge base]] ) to be known as Semantastic. The underlying technology is as purely Python as possible, ideally no external dependencies, maybe with Java for the messaging backplate and message queue components, perhaps some PHP in a supporting role. Probably, the most visible distinction between this and other frameworks is a [[http://en.wikipedia.org/wiki/Knowledge-based_systems | knowledge-based]] approach ( or perhaps more strictly a [[http://en.wikipedia.org/wiki/Case-based_reasoning | case-based]] approach ). Changed line 7 from:
[[Project/PyWacket]] is a loosely-defined integration framework, primarily for desktops. Probably, the most visible distinction between this and other frameworks is a [[http://en.wikipedia.org/wiki/Knowledge-based_systems | knowledge-based]] approach ( or perhaps more to:
[[Project/PyWacket]] is a loosely-defined integration framework, primarily for desktops. Probably, the most visible distinction between this and other frameworks is a [[http://en.wikipedia.org/wiki/Knowledge-based_systems | knowledge-based]] approach ( or perhaps more strictly a [[http://en.wikipedia.org/wiki/Case-based_reasoning | case-based]] approach ). Changed lines 2-4 from:
Welcome to main public site for the PyWacket project. to:
Welcome to main public site for the PyWacket project. The purpose is to develop of a Python 'semwiki' to power Semantastic and its content. PyWacket is a technically-oriented integration framework used to build the semwiki. ---------------------------------- Changed line 6 from:
The integration architecture and supporting components are useful in building several types of applications, including a Semantic Web wiki ( in essence a knowledge base ) to be known as Semantastic. The underlying technology is as purely Python as possible, ideally no dependencies, maybe with Java for the messaging backplane and message queue components, perhaps some PHP in a supporting role. to:
The integration architecture and supporting components are useful in building several types of applications, including a Semantic Web wiki ( in essence a knowledge base ) to be known as Semantastic. The underlying technology is as purely Python as possible, ideally no external dependencies, maybe with Java for the messaging backplane and message queue components, perhaps some PHP in a supporting role. Changed line 8 from:
There are a huge number of existing components to fill the 'slots' in the underlying architecture, with literally to:
There are a huge number of existing components to fill the 'slots' in the underlying architecture, with literally hundreds of combinations. Changed line 6 from:
The integration architecture and supporting components are useful in building several types of applications, including a Semantic Web wiki ( in essence a knowledge base ) to be known as Semantastic. The underlying technology is as purely Python as possible, ideally no dependencies, maybe with Java for the messaging backplane and message queue components, perhaps some PHP. to:
The integration architecture and supporting components are useful in building several types of applications, including a Semantic Web wiki ( in essence a knowledge base ) to be known as Semantastic. The underlying technology is as purely Python as possible, ideally no dependencies, maybe with Java for the messaging backplane and message queue components, perhaps some PHP in a supporting role. Changed line 6 from:
The integration architecture and supporting components are useful in building several types of applications, including a Semantic Web wiki ( to:
The integration architecture and supporting components are useful in building several types of applications, including a Semantic Web wiki ( in essence a knowledge base ) to be known as Semantastic. The underlying technology is as purely Python as possible, ideally no dependencies, maybe with Java for the messaging backplane and message queue components, perhaps some PHP. Changed line 4 from:
[[Project/PyWacket]] is a loosely-defined integration framework, primarily for desktops. Probably, the most visible distinction between this and other frameworks is a [[http://en.wikipedia.org/wiki/Knowledge-based_systems | to:
[[Project/PyWacket]] is a loosely-defined integration framework, primarily for desktops. Probably, the most visible distinction between this and other frameworks is a [[http://en.wikipedia.org/wiki/Knowledge-based_systems | knowledge-based]] approach ( or perhaps more accurately a [[http://en.wikipedia.org/wiki/Case-based_reasoning | case-based]] approach ). Changed line 4 from:
[[Project/PyWacket]] is a loosely-defined integration framework, primarily for desktops. Probably, the most visible distinction between this and other frameworks is a [[http://en.wikipedia.org/wiki/Knowledge-based_systems | 'knowledge-based']] to:
[[Project/PyWacket]] is a loosely-defined integration framework, primarily for desktops. Probably, the most visible distinction between this and other frameworks is a [[http://en.wikipedia.org/wiki/Knowledge-based_systems | 'knowledge-based']] approach ( or perhaps more accurately a [[http://en.wikipedia.org/wiki/Case-based_reasoning | case-based]] approach ). Changed line 4 from:
[[Project/PyWacket]] is a loosely-defined integration framework, primarily for desktops. Probably, the most visible distinction between this and other frameworks is a to:
[[Project/PyWacket]] is a loosely-defined integration framework, primarily for desktops. Probably, the most visible distinction between this and other frameworks is a [[http://en.wikipedia.org/wiki/Knowledge-based_systems | 'knowledge-based']] or perhaps more a [[http://en.wikipedia.org/wiki/Case-based_reasoning | 'case-based']] approach. Changed line 31 from:
[[WeirdAndWonderful | The to:
[[WeirdAndWonderful | The Weird and Wonderful ]] Added lines 30-32:
[[WeirdAndWonderful | The Wierd and Wonderful ]] Added lines 27-28:
Looking for [[http://www.pywacket.org/ | Pywacket.Org]] ? Deleted line 29:
Changed lines 17-18 from:
!!![[Main | Main to:
!!![[Main | Main Pages]] Changed line 21 from:
!!![[Project | Project to:
!!![[Project | Project Pages]] Changed lines 17-18 from:
!!![[Main | Main to:
!!![[Main | Main Page]] Changed line 21 from:
!!![[Project | Project to:
!!![[Project | Project Page]] Changed lines 17-18 from:
!!![[Main to:
!!![[Main | Main Pages]] Changed line 21 from:
!!![[Project to:
!!![[Project | Project Pages]] Changed lines 17-18 from:
!!!Main Pages to:
!!![[Main]] Pages Changed line 21 from:
!!!Project Pages to:
!!![[Project]] Pages Changed lines 14-16 from:
[[Main/AboutLinode | About Linode]] [[Project/Python | Python Topics]] to:
* [[Main/AboutLinode | About Linode]] * [[Project/Python | Python Topics]] Changed line 2 from:
Welcome to to:
Welcome to main public site for the PyWacket project. Deleted lines 27-28:
Deleted lines 29-36:
To continue setting up PmWiki, see [[PmWiki/initial setup tasks]]. The [[PmWiki/basic editing]] page describes how to create pages in PmWiki. You can practice editing in the [[wiki sandbox]]. More information about PmWiki is available from [[http://www.pmwiki.org]]. Changed lines 30-32 from:
and to:
[[PmWikiHelp | PmWiki Help Page]] PmWiki's documentation is available via the [[PmWiki/documentation index]]. Changed line 20 from:
(:pagelist group=Main list=normal fmt=#title to:
(:pagelist group=Main list=normal fmt=#title -WikiSandbox :) Changed line 20 from:
(:pagelist group=Main list=normal fmt=#title:) to:
(:pagelist group=Main list=normal fmt=#title: -WikiSandbox) Changed line 39 from:
More information about PmWiki is available from [[http://www.pmwiki.org]]. to:
More information about PmWiki is available from [[http://www.pmwiki.org]]. Changed line 10 from:
So to:
So ... still under construction :) Changed lines 4-6 from:
Info about the PyWacket Project to:
[[Project/PyWacket]] is a loosely-defined integration framework, primarily for desktops. Probably, the most visible distinction between this and other frameworks is a 'knowledge-based' approach. The integration architecture and supporting components are useful in building several types of applications, including a Semantic Web wiki ( knowledge base ) to be known as Semantastic. The underlying technology is as purely Python as possible, ideally no dependencies, maybe with Java for the messaging backplane and message queue components. There are a huge number of existing components to fill the 'slots' in the underlying architecture, with literally hundred of combinations. So, still under construction). !!!Current Topics Changed line 4 from:
Info about to:
Info about the PyWacket Project, Python, Linode, etc. Changed line 2 from:
Welcome to PyWacket. to:
Welcome to [[Project/PyWacket | PyWacket]]. Changed lines 10-11 from:
!!!Pages to:
!!!Main Pages Added lines 13-16:
!!!Project Pages (:pagelist group=Project list=normal fmt=#title:) Added lines 9-12:
!!!Pages of the Main Group (:pagelist group=Main list=normal fmt=#title:) Changed line 6 from:
[[Main/AboutLinode About Linode]] to:
[[Main/AboutLinode | About Linode]] Changed lines 1-3 from:
(:Summary:The default home page for the Welcome to to:
(:Summary:The default home page for the PyWacket Wiki:) Welcome to PyWacket. Info about Linode, Ubuntu, etc. ---------- Deleted lines 18-23:
[[http://billbreitmayer.com | BBcom ]] Looks good ... \\ More text Changed line 17 from:
[[http:// to:
[[http://billbreitmayer.com | BBcom ]] |