Good to track this issue in a JIRA. There is also the transitive issue of making external references to Flatbuffer and Parquet (...Thrift?), with an informative/normative flag, and concrete dated/versioned external specification, not just a github link to a moving target.
Mike -----Original Message----- From: Micah Kornfield [mailto:emkornfi...@gmail.com] Sent: Tuesday, January 29, 2019 10:02 AM To: dev@arrow.apache.org Subject: Re: Preferred way to cite Apache Arrow? I believe web-pages are updated each release, so you can get a rough "version number" by looking in git history (e.g. for the 0.12.0 release Layout can be found at https://github.com/apache/arrow/blob/apache-arrow-0.12.0/docs/source/format/Layout.rst ) It would probably be nice to have this on the pages themselves (but we might want a revision number that indicates changes, instead of release). I created https://issues.apache.org/jira/browse/ARROW-4412 to track adding version numbers into the web-pages. -Micah On Mon, Jan 28, 2019 at 10:41 PM Mike French <mfre...@tahakom.com> wrote: > I also notice there is no standalone specification document, and the 3 > spec web pages do not have a date or a version number. > > Mike > > > -----Original Message----- > From: Wes McKinney [mailto:wesmck...@gmail.com] > Sent: Monday, January 28, 2019 6:01 PM > To: dev@arrow.apache.org > Subject: Re: Preferred way to cite Apache Arrow? > > hi Jim, > > We don't have a canonical citation yet. I'd like to write an academic > paper about the project this year or next, so hopefully this will > change, but I think you can cite the website in a publication in the meantime. > > - Wes > > On Mon, Jan 28, 2019 at 8:49 AM Jim Pivarski <jpivar...@gmail.com> wrote: > > > > Is there a preferred reference (paper, proceedings, Zenodo link) to > > use when citing Apache Arrow? I couldn't find any on the Arrow website. > > > > Thanks, > > -- Jim >
