shared API for double-entry accounting, treating it as a 'math' library.
Marc Paré
marc at marcpare.com
Sat Jan 18 06:49:36 EST 2014
Hi everyone,
Yes, I see that I perhaps had not made my point/comment completely
clear. I was speaking from the point of view of, if any specific storage
format were to be contemplated, that we at least look towards one that
had good and solid backing from an open source driven organization (in
my example, I used the OASIS group). But, sure, we could also loop in
any report file format(s) that were contemplated as well. I am more
concerned with any suggestion of adopting a storage file format that is
not backed by its originating standardization group.
Cheers,
Marc
Le 2014-01-18 06:11, Tim Schofield a écrit :
> I am probably being dumb here, but in the context of an accounting
> system what do you mean by a standard file format? Are we talking
> about reports? In something like an office application an open
> standard document format is obvious and critical. For an accounting
> system?
>
> I read this http://npoacct.sfconservancy.org/UseCases/StorageAPI/ and
> it seems somewhat naive from an accounting POV. It has a simplistic
> view of what constitutes an accounting transaction (the bulk of
> transactions on accounting systems will be neither payments or
> receipts) and also from the need for a standard API for double entry
> bookkeeping. I am not sure who would use such a thing. I can't imagine
> a use case where you would want the front end of one system to talk to
> the back end of another, or am I missing something?
>
> Thanks
> Tim
>
>
> On 18 January 2014 10:07, Marc Paré <marc at marcpare.com
> <mailto:marc at marcpare.com>> wrote:
>
> Hi Daniel et al,
>
> I am just catching up on the discussion. While I can't really
> comment on the technical aspects of the API, I would like to chime
> in on some of the points you raise.
>
> I also agree that we need to be sensitive from where accountants
> are coming; they are being taught in schools (whether high
> school/college/university levels) using tools that are thought of
> as being the most appropriate for their regions.
>
> Where I am hoping this project will go, is that somewhere along
> our concerted efforts to build our NPO accounting tool, that we
> will ultimately look at establishing a standard format with an eye
> on having it adopted as a universal file format for all others to
> adopt and help maintain. Of course it would have to be an
> opensourced format, for which, if we are to consider it, already
> limits us -- XML, etc. ...
>
> At this point, now that the project has legs I also agree with
> Daniel that we should try to interest some international
> association that could be interested in maintaining the standard
> as an open standard as well as assure longevity to the format; or
> at least, that is what Daniel is suggesting. I for one put a lot
> of stock in the OASIS and its series of opendocument formats. As
> OASIS has support from many large opensource and NPO's, to me,
> would prove to our advantage to try to interest them in this
> particular project to see if they would be interested in helping
> document and adopt whichever format we decide on standardizing. If
> this were possible, we would a solid file format base to work
> from, and, protection from the OASIS group of the longevity of the
> file format.
>
> In short, I believe that at this point, we should be considering
> the assurance of the protection, longevity, standardization of
> whichever file format this project will adopt. Also consider if,
> whoever will champion this file format will have enough resources
> and industry partners to defend the format from any type of patent
> action assault. IMO, if we were to partner up with a group that
> specializes in opensource file formats such as the OASIS group,
> then, the file format will gain help from a group that is
> supported by many opensource and industry leaders, and also a
> group renowned for meticulous documentation of formats with the
> input of its stakeholder partners. Partnering with such groups
> will make for a more stable and dependable file format that could
> evolve in a more concerted effort by all of its stakeholders.
>
> Cheers,
>
> Marc
>
> [Disclaimer: I am part of the LibreOffice project -- marketing]
>
--
Marc Paré
Marc at MarcPare.com
http://www.parEntreprise.com
parEntreprise.com Supports OpenDocument Formats (ODF)
parEntreprise.com Supports http://www.LibreOffice.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sfconservancy.org/pipermail/npo-accounting/attachments/20140118/486a620f/attachment-0001.html>
More information about the npo-accounting
mailing list