Json in TiddlyWiki by standard

Developers
#54

was studying about archie, ipfs, IoT - Internet of Things and how can i contribute to tiddlywiki conceptually

#55

list all technologies:

  1. tiddlywiki_render.is
  2. tiddlywiki - file format
  3. tiddlywiki:// - protocol file local tiddlywiki
  4. plugin odbc
  5. new ui/ux tiddlywiki
  6. “RFC for tiddlywiki format and RFC for protocol file local tiddlywiki”
  7. MIME type as ‘application/octet-stream’ for tiddlywiki file
#56

That’s interesting…

I would like to know, how the development stack looks like to create the POC. …

So which programs, compilers which libraries which dependencies do you need to install on your computer to create a poc like this one?

1 Like
#59

image
image979×550 26.7 KB

  1. If everything is json, everything can be a handleable object… javascript and the browser itself has native support for things like json
  2. In this case that I show there… it would be a json displayed as a treeview
  3. there are libraries that read json and can change the view like: ‘kanban’, ‘table’, ‘treeview’ - sample: json-tree-view by luyuan in github-pages
#61

Thanks @anon5541130 I look forward to seeing what you come up with, its is using components I am not so familiar with so perhaps I can only help once you have a public beta. What I do suggest is plan for this to be an alternate, not a replacement, once an alternative is in use it can be evaluated as replacement.

1 Like
#63 
tiddlyWiki.render(
    [
        {"name": "Justice League", "year":2021},
        {"name": "Coming 2 America", "year":2021}
    ], 
    {"<>": "li", "html":[
    	{"<>": "span", "text": "${name} (${year})"}
      ]});
1 Like
#65

engine tiddlywiki → tiddlywiki_render.js

#69
  1. I manipulated the name of json2Html → tiddlywiki - I just changed the name… this is a simple thing.
  2. But the idea is that tiddlywiki( the json2Html based library: can allow json view types as I commented and also allows generating other schemas and reading other schemas as well)
  3. my proof of concept is to use everything as json: template/model/schema/viewer
  4. while viewing json and its schemas, managing/creating/controlling json schemas - I can finally rest ;D
  5. i insert a library to allow view types inside json2HTML, as json2HTML is a library that generates html data from json - json2HTML library developers didn’t think to create a json schema view environment and therein lies the proof of concept: view /generate schemas/validate json schemas etc
  6. my idea is that tiddlywiki as I said only works with json for everything: view/schema/validate schema/render schema etc
#71

methods

1. tiddlywiki-generateJSONSchema
document.write( tiddlyWiki.generateJSONSchema({},JSONSchema) ); // generate all types schema
2. tiddlywiki-validJSONSchema
document.write( tiddlyWiki.validJSONSchema({},JSONSchema) ); // valid all types schema
3. tiddlywiki-previewJSONSchema
document.write( tiddlyWiki.previewJSONSchema({},JSONSchema) ); // render as: kanban/table/treeview/card/list/card-title/card-description etc
4. tiddlywiki-renderJSONSchema
document.write( tiddlyWiki.renderJSONSchema({},JSONSchema) );
5. tiddlywiki-saveAs
document.write( tiddlyWiki.saveAs({},HTML) ); // .HTML, .Markdown, .CSV, .TSV, .TXT ...
6. tiddlywiki-metadataJSONSchema
document.write( tiddlyWiki.metadataJSONSchema({},HTML) ); // return metadata in JSONSchema as version tiddlyWiki, list-plugins, styles, contents, createdAt, lastModified, formattedSize, relativePath, tags, section, title, excerpt, id etc
7. tiddlywiki.JSONSchema
1. application logic layer
2. interface/interaction layer "UISchema"
3. data layer: 
       - layer1 :-: "Mock Datastore" , "Properties Schema"
       - layer2 :-: "Properties Schema"
       - layer3 :-: "Metadata Schema"
4. transport layer: "saveAsJSONSchema" for "local", "remote", "share", "backup"
5. session layer: "plugins" need "all layer JSONSchema: application logic layer,  interface/interaction layer, data layer"
6. network layer: "mimetype tiddlywiki" / "protocol tiddlywiki"
7. presentation layer: "renderJSONSchema" and/or "previewJSONSchema" and/or "validJSONSchema"

notes

  1. The Standard Json Tiddlywiki standard is based on the OSI model which is the standard for internet communication. In this case, Standard Json Tiddlywiki has layers similar to OSI with the difference that everything can be JSON. The image below illustrates the idea/concept:
    image
#74

This is where I am uncomfortable, if you said;

Can work with json for everything

  • I would be much hapier :slightly_smiling_face:

JSON can be more verbose, use more characters be unreadable to the naïve, has more complex needs to parse.

