Hello, this my first post. I'm currently working on another Information Organizer Software so this will not be the last posting, be prepared.

I'm curious if there is some markdown for data fields. I remember AskSam used "Field[" with a closing bracket either on the same line (single line field) or on a next line.

Using markdown it would seem natural to change this to "Field:[ ]" and [[[Field: ]]] (because the blockquote is already using ```lang ``` syntax) for multiline fields.

Is there any free form database already which is using fields and markdown?

There are a number of free-form databases that use some form of fields or key:value pairs.

Org mode is using the property drawer for it with a plain text markup, see here http://orgmode.org/manual/Property-syntax.html

Tinderbox is using XML for this purpose

Quiver uses JSON

They are not terribly hard to parse but are not plain text so may not be what you are looking for.

On which platform is your program going to run?
Prion

Org mode is using the property drawer for it with a plain text markup,
see here http://orgmode.org/manual/Property-syntax.html

Oh yes, i forgot the answer is always 42 or Emacs.

They are not terribly hard to parse but are not plain text so may not be
what you are looking for.

It wasn't a parsing question. I just thought i'm not the first one with this idea.
Being an AskSam user since version 1.03

On which platform is your program going to run?

Frontend: MacOSX, Windows.
Backend: MacOSX, Windows, Linux, FreeBSD

Oh yes, i forgot the answer is always 42 or Emacs.

Lother, you made my day :-)

couldn't you use yaml headers in the .md files? or what exactly do you mean by a data field?

Well what i want is that you can have a text document and then you can "stamp" data records in it. For example a document representing a company with the typical name, address fields but also some products i'm interested in in the same text document. Or a literature database with the book details and (quotes, pages) tuples.

In this case i would have one markup file which models a 1:N relation. If N is small strongly context bound and have few fields i found this very convenient.

In this case i cant get away with a header-body document model.

YAML is a nice suggestion. I just think that it is a bit to fragile for hand editing. Especially if nested and you want markup inside a field.

Also strict YAML does not offer the ability to have the same field name multiple times.
But thanks for the hint, i certainly will look inside it and maybe find some inspiration.

Lothar Scholz wrote:

Well what i want is that you can have a text document and then you can
"stamp" data records in it. For example a document representing a
company with the typical name, address fields but also some products i'm
interested in in the same text document. Or a literature database with
the book details and (quotes, pages) tuples.

ConnectedText works like that. Features such as categories, properties and attributes use a markup that have a "completion proposal," meaning that the markup for them gets filled automatically as you start typing, and the value as well (after it has been entered at least once).