Project /
SemantasticProject.Semantastic HistoryShow minor edits - Show changes to markup Changed lines 16-20 from:
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 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. 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 Mediawiki Templates and SMW Forms would be nice to have as well. However, the 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 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:
Building the Semantastic semantic wiki is the immediate objective of this site. to:
The immediate objective of this site is to build the Semantastic semantic wiki using PyWacket integration as a springboard. Changed line 30 from:
to:
Changed line 37 from:
to:
Changed lines 14-15 from:
A Python Alternativeto:
The Python AlternativeChanged lines 30-32 from:
to:
Changed lines 35-37 from:
to:
Added line 41:
Changed lines 44-45 from:
to:
Changed line 57 from:
Blog capabilities are also a big plus, essentially the same as a wiki page with an HTML editor rather than wiki markup. 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 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. to:
The Semantastic project was at one point fairly well defined. It was going to be to be based on 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:
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 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. 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 ' 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. 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. 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. 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 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 semantic wiki is the immediate objective of this site. to:
Building the Semantastic 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 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 basic functions. 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:
to:
Also see RuleForge basic functions. Added lines 16-43:
Major FunctionsSome of the basic 'semantic' types include:
Changed line 1 from:
The Semantastic project was at one point fairly well defined. It was going to be to be based on ( 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. to:
The Semantastic project was at one point fairly well defined. It was going to be to be based on 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', 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. 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 lines 5-7 from:
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. to:
Tracking Down the CulpritIs 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 AlternativeAdded lines 14-15:
Progress ... of a sortChanged line 13 from:
So, some progress has been made toward a prototype blog and a 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. to:
So, some progress has been made toward a prototype blog and a 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 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. to:
So, some progress has been made toward a prototype blog and a 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 ( 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. to:
The Semantastic project was at one point fairly well defined. It was going to be to be based on ( 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 basic functions. Changed line 11 from:
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. 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 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 a good reason to implement it in Python. 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:
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. 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:
Howeever, recently haker broke into my SemWiki demo and demolished it with spam ... so PHP bites the security dust yet again. 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. |