Environment: Production Stamm postit

Abstract

nulllogicone.net is an abstract system for mediating messages between unknown parties, describing authors, messages, and recipients. It consists of a Cycle Model [SAPCT], the Word Space [NKBZ], and a Mediation Logic [OgIf]. A web application against a central database server is realized as a reference implementation.

Table of Contents

  1. Instances
  2. Schema
  3. Documents
  4. Input / Output
  5. Applications
  6. Service
  7. Client

1. Instances

All entities are data records that can be displayed on their own page (for examples there is a page with random links).

In the database tables, the key fields are GUIDs. These are used in URIrefs and URLs. A URIref in an RDF statement consists of the base namespace (https://nulllogicone.net/) followed by the full class name from [SAPCT][NKBZ] with appended GUID. These can display further information on a webpage as URLs.

Example: various URIrefs as hyperlinks

https://nulllogicone.net/Stamm/b4111e0e-48d9-42c4-a6f6-ec4991264947
https://nulllogicone.net/Angler/be279cca-b934-45e6-85fd-96b1a6b1e6ed
https://nulllogicone.net/PostIt/?176bae4e-05d7-4256-97a5-c98bfcbb2869
https://nulllogicone.net/Netz/?76035f19-f4ae-4d58-a388-4bbc72c51cef

2. Schema

For the exchange of data at nulllogicone.net in RDF format, you can download the schema.rdfs file.
On the FRODO RDFSViz Tool page, the relationships can be visualized. As URL for the schema, you must specify the full path https://nulllogicone.net/schema.rdfs.

For storage in local databases or XML files, XSD documents are available as schema definitions for the entities with their fields and the definition of the table structure with their relational relationships. If they are used against web services, the types are bindingly defined in the wsdl files.

For setting up a relational table structure, there are SQL scripts which can be tailored to any use case.

3. Documents

nulllogicone.net mediates messages between unknown parties. For the exchange of data, the RDF format is used to enable decentralization and distributability.

RDF is based on XML and describes arbitrary resources with simple sentences consisting of subject, predicate, and object.

Example: A shortened RDF document 
<?xml version="1.0" encoding= "utf-8"?> 
<rdf:RDF
  xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns#
  xmlns:nlo="https://nulllogicone.net/schema.rdfs#" 
  xml:base="https://nulllogicone.net/">
   <nlo:Stamm rdf:about="https://nulllogicone.net/Stamm/?b4111e0e-48d9-42c4-a6f6-ec4991264947">
     <nlo:name>Oli</nlo:name>
   </nlo:Stamm>
</rdf:RDF>
Example: Links to complete RDF documents

https://nulllogicone.net/Stamm/b4111e0e-48d9-42c4-a6f6-ec4991264947.rdf
https://nulllogicone.net/Angler/be279cca-b934-45e6-85fd-96b1a6b1e6ed.rdf
https://nulllogicone.net/PostIt/176bae4e-05d7-4256-97a5-c98bfcbb2869.rdf

same with json
https://nulllogicone.net/Stamm/b4111e0e-48d9-42c4-a6f6-ec4991264947.json
https://nulllogicone.net/Angler/be279cca-b934-45e6-85fd-96b1a6b1e6ed.json
https://nulllogicone.net/PostIt/176bae4e-05d7-4256-97a5-c98bfcbb2869.json

For each further entity in an RDF document, a link is specified with the predicate <nlo:resource> , which can be followed.

4. Input / Output

Data can be exchanged and distributed in RDF format. For this purpose, functions are summarized on the Input / Output page that output instances from [SAPCT] as RDF documents, validate these documents, and parse them back into objects. The data objects can then be easily stored in a DBMS or serialized as XML.

In addition, the entire Word Space can be output as an RDF file.

5. Applications

6. Service

Web Services: service.oli-it.com

7. Client

Client applications: https://client.oli-it.com