One key question
I need to resolve is what if any namespace, or prefix shall I add to “field tiddlers” that define the fieldname. The following are at the top of my list;
- Prefixed
▭eg▭ fieldname, Searchable but we could hide them with and additional system namespace - Prefixed
$:/fields/eg$:/fields/fieldname, only searchable in advanced search - Or just fieldname = tiddler name eg fieldname, searchable and may conflict with tiddlers of the same name, especially if a tiddlername is used as a fieldname.
Keeping in mind I plan to permit a custom namespace filter on each tiddler. Thus a tiddler may include a field field-namespace containing [prefix[$:/brand/fields/]] which is applied to find field definition tiddlers for the fields on the current tiddlers
A second key question
How do I handle existing standard and core fieldnames?
- Include them in this field handling mechanisium ie the field tiddler according to the method chosen above
- Provide a seperate namespace to use for known core fieldnames eg prefix $:/system-fields/`
- Or just fieldname = tiddler name eg fieldname, searchable and may conflict with tiddlers of the same name, especially if a tiddlername is used as a fieldname.
- Just exclude them from field handling altogether?
Keep in mind this will provide additional handling and not impact default tiddlywiki field behaviours.