Re: [ELPA Submission] OpenDocumentText exporter for Orgmode

[Jambunathan K <kjambunathan@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 4393 bytes --]

Chong Yidong <cyd@stupidchicken.com> writes:

> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> I would like to submit the "OpenDocumentText exporter for Orgmode" - the
>> org-odt-YYYYMMDD.tar for inclusion in http://elpa.gnu.org/packages.
>>
>> The URL for `package-archives' is:
>> http://repo.or.cz/w/org-mode/org-jambu.git/blob_plain/HEAD:/packages/
>
> The link is broken.

No it is not, it only seems so. The server (which is not a webserver, so
to speak) is merely refusing to list the contents of the directory.

Configure the package-archives with the above URL and the package will
be visible.

Here is the link to archive-contents and the tar file:
http://repo.or.cz/w/org-mode/org-jambu.git/blob_plain/HEAD:/packages/archive-contentshttp://repo.or.cz/w/org-mode/org-jambu.git/blob_plain/HEAD:/packages/org-odt-20110613.tar

Did you checkout README.html?
http://repo.or.cz/w/org-mode/org-jambu.git/blob_plain/HEAD:/packages/README.html

>
>> 2. It is a "friendly fork" (or a "feature branch") of Orgmode and is not
>>    part of official Orgmode Repo (yet).
>
> Does it really have to duplicate the entire Org mode tree?  

Doesn't have to.

> Why can't the "OpenDocumentText exporter" functionality be a single
> Org module?

There are three approaches that I can think of:

1. Roll out my own.

2. I can include *only* the modified and new files as a multi-file
   package and make org-odt dependent on a base version of org.

3. I can distribute my changes as plain old diff against a well-known
   revision of the parent module say org-20110613.tar.

Case 1 => KISS. Self-contained and guaranteed to be consistent. No need
to track dependencies.

Case 2 => In this scenario, at the least, the package manager has to
assure me that org-odt-YYYYMMDD.tar is overlaid on top of the parent
package i.e., at the run time the feature `org-html' is *always*
provided by org-odt package and not by org package.

Case 3 => This scenario sounds like an ugly hack. In this case, the
package server might have to maintain not only the latest
org-YYYYMMDD.tar package but also the historical org-20110613.tar in
it's archives.

Do you see any issues with Case 2?

> Also, could you explain in more detail whether/when this work is
> slated to become part of org-mode?  

AFAICS, Bastien is in favor of inclusion (pending a review, ofcourse). I
believe that the only thing that is slowing things down is the Life
itself with it's non-negotiable demands.

It is close to 3 months since I proposed a formal patch. I am simply
impatient and restless.

> I'm not sure it makes sense to include it as a separate package, if
> it's soon going to be available via the Org daily package (or when Org
> is synched to the Emacs repository) anyway.

There is a strong case for package installers. It attracts more users
and thereby eyeballs. Newbie users are averse to using git. Furthermore,
even serious users rely on installers or stable released before diving
deep.

More importantly, I want that my little work to be available for
posterity and not be lost in the corridors of frail memories or fickle
servers.

>
> Also, could you explain in more detail whether/when this work is slated
> to become part of org-mode?  I'm not sure it makes sense to include it
> as a separate package, if it's soon going to be available via the Org
> daily package (or when Org is synched to the Emacs repository) anyway.
>
>> 4. The package bundles rnc files for OpenDocument format [3]. I need
>>    help from Emacs developers on what would be the right way to include
>>    the copyright notice. I would appreciate if someone could offer me a
>>    helping hand here.
>
> See etc/schema/README.

I need help on two fronts:

1. There is are different schema files for 1.1 and 1.2 formats. Can I
   include them both? How should my schema locating file be composed in
   that case.

2. IANAL and I am anxious to DTRT.

   Does it suffice if I just include the copyright info from the rng
   file or do I also need to copy copyright info from the formal
   spec. (See attachments) If both 1.1 and 1.2 schemas is under included
   do I need to include for each of the instances.

