From: Henning Hraban Ramm <angerweit@gmx.net>
Subject: [NTG-context] FAQ structure (was: Context manuals)
Date: Mon, 21 Oct 2002 20:15:15 +0200 [thread overview]
Message-ID: <200210212015.15305.angerweit@gmx.net> (raw)
In-Reply-To: <20021021140025.27ae9348.morawski@gmx.net>
Am Montag, 21. Oktober 2002 14:00 schrieb Jens-Uwe Morawski:
> > I would take SQL or something other, too.
> hmm, i'm thinking about an XML-file:
I've nearly no experience with XML, but I'm just starting to play with Perl's
XML modules.
If you provide your FAQs as XML I will be able to process it somehow and then
use the same input format myself.
> <contextfaq>
> <author>...</author>
needs only a number or a login name as link to an user database that contains
also email and homepage. (Or are XML databases supposed to be non-relational
and redundand?)
> <keyword>...</keyword>
What about several keywords in one tag?
Or, perhaps better, bundle several <keyword>s in one <keywords>?
> <section>...</section>
> <subsection>...</subsection>
Hm, somewhat unflexible (fixed at two levels).
What do you think of "1.2.3" format with 1, 2, 3 being IDs in a structure
list/database? (We had to define this first, of course.)
> <answer>
> ....
> </answer>
If we are on it, we should divide the <answer> in sections like <text>,
<texcode> and <shellcode> to enable a simple style switching.
> </contextfaq>
And a set of <contextfaq> must be surrounded by a container.
And if I understand XML right, we should use some namespace-prefix, shouldn't
we?
> > > - the KEYWORD field should be replaced by a drop-down menu,
> > > since the user cannot know what key-words are available
> Uups, i mean the keyword-field in the user/reader interface. The authors
> of course should be able the define new keywords.
Ok, must become some multi select box.
Grüßlis vom Hraban!
--
http://www.fiee.net/texnique/
http://www.ramm.ch/context/
---
_______________________________________________
ntg-context mailing list
ntg-context@ref.ntg.nl
http://ref.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2002-10-21 18:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 2:32 [NTG-context] Context manuals John Culleton
2002-10-18 18:48 ` Henning Hraban Ramm
2002-10-18 20:44 ` Jens-Uwe Morawski
2002-10-20 16:56 ` Hans Hagen
2002-10-20 17:48 ` Henning Hraban Ramm
2002-10-20 18:42 ` Hans Hagen
2002-10-21 12:00 ` Jens-Uwe Morawski
2002-10-21 18:15 ` Henning Hraban Ramm [this message]
2002-10-21 21:22 ` [NTG-context] FAQ structure Jens-Uwe Morawski
2002-10-22 8:59 ` [NTG-context] Context manuals Hans Hagen
2002-10-22 19:34 ` Henning Hraban Ramm
2002-10-22 23:23 ` Hans Hagen
2002-10-23 19:15 ` Henning Hraban Ramm
2002-10-23 22:00 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200210212015.15305.angerweit@gmx.net \
--to=angerweit@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).