Title: RE: RFC: next generation of BibFormat

Hi Ferran,

Concerning your first question, the specifications are still open:

in the implementation we have now, the values returned for a tag
are pretty much the same as those returned by BibRecord, a module
on which BibFormat relies to handle XMLMarc records. This means that
if you specify indicators, you get only the values that have the
indicators. Therefore if no value exists for the indicators, nothing
is returned. If you don't specify indicators, you get only values that
have no indicators.

In the examples that you have pointed out, there is a slight
misunderstanding (as it was not explained in the technical draft): we have used
in our implementation a very general syntax for accessing fields (you can omit indicators,
or use underscore for 'no indicator', use or not dot before subcode etc.).
We shall use a more strict syntax in the final release.
This should help to indroduce something similar to your suggestion.
For example we could use '%' as wildcard (as it is already done in some
places) in a tag, to get all values whatever the indicator is.


> Will the new implementation keep the current language after those
> navigation?

YES, the local language can be forwarded through links.
Please note that as we have dropped link rules, links have to be specified directly
in the new 'format elements', the bricks written in Python. The format elements
can get access to the current language of the user as attribute 'ln' of the 'bfo'
(BibFormat Object) given as parameter to the 'format' function.

Jerome

Reply via email to