Use container as index file

[bourgeoa]

I made a test building an index.json with only title and date modified skinnytiddlers works without any problems.
I took these from the container. So no need for an index except if you want to load the **tags **without loading the tiddlers

[linonetwo]

The question is, is title enough to decide whether TW needs to reload a tiddler?

If you change some tiddler in another device, you may want to reload it depends on some other metadata.

But I agree that container as index file is enough since we can get "modified" from the container, look at https://groups.google.com/forum/#!topic/tiddlywikidev/mgiYWXRy0_E , seems if you only return title field, TW will use it to determining whether tiddler has changed in the backend, but if you also return a modified(Date) field, it will use it too.

[linonetwo]

But load more metadata is not so hard, we can store tiddler fields inside xxx.meta files, and:

1. only load title from the container on the startup.
2. load all metadata use globbing on the second getSkinnyTiddlers(), maybe these metadata will be used in searching?
3. only load title and modified from the container on subsequent getSkinnyTiddlers(), only for TW to determine whether to trigger loadTiddler().

FYI to use globbing:

[linonetwo]

There are two problems:

1. "modified" field from the server is the time POST reaches the server, but in the client side, it's the time user click save button. So "modified" in the client side will be earlier than that on the server side.
2. "title" contains slash "/", we can't store it directly to the server, we may need to replace "/" with some other characters.

@bourgeoa how did you dealt with that?

[bourgeoa]

I don't have any / in the title. Title is the name of the tiddler and the name of the tiddler file without extension.

I have decided to keep the index file for the time being because when I load the skinnytiddlers without the tags these are not loaded through the load tiddler function.

[bourgeoa]

I have made a RDF .tll version functional.
Just need to test the migration function.

We must agree to a final commun ontology.

There is a small problem with the "Draft of 'New tiddler'" that creates 2 vocab draft.of and draft.title. A dot character being forbidden in ontologies I have converted the dot (draft.) by underscore (draft_).

[linonetwo]

Can you reuse some of the existed vocabularies for the draft? Here are some of them https://lov.linkeddata.es/dataset/lov/terms?q=draft

But I dont understand how you are going to use draft.of and draft.title, what is the subject and object?

[linonetwo]

Maybe using globbing?

[linonetwo]

I'm trying to name all metafile (each contains skinny fields for a tiddler) with pattern .meta.xxxtiddlername.ttl, so I can globbing all .meta.* so GET them in a single file.

https://github.com/solid/solid-spec/blob/master/api-rest.md#globbing-inlining-on-get

Ideally, I can globbing xxxtiddlername.meta, but seems globbing can't work in that way.

[linonetwo]

Actually, just after startup, saveTiddeler() will try to save $:/StoryList, so I'm asking how you handle / in the title.

[linonetwo]

Some tiddlers don't have the tags, will load tiddler function refused to load them? What did you mean by this?

[linonetwo]

You can see how node-tiddler handles filename, I think reading all fields from metafiles (through globbing) is a good way to avoid trouble.

[bourgeoa]

I never store $:/StoryList and I think any so called system files ($:/......).

For the filename only I use encodeUriComponent(title).

[linonetwo]

Why not? I think some plugin may store some config in the $:/ tiddlers, and maybe user want to store their configs?

[linonetwo]

BTW, I'm trying to use https://github.com/pasqLisena/rdf-translator to translate between JSON and turtle. But it's very slow.