Project /
SemantasticProject.Semantastic HistoryHide minor edits - Show changes to output Changed line 30 from:
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/ to:
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/category/learning-to-program-the-d-wave-one/ | D-Wave is programmed via Python]] ).'' Changed lines 18-24 from:
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. 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 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 to:
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 [[http://jinja.pocoo.org/docs/ | jinja2]] to generate instances of as type, or else use a standard object factory pattern like [[https://docs.python.org/2/library/collections.html#namedtuple-factory-function-for-tuples-with-named-fields | named tuples]] to generate 'semi-static' objects, rather than creating a full-blown dynamic object composer. In any case, it would be a major piece of functionality, certainly person-months ( my person-months, in fact. ) So ... perhaps a monumental task, but not an impossible task. I had considered building on Trac as a python-based semwiki and this may still be a good idea. There might also be the potential for something like true wiki Categories than the Page/Sub-page mechanism in Trac. Just extending of simple Tags to Tag:Type->Templates ( in other words tag subtypes ) 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 useful its own right. 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]] ).'' Changed lines 16-20 from:
The alternative to SemanticMediawiki is to replicate just enough basic functionality in Python Semantic MW Templates and Forms would be nice to have as as well So, to:
The alternative to SemanticMediawiki is to replicate just enough basic functionality in Python to build a bare-bones semantic wiki, including a basic implementation of RDF and various Types/Properities functions. This limited objective is certainly possible to achieve within a finite period of time. 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. Changed line 1 from:
to:
The immediate objective of this site is to build the Semantastic [[http://en.wikipedia.org/wiki/Semantic_wiki | semantic wiki]] using [[PyWacket]] integration as a springboard. Changed line 58 from:
There may be to:
There may be a full set of document repository functions ( 'resources' ) as well, particular using Trac as a platform. This would dovetail back into the desktop environment. Changed lines 30-31 from:
* Basic Wiki Functions to:
* Basic Wiki Functions ** markup, links, backlinks, categories etc. Changed line 30 from:
* Basic to:
* Basic Wiki Functions: markup, links, backlinks, categories etc. Changed line 37 from:
** 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]]. to:
** 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]]). Changed lines 14-15 from:
!!!! to:
!!!!The Python Alternative Changed lines 30-32 from:
* Basic wiki functions: markup, links, backlinks, etc. to:
* Basic wiki functions: markup, links, backlinks, categories etc. ** extended sub-page mechanisms such as as top-down hierarchy of categories of unlimited depth, ability to clone and split TitleIndex subtrees. * Tags and Relationships Changed lines 35-37 from:
** ** extend sub-page mechanisms such as to:
** extended tag semantics: relationship types ( inverse, transitive, etc. ), tag associations/clusters. ** tags plugins, for functional customizations ** 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]]. Added line 41:
** essentially the same as a wiki page with an HTML editor rather than wiki markup. Changed lines 44-45 from:
to:
Changed line 57 from:
to:
There may be document repository functions as well, particular using Trac as a platform. This would dovetail back into the desktop environment. Changed lines 3-6 from:
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]] However ... recently spammers/hackers broke into my SemWiki demo and demolished it with spam ... so PHP bites the security dust yet again. to:
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. Security is a big requirement for this project, second only to the requirements for core functionality. Added line 13:
Added lines 29-30:
* Basic wiki functions: markup, links, backlinks, etc. Added lines 51-52:
Blog capabilities are also a big plus, essentially the same as a wiki page with an HTML editor rather than wiki markup. Changed lines 9-11 from:
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 So something is out of whack, whether the fault to:
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've gotten nailed so many times with PHP and apparently that's the way it is for me 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, I really feel like I need Python to have a secure website. Call it a quirk. Changed lines 9-10 from:
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 ' to:
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. Changed lines 15-17 from:
The alternative to SemanticMediawiki is to replicate just enough basic functionality in Python so that a bare-bones semantic wiki 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 to:
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. Changed line 1 from:
Building the Semantastic to:
Building the Semantastic [[http://en.wikipedia.org/wiki/Semantic_wiki | semantic wiki]] is the immediate objective of this site. Added lines 1-2:
Building the Semantastic semantic wiki is the immediate objective of this site. Changed lines 11-12 from:
The alternative to SemanticMediawiki is to replicate just enough basic functionality in to:
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. Changed lines 44-46 from:
** should it be a micro-format ? to:
** should it be a micro-format ? Also see [[RuleForge | RuleForge basic functions]]. Added lines 16-43:
!!!!Major Functions Some of the basic 'semantic' types include: * Categories and Tags ** realm for tags: ** Tags Plugin, minor customizations ** extend sub-page mechanisms such as as top-down hierarchy of categories, unlimited depth, clone and split TitleIndex * Embedded HTML Content ** realm for HTML documents:, similar to Blog Plugin, maybe call realm "weblog:" ** can display as weblog: or as embedded HTML via include macro, render safe HTML ** no wiki search but uses tags ** there may be document repository functions as well * Links and Resources ** realm for links: ** uses wiki and tags ** extended to blob stores and local files, MIME handling * Wiki Language Extensions ** use or convert different wiki dialects, such as Creole, MarkDown, Mediawiki, etc. ** safe includes and embedding of external HTML from trusted sources, such as Wikipedia and other 'interwiki' sources. * Ontology server API for wiki/links and categories/tags ** should it be a micro-format ? Changed line 1 from:
The Semantastic project was at one point fairly well defined. It was going to be to be based on to:
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. Changed line 7 from:
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 to:
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. Changed line 5 from:
!!!Tracking Down the Culprit to:
!!!!Tracking Down the Culprit Changed lines 5-7 from:
to:
!!!Tracking Down the Culprit 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. Added lines 7-8:
!!!!A Python Alternative Added lines 14-15:
!!!!Progress ... of a sort Changed line 13 from:
So, some progress has been made toward a [[http://billbreitmayer.com/cgi-bin/home/ | prototype blog ]] and a [[http://billbreitmayer.com/cgi-bin/ to:
So, some progress has been made toward a [[http://billbreitmayer.com/cgi-bin/home/ | prototype blog ]] and a [[http://billbreitmayer.com/cgi-bin/wiki/ | 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. Changed line 13 from:
So, some progress has been made toward a [[http://billbreitmayer.com/cgi-bin/home/ | prototype to:
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. Changed lines 1-5 from:
The Semantastic project was at one point fairly well defined. It was going to be to be based on Semantic MediaWiki ( 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. to:
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 ? 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. 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]]. Changed line 11 from:
So, some progress has been made toward a to:
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. Changed line 9 from:
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 to:
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. Changed lines 11-13 from:
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 to:
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. Changed line 3 from:
to:
However ... recently spammers/hackers broke into my SemWiki demo and demolished it with spam ... so PHP bites the security dust yet again. Added lines 1-13:
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. Howeever, recently haker 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. 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 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. |