ingo
i have again brushed up our file acc to Chris's remarks:
please see:
http://www.zefania.de/osis20/pbg-osis20_id_b.zip
smile
wolfgang
http://www.zefania.de
Home of Zefania BibleMarkup Language and True Sharp Sword API.
Ingo schrieb:
schultz wrote
Yet i have assigned the verse enumeratio
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
> schultz wrote
> Yet i have assigned the verse enumeration using scheme: osiID="Gen1.1"> ect.
>
> http://www.zefania.de/osis20/pgb_osis20_id.zip
>
> Congratulate we have probably first OSIS 2.0 bible text ready for use :)
>
> have fun
It's great! (I hope - I can't open the file...seems to be
I couldn't read your version with osisIDs (corrupt ZIP), so these
comments relate to the version Ingo has posted.
To illustrate some problems that show why you should wait for the manual:
- The osis element does not reference the public, reference version of
the schema. The manual will describ
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
Hi folks,
I was able to see a *preview* edition of the NET Bible: Second Beta
Edition today, as the first case *just* came in. It is *not* yet ready
for sale, so don't expect to be able to order it yet. The new version
is slightly smaller despite the addition of 3,000 more footnotes (over
60,000
ingo,
Yet i have assigned the verse enumeration using scheme: ect.
http://www.zefania.de/osis20/pgb_osis20_id.zip
Congratulate we have probably first OSIS 2.0 bible text ready for use :)
have fun
wolfgang
http://www.zefania.de
Home of Zefania BibleMarkup Language and True Sharp Sword API.
> schultz wrote:
> I took the liberty to insert verses tags in your osis text and have
> made some small changes . Now it is valid against CoreOSIS 2.0.
>
> I validated this with Sun's Multi Schema Validator (MSV).
>
> The largest problem was to find the verses, because I do not speak
> Polish. :
Hello Dan,
Thanks for your reply.
I planned to include the search functions as well. Where I want to focus
on first, however, is rewriting the program to make it faster. The 2
second delay before displaying the buttons to select a chapter for the
first time I think is not acceptable. Furthermore
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
13 matches
Mail list logo
