From: Vaidheeswaran <kjambunathan@gmail.com>
To: Richard Lawrence <richard.lawrence@berkeley.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Citation syntax and ODT
Date: Mon, 23 Feb 2015 11:52:18 +0530 [thread overview]
Message-ID: <54EAC71A.6080502@gmail.com> (raw)
In-Reply-To: <87zj85s1vf.fsf@berkeley.edu>
On Monday 23 February 2015 09:41 AM, Richard Lawrence wrote:
> Hi Vaidheeswaran,
>
> Thanks for your input about citations!
>
> Vaidheeswaran<vaidheeswaran.chinnaraju@gmail.com> writes:
>
>> Those working on the citation syntax should make it clear that the
>> "lowest common" cite syntax does NOT also IMPOSE (or GUARANTEE) a
>> specific style on the produced document.
>>
>> When I say this, I specifically mean:
>>
>> 1. I want my citation and references to be carried over FAITHFULLY to
>> the exported document.
>>
>> 2. I DON'T CARE how (1) is styled.
>
> I'm afraid I don't quite understand your concern here. What does it
> mean to export a citation faithfully, but without imposing a particular
> style (or without giving it any specific formatting properties)?
>
> My understanding (based on the LaTeX world) is that a `style' defines a
> broad set of conventions for formatting citations and bibliographies in
> the output document. For example, a style might define citations to be
> author-year, or numerical. Within a style, individual citations can
> still have different formatting properties, such as whether it appears
> inside parentheses or not.
User: I want 'Style Newyork'.
ODT/Jabref: I don't have 'Style Newyork'. I can give you 'Style
Chicago'. It is all that I have.
> We haven't really discussed how styles should be specified (yet), or the
> formatting of bibliographies. But we have been discussing a syntax that
> lets you specify those formatting properties which commonly differ
> between individual citations.
IMO, it is better to roll out the citation feature WITHOUT any
formatting properties. The specific formatting chosen is at the mercy
of capabilities of the export backend or citation engine it works
with.
>> ----------------------------------------------------------------
>>
>> The above observations would translate to:
>>
>> The Cite object in it's SIMPLEST form specifies just a citekey (or a
>> set of citekeys). The Cite-object is qualified with a footnote saying
>> that any key-value pair -- including "type" -- that is specified with
>> Cite object MAY BE IGNORED by a backend.
>>
>
> If I understand what you're saying here correctly, I think this is too
> little to expect. If *all* the formatting information in a citation can
> be ignored by any backend, there isn't very much to be gained by having
> a citation syntax in Org.
In Network protocols, the client and server can negotiate the
parameters of a service. The actual service is at the intersection of
client and server capabilities. The RFC itself states what every
compliant client and server implementation should provide at the
minimum. i.e., There is a basic service which is guaranteed.
In our specific case, a backend like ODT will guarantee a readable and
well-styled document limited from among the choice of styles that the
citation engine -- for eg., Jabref -- itself supports. The document
so produced may not be acceptable to a publishing house (Focus here
is on a specific style). Neverthless, document will be respectable
enough to be circulated among peers (for a review) or distributable to
wider public (Focus here is on content rather than SPECIFIC
style).
>> ----------------------------------------------------------------
>> Note that I am not speaking against Bells and Whistles. I am only
>> saying that Bells and Whistles MUST NOT be imposed upon a backend like
>> ODT where the available tools are NOT AS RICH OR AS MATURE AS that
>> available with other backends like HTML or LaTeX.
>
> I don't really know anything about ODT. In particular, I don't know if
> ODT makes room for a distinction between the overall citation style and
> the formatting properties of individual citations. Can you say a bit
> more about what you think its limitations are?
> Obviously, we can't impose anything on the formatting of citations which
> the output document format is incapable of expressing. But I can't
> think of anything we've discussed for the main syntax that seems likely
> to be inexpressible in ODT.
The question is not about expressibility. The question is about what
is expressible using the current set of tools that are available
off-the-shelf.
Do you think of a scenario where:
1. Org acts like a citation engine. (A self-contained Org-ecosystem)
2. Org-backends interfaces with a 3rd-party engine (like pandoc,
zotero, JabRef)
If the current effort is to build (1), ODT backend will have no reason
to complain.
If the effort is geared more towards (2), the ground reality is that
JabRef's style catalog is not as extensive or mature as, say Zotero's
or LaTeXs. The implication is that the PDF document produced via the
LaTeX document WILL DIFFER IN STYLE from the PDF document produced via
the ODT backend.
I am imagining something along a mix of (1) and (2), with more initial
thrust in favor of (2).
> Have you had a chance to read the proposal that I sent around last
> weekend? Are there specific features of the main syntax described there
> (ignoring the `%%(...)' part, which it now appears will be dropped) that
> you don't think ODT or other backends can support? If so, I think that
> is a concern, and should be discussed.
Let me state my position this way:
There was a recent thread (see
http://lists.gnu.org/archive/html/emacs-orgmode/2015-02/msg00650.html)
where a user was having a specific expectation on the ODT engine
dictated by his own (extensive) experience with LaTeX. Since the ODT
engine, behaved differently, he concluded that "ODT engine was
fragile". I am not faulting the user's remarks. I am only saying that
the people who work on the specification take sufficient care to
TEMPER what a user can reasonably expect when he moves between
different backends.
My primary motivation is to draw the attention of people like you (who
are hammering out the syntax) to factor the case of a backend-like
ODT.
----------------------------------------------------------------
That said,
Why don't you give us an example an Org-file that uses the new syntax
in it's more BARE MINIMAL FORM (together with it's accompanying .bib
file). I will pass it via the existing ODT/JabRef backend and
circulate the resulting ODT file to the list. We can use THIS
specific Org-file as an use-case to think through what each of us are
arguing for and against.
My focus in not so much on syntax-richness but on quick roll-out of
citation support.
I have been in this list mostly as a lurker for a long time. The
citation proposal never gained much traction as much as it is seen
right now. More importantly I see Nicolas willing to make the
necessary modifications to export engine. My only suggestion is to
MERELY TO TAKE COGNIZANCE of the need for bells-and-whistles without
the current momentum being dragged down by an attempt to arrive at a
consensus that will keep all parties happy.
next prev parent reply other threads:[~2015-02-23 6:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 7:22 Citation syntax and ODT Vaidheeswaran
2015-02-23 4:11 ` Richard Lawrence
2015-02-23 6:22 ` Vaidheeswaran [this message]
2015-02-23 7:10 ` Vaidheeswaran
2015-02-23 17:15 ` Richard Lawrence
2015-02-23 18:11 ` Vaidheeswaran C
2015-02-23 23:25 ` Richard Lawrence
2015-02-24 3:26 ` Alexis
2015-02-24 3:52 ` Vaidheeswaran C
2015-02-24 4:34 ` Vaidheeswaran C
2015-02-24 5:01 ` Thomas S. Dye
2015-02-24 5:31 ` Vaidheeswaran C
2015-02-24 6:07 ` Thomas S. Dye
2015-02-24 6:37 ` Vaidheeswaran C
2015-02-24 7:48 ` Thomas S. Dye
2015-02-24 17:19 ` Jorge A. Alfaro-Murillo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54EAC71A.6080502@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=richard.lawrence@berkeley.edu \
--cc=vaidheeswaran.chinnaraju@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).