The spec is here:
http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html

RNG file is here:
http://docs.oasis-open.org/office/v1.2/cs01/OpenDocument-v1.2-cs01-schema.rng

Is there anything else I need to do?

Jambunathan K.


[-- Attachment #2: CopyrightNotice-From-RNG-File.txt --]
[-- Type: text/plain, Size: 1667 bytes --]

Open Document Format for Office Applications (OpenDocument) Version 1.2
Committee Specification (CS) 01, 17 March 2011
Relax-NG Schema

Copyright (c) OASIS Open 2002-2011. All Rights Reserved.

All capitalized terms in the following text have the meanings
assigned to them in the OASIS Intellectual Property Rights
Policy (the "OASIS IPR Policy"). The full Policy may be found at
the OASIS website.

This document and translations of it may be copied and furnished
to others, and derivative works that comment on or otherwise
explain it or assist in its implementation may be prepared,
copied, published, and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright
notice and this section are included on all such copies and
derivative works.  However, this document itself may not be
modified in any way, including by removing the copyright notice
or references to OASIS, except as needed for the purpose of
developing any document or deliverable produced by an OASIS
Technical Committee (in which case the rules applicable to
copyrights, as set forth in the OASIS IPR Policy, must be
followed) or as required to translate it into languages other
than English.

The limited permissions granted above are perpetual and will not
be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided
on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE
USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP
RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.  

[-- Attachment #3: CopyrightNotice-From-TheSpecification.txt --]
[-- Type: text/plain, Size: 4047 bytes --]

Copyright © OASIS Open 2002–2011. All Rights Reserved.

All capitalized terms in the following text have the meanings assigned
to them in the OASIS Intellectual Property Rights Policy (the "OASIS
IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published,
and distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this section are included
on all such copies and derivative works. However, this document itself
may not be modified in any way, including by removing the copyright
notice or references to OASIS, except as needed for the purpose of
developing any document or deliverable produced by an OASIS Technical
Committee (in which case the rules applicable to copyrights, as set
forth in the OASIS IPR Policy, must be followed) or as required to
translate it into languages other than English.

The limited permissions granted above are perpetual and will not be
revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an
"AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.

OASIS requests that any OASIS Party or any other party that believes
it has patent claims that would necessarily be infringed by
implementations of this OASIS Committee Specification or OASIS
Standard, to notify OASIS TC Administrator and provide an indication
of its willingness to grant patent licenses to such patent claims in a
manner consistent with the IPR Mode of the OASIS Technical Committee
that produced this specification.

OASIS invites any party to contact the OASIS TC Administrator if it is
aware of a claim of ownership of any patent claims that would
necessarily be infringed by implementations of this specification by a
patent holder that is not willing to provide a license to such patent
claims in a manner consistent with the IPR Mode of the OASIS Technical
Committee that produced this specification. OASIS may include such
claims on its website, but disclaims any obligation to do so.

OASIS takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or
might not be available; neither does it represent that it has made any
effort to identify any such rights. Information on OASIS' procedures
with respect to rights in any document or deliverable produced by an
OASIS Technical Committee can be found on the OASIS website. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such proprietary
rights by implementers or users of this OASIS Committee Specification
or OASIS Standard, can be obtained from the OASIS TC
Administrator. OASIS makes no representation that any information or
list of intellectual property rights will at any time be complete, or
that any claims in such list are, in fact, Essential Claims.

The names "OASIS", “OpenDocument”, “Open Document Format”, and “ODF”
are trademarks of OASIS, the owner and developer of this
specification, and should be used only to refer to the organization
and its official outputs. OASIS welcomes reference to, and
implementation and use of, specifications, while reserving the right
to enforce its marks against misleading uses. Please see
http://www.oasis-open.org/who/trademark.php for above guidance.

[-- Attachment #4: Type: text/plain, Size: 5 bytes --]


--