#75
  1. what I talked about at the beginning is having a binary file - this prevents people from reading code and makes the file smaller too
  2. as I said this is similar to a PDF - but with great potential for use
  3. imagine in a world where you can edit your files, share files without needing things like onlyoffice, word etc… that world is possible with tiddlywiki as json binary in browsers
  4. what remains to make this dream a reality is to create documentation that forces or allows browsers to internally adopt tiddlywiki
  5. PDF is a highly used format in the industry, so it is kind of mandatory for every browser to install or have a library to view PDF files.
  6. the same thing that happened with PDF can happen with Tiddlywiki - which can make it more commercial and developed - a good example of this is json/csv format - most browsers support jpeg/jpg/png/pdf/json /csv - could support tiddlywiki format
  7. this also depends on whether the community is active and a good part of the industry and everyday people use the format
#76

this represents the topic “Json in TiddlyWiki by standard” - note “the binary file is read in blocks and not had which makes reading generally faster”

#77

OK, This may have value and I look forward to seeing it but already we can encrypt wikis, and or individual tiddlers. Once loaded in the browser all the tiddlers must become visible to work, so if you can open it, you can read it.

Whilst I too may like to make proprietary solutions, remember tiddlywiki is an open source tool which gains strength from this fact.

I can see what you propose perhaps could be considered a compiler of tiddlywikis. Convert to binary as you say, but this should be a way to publish not the way TiddlyWiki works.

  • This is what we can do already with the tiddlywiki html file + a browser!
  • This of course is not needed with the html version, but I to have promoted the idea of “.tw” files so you can associate a particular browser or app to open such files and avoid the confusion with other html.
  • Did you know if you open a wikiname.tw file (as would .tiddlywiki in most browsers it finds the html headers and opens it as html, many of the savers and backup solutions also honour this?

The key possibility I see in the approach you are suggesting is the browsers could recognise a tiddlywiki and permit saving locally without needing to establish the mechanism, however Timimi as an addon comes close.

  • However the modern security views may stop this.

Keep up the work, but I am not sure I have the knowledge to follow.

#78
  1. A media type (also known as a Multipurpose Internet Mail Extensions or MIME type) indicates the nature and format of a document, file, or assortment of bytes. MIME types are defined and standardized in IETF’s RFC 6838. - link: MIME types (IANA media types) - HTTP | MDN
  2. The Internet Assigned Numbers Authority (IANA) is responsible for all official MIME types, and you can find the most up-to-date and complete list at their Media Types page.
  3. Text-only data including any human-readable content, source code, or textual data such as comma-separated value (CSV) formatted data. Examples include: text/plain, text/csv, and text/html. (Registration at IANA)
  4. I would like to contribute to tiddlywiki with mimetype like this:
    • text/tw as text/html
    • mimetype text/tw registration in IANA
    • mimetype text/tw registration in WICG
    • mimetype text/tw registration in IETF “Internet_Engineering_Task_Force” as RFC

refs

#79

@TW_Tones Hi! How are you? Thanks for feedback… So…

  1. What do you think of this idea of having an official mimetype registry for tiddlywiki in browsers?
  2. or the idea of having an official mimetype registry for tiddlywiki at IANA/WIGC/IETF?
#80

Some interesting notes

  1. Summed it all up, that’s exactly the idea!
  2. But in that case you wouldn’t need Timimi for that, if the browser itself has that possibility. I don’t know if you know, but there are proposals in the WICG for the browser to have a permanent and lightweight database. This can undoubtedly make tiddlywiki viable. You wouldn’t need plugins to save or even extension to save your tiddlywiki information. In that sense, tiddlywiki would be like a dApp - a decentralized application.
  3. Web Platform Incubator Community Group - W3C - reference: (proposal) - ship browsers with builtin wasm-sqlite3 and Writable file API
#81

“Those could be my contributions for communty Tiddlywiki.”

#82
  1. ISO files are also binary files, most linux distros have iso versions to facilitate their distribution. This in no way makes it some kind of proprietary software.
  2. The PDF file can be produced with open software, this also does not make the PDF file proprietary. PDF is an open format, until 2010 or 2011 era it was not an open format, as of mid 2012 yes, Adobe has a group of people responsible for the PDF file format for it to be open.
  3. What I talk about in this topic here as you can see is the idea of distributing tiddlywiki as a binary file.
  4. In other words, one thing is the .tiddlywiki binary file format and another thing is the tiddlywiki program.
#83

I said this emphatically, meaning I was just really reinforcing the idea of what tiddlywiki is capable of doing or does.

#84

I’m thinking of opening a thread about this here on tiddlywiki community

Mimetype ".tw - tiddlywiki" in IANA, WICG, IETF (discussions\ideas\concepts)