A see a couple of typos in the xs:annotation of the Schema Documentation
The last reads:
The lastest version of the OSIS schema and user documentation can always
be found at: http://www.bibletechnologies.org and comments can be forewarded
to the OSIS Technical Editors...
I think it should be "l
Chris Little schrieb:
[..]
I realize that OSIS may seem complex and difficult to master, but it
is truly simpler than, for example, any modern variety of (X)HTML.
The fact is, we needed to build an XML language that can be used to
represent real Bibles and all of the other literature that wo
Wolfgang,
Well, I suppose you're entitled to your own opinion. There are
essentially two reasons why we have best practices for OSIS.
The first reason is to allow different levels of encoding. For example,
you could encode all quotations using quotation marks rather than the
element. But d
Chris
in a former posting i have said that OSIS is a little bit overdressed.
Rules for best practices is the proof for it.
Best practices must be described in the schema definition and otherwise
nowhere.
the schema definition has to guarantee that i can finde each information
in an osis fil
Wolfgang,
You should probably hold off on template files for a while, or at least
wait until the manual is published, since it will describe best
practices. There are a number of items in your example that should not
be emulated by others. We hope everything will be well explained by the
man
Chris Little schrieb:
I put some new auto-generated documentation for OSIS Core 2.0 online,
along with a sample minimal valid document on our page at
http://www.bibletechnologieswg.org/osis/specs/ .
Hi all,
for creating OSIS 2.0 bibletexts i have made a template.
http://www.zefania.de
The page:
http://www.bibletechnologieswg.org/bibletech/index.jsp
has a typo. The 3rd item under External Links is Interative Maps. Should
be Interactive Maps?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Chris Little
> Sent: Sat, November 08, 2003
