[sword-devel] osisCore 2.0 docs

[schultz]

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 file, without knowing further best practices rules.

In my Opinion OSIS is too diffuse................... :(

best wishes
wolfgang
http://www.zefania.de
Home of Zefania BibleMarkup Language and  True Sharp Sword API.



Chris Little schrieb:

> 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 manual when it is released (soon).  Until then, we all have to 
> be patient.  If you have specific questions, you can also email the 
> osis-user list.  (See the OSIS portal for techies at WTS, linked from 
> the main OSIS page.)
>
> --Chris
>
> schultz wrote:
>
>>
>> Hi all,
>>
>> for creating   OSIS 2.0  bibletexts  i have made a template.
>>
>> http://www.zefania.de/osis20/osis20_tmpl_biblefiles.zip
>>
>> the template itself is valid against OSIS Core 2.0.
>>
>> You can also see the template online:
>>
>> http://www.zefania.de/osis20/osis20_bible_template.xml
>>
>>
>> i hope it will help by creating osis 2.0 bibles.
>>
>>
>>
>> best wishes
>> wolfgang
>> http://www.zefania.de
>> Home of Zefania BibleMarkup Language and  True Sharp Sword API.
>>
>>
>>
>>
>> _______________________________________________
>> sword-devel mailing list
>> sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>
>
>
>
>
> _______________________________________________
> sword-devel mailing list
> sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
>