[osis-core] sidebars

[Todd Tillinghast]

Patrick,

I see the point for the historical manuscripts.

Do you think it makes sense to have a historical manuscripts extension
to the schema that adds additional enumerated values to the osis*
SimpleTypes.  We have run into a number of cases where we are happy to
allow format and layout oriented information to be encoded as long as it
is a historical manuscript but not for modern texts.

If not a separate extended schema we could have a section for
manuscripts in the user documentation and not list or mention the
presentation oriented enumerated values in the documentation for modern
texts.

If we can I would rather keep "sidebar" out for now.

Todd

> -----Original Message-----
> From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
> admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
> Sent: Tuesday, February 24, 2004 1:07 PM
> To: osis-core@bibletechnologieswg.org
> Subject: Re: [osis-core] sidebars
> 
> Todd,
> 
> Todd Tillinghast wrote:
> > Patrick and Chris,
> >
> > I don't think we should add "sidebar" at any point.  The notes (or
other
> > content that are not notes) that may be presented to the side should
be
> > encoded as a specific type of note using the already existing note
> > types.  Where they get rendered is a matter of layout and
presentation.
> >
> 
> Agree in terms of encoding modern texts, it is a matter of layout.
> 
> The harder question is when we reach manuscript markup, which we may
> very well leave alone, where it is important to record the
presentation
> of the prior text, not necessarily to duplicate its layout in
> presentation but to record "the fact that" it was so presented.
> 
> Marginal notes (the equivalent of the modern side-bar) marked as such
> with their location keyed to a particular portion of text, alert
someone
> doing analysis of the text as to what material was presented to the
> original reader of the text.
> 
> But, as I said, this is not an issue for modern texts, which really
have
> no layout until we impose one with a stylesheet.
> 
> Hope you are having a great day!
> 
> Patrick
> 
> 
> > It is possible that they could use the editions="study" attribute
and
> > value to indicate that these are notes that only apply in study
editions
> > and the render would know to put them to the side.  (worse would be
> > editions="sidebar")
> >
> > Todd
> >
> >
> >
> >
> >>-----Original Message-----
> >>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
> >>admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
> >>Sent: Friday, February 20, 2004 8:53 AM
> >>To: osis-core@bibletechnologieswg.org
> >>Subject: [osis-core] sidebars
> >>
> >>Chris,
> >>
> >>
> >>>USFM provides an element for identifying material that will appear
> >>
> > in
> >
> >>>a sidebar.  <div type="sidebar"> would be the obvious solution, but
> >>>that is rather presentation-oriented.  Another solution would be to
> >>>force users to decide what types of material they are presenting in
> >>>sidebars (e.g. background notes) and to indicate that.
> >>
> >>If I had my preference, both type="sidebar" and type="x-sidebar"
would
> >>be fatal OSIS errors. ;-)
> >>
> >>Sidebars, as you know, are flow objects that are determined at the
> >
> > time
> >
> >>of rendering. I can imagine when we reach markup for manuscripts
that
> >
> > we
> >
> >>will want to allow marking of the location of a note (and other
> >
> > things)
> >
> >>in the original and that will be abused when we make that possible.
> >>
> >>In terms of going into OSIS markup, would need to convert into
> >
> > whatever
> >
> >>elements are appropriate and select them with a stylesheet. I assume
> >>this is something consistent to a particular edition and not notes
of
> >>the same kind can appear at the end of columns, as footnotes or as
> >>sidebar notes?
> >>
> >>Hope you are having a great day!
> >>
> >>Patrick
> >>
> >>
> >>--
> >>Patrick Durusau
> >>Director of Research and Development
> >>Society of Biblical Literature
> >>Patrick.Durusau@sbl-site.org
> >>Chair, V1 - Text Processing: Office and Publishing Systems Interface
> >>Co-Editor, ISO 13250, Topic Maps -- Reference Model
> >>
> >>Topic Maps: Human, not artificial, intelligence at work!
> >>
> >>
> >>_______________________________________________
> >>osis-core mailing list
> >>osis-core@bibletechnologieswg.org
> >>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> >
> >
> > _______________________________________________
> > osis-core mailing list
> > osis-core@bibletechnologieswg.org
> > http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> >
> 
> 
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> Patrick.Durusau@sbl-site.org
> Chair, V1 - Text Processing: Office and Publishing Systems Interface
> Co-Editor, ISO 13250, Topic Maps -- Reference Model
> 
> Topic Maps: Human, not artificial, intelligence at work!
> 
> 
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core