Search results come in 4 columns. (…more…)

  • A leading "line" number. Linked to a specialised display. (Often a barely useful, basic navigation; except when there's a customized template registerd for the class definition.
  • 3 columns in order subject, predicate, object: Each a term, URL, text or picture. Any column matching the query, thereby returning relevance context for the actual match.

A match is either a sqlite full text match of search term with a resource or a numeric match of the s, p or o parameter of the query. (The latter is indicated by the corresponding columns having all this value.)

search results

511 Needs to cover: * Required Source Code * Access Control * Choice of Replica * Usage of the (rather minimal) initial setup form Since those are subject to further improvements, documentation is defer created 2011-11-06 17:23:31 +0100
533 Initially most views are disabled and there is no menu. Just a list of tables. To enable the bug tracker menu entry: 1. Head straight to the menu table. 2. Select the one labeld *hoist* (click the n created 2011-11-06 17:43:32 +0100
547 Initially the literal value `` urn:about: `` appears where ever the site's title should be. This is to be changed by the following steps. 1. From the start page follow the link *show all tables" 2. created 2011-11-06 19:36:45 +0100
560 There is a form (currently above the table listing at the initial view of a fresh installation; but that may change over time) with a *snapshot* label (or localised equivalent) containing just a *new* created 2011-11-06 21:35:16 +0100
573 It was felt to be important to decouple changes to the "skin", the visual appearance of the site, from changes to the functional core source. How exactly this is implemented might be subject to chang created 2011-11-07 11:33:27 +0100
589 The last step, before you actually get into doing you own application is to change the cover page of the site. There is a template by the name "homepage": It is preselected as at the public view of created 2011-11-07 12:10:17 +0100
722 Askemos at CeBIT 2012 in Hannover, Germany. 6. - 10. March in Hall 12 (Security Plaza). created 2012-01-05 21:11:37 +0100
2011 Askemos - A Distributed Settlement created 2002-04-28
1261 We've got another two [locations][1]. Environmental friendly: Now 50% on just 5 Watt per location. [1]: created 2012-04-24 18:23:51 +0200
1272 We've got another two [locations][1]. Environmental friendly: Now 50% on just 5 Watt per location. [1]: created 2012-04-24 18:24:00 +0200
1621 *comments please* period open. created 2012-11-30 17:14:53 +0100
1682 created 1762
1975 A digital signature is reminiscent of an ordinary signature; they both have the characteristic of being easy for a user to produce, but difficult for anyone else to forge. Digital signatures can also be permanently tied to the content of the message being signed; they cannot then be 'moved' from one document to another, for any attempt will be detectable. In digital signature schemes, there are two algorithms: one for signing, in which a secret key is used to process the message (or a hash of the message, or both), and one for verification, in which the matching public key is used with the message to check the validity of the signature. created 2012-12-17
2606 A28488eac1bacf0ffa3b98017470a8dfa created 2013-01-12 21:44:59 +0100
2885 Cyberpower and cyber security are conceptualized as a 'Global Game' with a novel 'Cyber Gameboard' consisting of a nine-cell grid. The horizontal direction on the grid is divided into three columns re created 2013-05-23 08:11:32 +0200
2890 In light of recent news, why&how section should point out that this was born by individuals trained as surveillance targets in sovijet Germany. *Sousveillance* seem the recently coined term for the co created 2013-06-14 09:28:39 +0200
2969 Beweiswürdigung elektronischer Dokumente im Zivilprozess unter vergleichender Betrachtung von qualifizierten elektronischen Signaturen nach dem Signaturgesetz und dem Askemos-Verfahren created 2007-07-19
2994 In general, what we need is assurance: methodologies for ensuring that a piece of software does what it's supposed to do and nothing more. created 2013-10-25 20:54:50 +0200
3060 Read [more on the front page's claim][1] "*for the future of due process and **finance***". [1]: ?_id=3057&_v=footnote created 2013-12-21 19:35:39 +0100
3113 Enabling Privacy Through Transparency created 2014-05-19
3133 created 2010-07-20
3222 Tendermint created 2014-05-18