oh, duh: <listAnnotation> in upcoming release?
My vague recollection is we had wanted <listAnnotation> to go into the upcoming release whether <annotation> was ready or not. It is not ready. However, I am just newly reminded that 1. There is no prose in the Guidelines that discusses <listAnnotation>; 2. thus there is no place for the <listRef> of <listAnnotation> to point; and 3. the <desc> of <listAnnotation> (and presumably any prose that discusses <listAnnotation>) makes reference to <annotation>, which does not exist.
Since standOff made it last time, I think it may be ok to delay this if we risk delivering it a little half-baked. Raff On Wed, Jul 29, 2020 at 9:45 PM Syd Bauman <s.bauman@northeastern.edu> wrote:
My vague recollection is we had wanted <listAnnotation> to go into the upcoming release whether <annotation> was ready or not. It is not ready. However, I am just newly reminded that 1. There is no prose in the Guidelines that discusses <listAnnotation>; 2. thus there is no place for the <listRef> of <listAnnotation> to point; and 3. the <desc> of <listAnnotation> (and presumably any prose that discusses <listAnnotation>) makes reference to <annotation>, which does not exist. _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
I'd love to get it in if that's possible. Why don't I do a pull request, and we can either accept it or wait on it? On Thu, Jul 30, 2020 at 3:13 PM Raffaele Viglianti < raffaeleviglianti@gmail.com> wrote:
Since standOff made it last time, I think it may be ok to delay this if we risk delivering it a little half-baked.
Raff
On Wed, Jul 29, 2020 at 9:45 PM Syd Bauman <s.bauman@northeastern.edu> wrote:
My vague recollection is we had wanted <listAnnotation> to go into the upcoming release whether <annotation> was ready or not. It is not ready. However, I am just newly reminded that 1. There is no prose in the Guidelines that discusses <listAnnotation>; 2. thus there is no place for the <listRef> of <listAnnotation> to point; and 3. the <desc> of <listAnnotation> (and presumably any prose that discusses <listAnnotation>) makes reference to <annotation>, which does not exist. _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
Sounds good -- happy to review On Thu, Jul 30, 2020 at 3:15 PM Hugh Cayless <philomousos@gmail.com> wrote:
I'd love to get it in if that's possible. Why don't I do a pull request, and we can either accept it or wait on it?
On Thu, Jul 30, 2020 at 3:13 PM Raffaele Viglianti < raffaeleviglianti@gmail.com> wrote:
Since standOff made it last time, I think it may be ok to delay this if we risk delivering it a little half-baked.
Raff
On Wed, Jul 29, 2020 at 9:45 PM Syd Bauman <s.bauman@northeastern.edu> wrote:
My vague recollection is we had wanted <listAnnotation> to go into the upcoming release whether <annotation> was ready or not. It is not ready. However, I am just newly reminded that 1. There is no prose in the Guidelines that discusses <listAnnotation>; 2. thus there is no place for the <listRef> of <listAnnotation> to point; and 3. the <desc> of <listAnnotation> (and presumably any prose that discusses <listAnnotation>) makes reference to <annotation>, which does not exist. _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
Indeed. I think a pull request would focus minds. (am I the only one who now top-posts by default, but also feels bad about it all the same?) On 30 Jul 2020, at 20:15, Hugh Cayless <philomousos@gmail.com<mailto:philomousos@gmail.com>> wrote: I'd love to get it in if that's possible. Why don't I do a pull request, and we can either accept it or wait on it? On Thu, Jul 30, 2020 at 3:13 PM Raffaele Viglianti <raffaeleviglianti@gmail.com<mailto:raffaeleviglianti@gmail.com>> wrote: Since standOff made it last time, I think it may be ok to delay this if we risk delivering it a little half-baked. Raff On Wed, Jul 29, 2020 at 9:45 PM Syd Bauman <s.bauman@northeastern.edu<mailto:s.bauman@northeastern.edu>> wrote: My vague recollection is we had wanted <listAnnotation> to go into the upcoming release whether <annotation> was ready or not. It is not ready. However, I am just newly reminded that 1. There is no prose in the Guidelines that discusses <listAnnotation>; 2. thus there is no place for the <listRef> of <listAnnotation> to point; and 3. the <desc> of <listAnnotation> (and presumably any prose that discusses <listAnnotation>) makes reference to <annotation>, which does not exist. _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council
RV> Since standOff made it last time, I think it may be ok to delay this if we risk delivering it a little half-baked. HC> I'd love to get it in if that's possible. Why don't I do a pull request, and we can either accept it or wait on it? RV> Sounds good -- happy to review NC> Indeed. I think a pull request would focus minds. Y’all must think of pull requests quite differently than I do. I think of a pull request as a request that something be pulled in. I know full well the current state of sydb-standOff is such that it would not be acceptable to pull it into dev, especially right before a release. If it will kick us into gear and get things done, be my guest. But I am very hesitant to issue a request that I know should be denied. (And I know I won’t put in any significant TEI work until the weekend.) So I am inclined to go with RV’s initial thought, and post an apologetic comment with a vague timetable to the ticket.
https://github.com/TEIC/TEI/pull/2018 doesn't fix *everything* to do with standOff, but I hope is enough for comments and perhaps can be cleaned up in time for a release. Have at it! Hugh On Thu, Jul 30, 2020 at 5:49 PM Bauman, Syd <s.bauman@northeastern.edu> wrote:
RV> Since standOff made it last time, I think it may be ok to delay this if we risk delivering it a little half-baked. HC> I'd love to get it in if that's possible. Why don't I do a pull request, and we can either accept it or wait on it? RV> Sounds good -- happy to review NC> Indeed. I think a pull request would focus minds.
Y’all must think of pull requests quite differently than I do. I think of a pull request as a request that something be pulled in. I know full well the current state of sydb-standOff is such that it would not be acceptable to pull it into dev, especially right before a release.
If it will kick us into gear and get things done, be my guest. But I am very hesitant to issue a request that I know should be denied. (And I know I won’t put in any significant TEI work until the weekend.) So I am inclined to go with RV’s initial thought, and post an apologetic comment with a vague timetable to the ticket.
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
participants (5)
-
Bauman, Syd -
Hugh Cayless -
Nicholas Cole -
Raffaele Viglianti -
Syd Bauman