Questions:
(I hope these don't seem too naive to be asked in erudite company!)
When it's not something obvious such as support for av11n, how does one
determine what to specify for the *MinimumVersion* property in module.conf
files?
See
Often, there's some obvious feature that requires a minimum Sword
version. Absent that, I have been setting 1.5.8. I'll probably bump that
to 1.6.1 after the release of 1.7.0.
There are two functions of MinimumVersion. One is to shelter users from
modules they can't use. Another is to
Thanks Chris,
Suppose the module being developed has some preverse content, that gets
converted by *osis2mod* as follows:
div type=x-milestone subType=x-preverse sID=pv1/
div type=x-milestone subType=x-preverse eID=pv1/
am I correct in thinking that I should set
MinimumVersion=1.6.0
?
As Chris noted, this is a clue to a frontend that the module might not work as
expected. What a frontend does with that can vary.
The MinimumVersion, at least in part, is a handshake between osis2mod and the
SWORD engine as to whether a module built by osis2mod has features that a
particular
1.7.0 not 1.6.0.
On Aug 6, 2013, at 11:00 AM, David Haslam dfh...@googlemail.com wrote:
Thanks Chris,
Suppose the module being developed has some preverse content, that gets
converted by *osis2mod* as follows:
div type=x-milestone subType=x-preverse sID=pv1/
div type=x-milestone
Thanks DM for the further clarification.
So, if my understanding is correct, osis2mod version 1.7.0 transforms the
OSIS such that because at least one instance of preverse content must use
the milestone form of the div element, then all div elements in the module
must also be the milestone form
The pre-verse div should be ignored as a div. It probably should have been a
milestone element. It should not confuse the SWORD engine.
osis2mod 1.6.1 had the pre-verse div. It is not new w/ 1.7.0. It was supposed
to work with SWORD 1.6.1, but it did not. From what I can tell 1.7.0 does work
Thanks DM,
I agree - mod2imp is only for getting some clues as to what went on under
the hood when the module was built using osis2mod.
The OSIS file from which the module was made was generated by [the latest]
usf2m2osis.py
It is well-formed and valid to the schema, and the only milestone
