Issue description
It should be possible to assemble instances of the planned new components (table, form, view) to pages.
The clear separation of the server as a data provider and the client as the presentation provider should be adhered.
No programming should be necessary to get the common tasks done. As much information as possible should be stored in the topic map as topics and statements, not as data of some format a in occurrences.
What needs to be done is an interpreter of this component ontology.
On the top of my mind i can think of the following component types:
* View: A list of statement types which are evaluated for one topic (read only)
* Form: A list of statement types which are rendered for a subject for data manipulation purposes
* Table: A list of statement types which are displayed for n subjects for reading
* Menu: Links to components
The general intention is to simplify the manipulation and retrieval of information further to come closer to support the vision of agile, distributed data stores, which individually do serve a certain purpose, but can be integrated with no to little effort within the context of an individual or organization.
*Under no circumstances flexibility, the big advantage of a semantic technology over RDBMS should be given up.*
The word "topic" should not occur in the user interface.
Tasks should be done quickly without any new user interace elements.
Created: 2008-12-04 12:36:11, Robert Cerny Modified: 2009-08-21 08:59:06, Robert Cerny
Link,
No reifier
Use cases
On the start page of this store (the issues store) there should be a table of the latest additions. It should contain the following columns:
* Name of the issue
* Type of the issue
* Reporter
* Reporting date
* Discoverd in version
There should be a link to the page that creates a new issue.
On the same page, there should be a table of the latest resolvings,with the follwing columns:
* Name
* Type
* Resolving date
* Resolver
* Resolved in version
Created: 2008-12-04 12:36:10, Robert Cerny Modified: 2008-12-04 12:36:10, Robert Cerny
Link,
No reifier
The current topincs manual in the Topincs Wiki form (as of Version 3) is unusable. With this feature in place it should be possible to defined an entry page which actually helps the user in finding information of how to understand Topincs and how to do a certain task.
The main page could contain:
* A list of articles
* A list of tasks
* Reading paths through articles
Created: 2008-12-04 13:23:21, Robert Cerny Modified: 2008-12-04 13:23:21, Robert Cerny
Link,
No reifier
|
Reporting date2008-12-04+01:00 Created: 2008-12-04 12:36:10, Robert Cerny Modified: 2008-12-04 12:36:10, Robert Cerny
Link,
No reifier
Has sub issue
Creation forms (Enhancement)
Created: 2008-12-22 13:48:48, Robert Cerny Modified: 2008-12-22 13:48:48, Robert Cerny
Link,
No reifier
Reported by
Robert Cerny
Created: 2008-12-04 12:36:11, Robert Cerny Modified: 2008-12-04 12:36:11, Robert Cerny
Link,
No reifier
|