Semantastic

Some of the 'wiggier' conceptual modeling content will wind up in Semantastic and maybe even wiggier stuff like connectionist and neural network topics and non-linear system dynamics ... which is reason enough to implement it in Python.  ''(I love it that [[http://dwave.wordpress.com/2011/05/20/learning-to-program-the-d-wave-one-software-you-should-install-a-book-you-should-buy/ | D-Wave is programmed via Python]] ).'' 

More advanced features, such as [[ http://meta.wikimedia.org/wiki/Help:Template | Mediawiki Templates]] and [[http://www.mediawiki.org/wiki/Extension:Semantic_Forms/Defining_forms | SMW Forms]] would be nice to have as well.  However, the [[http://www.mediawiki.org/wiki/Extension:Semantic_Forms/Semantic_Forms_and_templates | abstruse syntax of SMW Templates]] can be quite daunting.  In fact, it may be easier to use a Python template engine like jinja2 or a standard object factory pattern like [[https://docs.python.org/2/library/collections.html#namedtuple-factory-function-for-tuples-with-named-fields | named tuples]] rather than using a fully dynamic object composer.  In any case, it will be major piece of functionality, certainly person month ( my person, in fact. )   

So ... perhaps a monumental task but not an impossible task.  

I had considered building on Trac as a python-based semwiki, there might also need to be something more like true wiki Categories than the Page/Sub-page mechanism in Trac. Extending of Tags to Tags/Types via RDF might provide a lot of functionality for relatively small investment of time.

There is  the remnants of a fairly developed SemanticMediawiki site that may be revivable in its own. Some of the wiggy Semantic Web content will wind up in Semantastic and maybe even wiggier stuff like connectionist and neural network topics and non-linear system dynamics ... which is reason enough to implement it in Python.

The alternative to SemanticMediawiki is to replicate just enough basic functionality in Python so that a bare-bones semantic wiki, including basic implementation of Types/Properities. This is certainly possible to do within a finite time.

Semantic MW Templates and Forms would be nice to have as as well.  In fact, it may be easier to use a Python template engine like jinja2 or something like standard [[https://docs.python.org/2/library/collections.html#namedtuple-factory-function-for-tuples-with-named-fields | named tuples]] rather than using the abstruse syntax of Semantic Mediawiki Templates, they can be quite daunting.

So, perhaps a monumental task but not an impossible task. 

Building the Semantastic [[http://en.wikipedia.org/wiki/Semantic_wiki | semantic wiki]] is the immediate objective of this site.

There may be document repository functions as well, particular using Trac as a platform.  This would dovetail back into the desktop environment. 

* Basic Wiki Functions: markup, links, backlinks, categories etc.

* Basic wiki functions: markup, links, backlinks, categories etc.

** Note that RDF 3-way/5-way meta-table structures can be hairy, especially tree-like expansions and 'truth maintenance' ( see [[http://en.wikipedia.org/wiki/Semantic_reasoner | semantic reasoner]].

!!!!A Python Alternative

* Basic wiki functions: markup, links, backlinks, etc.

* Categories and Tags

** Tags Plugin, minor customizations
** extend sub-page mechanisms such as  as top-down hierarchy of categories, unlimited depth, clone and split TitleIndex

Blog capabilities are also a big plus, essentially the same as a wiki page with an HTML editor rather than wiki markup.

The Semantastic project was at one point fairly well defined. It was going to be to be based on [[https://semantic-mediawiki.org/ | Semantic MediaWiki]] ( implemented in PHP ) rather than a Python framework. The primary reason for using PHP was that translating all the SMW functionality into Python would be a monumental task.

However ... recently spammers/hackers broke into my SemWiki demo and demolished it with spam ... so PHP bites the security dust yet again.

Is it my fault that PHP security failed again ?  Was it something I did or didn't do ?  I hadn't done the most recent updates so the answer is 'probably yes '.  In fact, the answer is actually 'almost certainly yes'.  But ...  I gotten nail with PHP again and again and apparently that's the way I do ( or don't do ) things and I'm getting too old to change.

So something is out of whack, whether the fault is in PHP or myself is immaterial.  After getting whammed so many times with PHP ( which I don't get a warm feeling about ), I really feel like I need Python to have a secure website.  Call it a quirk.

Is it my fault that PHP security failed again ?  Was it something I did or didn't do ?  I hadn't done the most recent updates so the answer is 'probably yes '  actually 'almost certainly yes' might be more accurate.  But that's the way I do ( or don't do ) things and I'm getting too old to change, so something is out of whack, whether the fault is in PHP or myself is immaterial.  After getting whammed so many times, I feel like I need Python to have a secure website.

The alternative to SemanticMediawiki is to replicate just enough basic functionality in Python so that a bare-bones semantic wiki. including basic implementation of Types/Properities.  This is certainly possible.

Semantic Template and Forms would be nice to have as as well.  In fact, it may be easier to use a Python type templates like jinja2 or standard named types rather than Semantic Mediawiki style Templates, they can be quite duanting.  So, a monumental task but not an impossible task. 

Building the Semantastic semantic wiki is the immediate objective of this site.

The alternative to SemanticMediawiki is to replicate just enough basic functionality in python so that a bare-bones semantic wiki is possible: the basic Types/Properities at a minimum and perhaps semantic Template and Forms as well - monumental but not impossible. See [[RuleForge | RuleForge basic functions]]. 

** should it be a micro-format ?

The Semantastic project was at one point fairly well defined. It was going to be to be based on [[[https://semantic-mediawiki.org/ | Semantic MediaWiki]] ( implemented in PHP ) rather than a Python framework. The primary reason for using PHP was that translating all the SMW functionality into Python would be a monumental task.

Is it my fault that PHP security failed again ?  Was it something I did or didn't do ?  I hadn't done the most recent updates so the answer is 'probably', actually 'almost certainly' might be more accurate.  But that's the way I do ( or donlt do ) things and I'm getting too old to change, so something is out of whack, whether the fault is in PHP or myself is immaterial.  As getting whammed so many times, I feel like I need Python to have a secure website.

!!!Tracking Down the Culprit

Is it my fault that PHP security failed again ?  Was it something I did or didn't do ?  Probably, but that's the way I do things and I'm getting too old to change, so something is out of whack, whether the fault is in PHP is immaterial.  I feel like I need Python to have a secure website.

So, some progress has been made toward a [[http://billbreitmayer.com/cgi-bin/home/ | prototype blog ]] and a  [[http://billbreitmayer.com/cgi-bin/home/ | prototype semwiki ]] implemented in Python on the old BBcom site, but I need to take a closer look at Python security before making it public.  I've been nailed too many times.  Maybe I'll just lock up the semwiki part and publish static HTML.

So, some progress has been made toward a [[http://billbreitmayer.com/cgi-bin/home/ | prototype python semwiki ]] based on the old BBcom site, but I need to take a closer look at Python security before making it public.  I've been nailed too many times.  Maybe I'll just lock up the semwiki part and publish static HTML.

The Semantastic project was at one point fairly well defined. It was going to be to be based on  Semantic MediaWiki ( PHP ) rather than Python and/or Twisted. The primary reason was that translating all the SMW functionality into Python would be a monumental task.

However ... recently spammers/hackers broke into my SemWiki demo and demolished it with spam ... so PHP bites the security dust yet again.  

The alternative was to replicate just enough basic SemanticMediawiki functionality in python so that a bare-bones semantic wiki is possible: the basic Types/Properities at a minimum and perhaps semantic Template and Forms as well - monumental but not impossilbe. 

So, some progress has been made toward a prototype python semwiki based on the old BBcom site, but I need to take a closer look at Python security before making it public.  I've been nailed too many times.  Maybe I'll just lock up the semwiki part and publish static HTML.

There is  the remnants of a fairly developed SemanticMediawiki site that may be revivable in its own. Some of the wiggy Semantic Web content will wind up in Semantastic and maybe even wiggier stuff like connectionist and neural network topics and non-linear system dynamics ... which is a good reason to implement it in Python.

Another starting point for content structuring is the old  BBcom InterWiki application ( using Wikka Wiki ). Maybe the basis for an Ontology Server ?

No to mention a prototype python semwiki based on the old BBcom site, but I need to take a closer look at Python security before making it public.  I've been nailed too many times.

Howeever, recently haker broke into my SemWiki demo and demolished it with spam ... so PHP bites the security dust yet again.