#288 deprecate use of gram except as a child of gramGrp

GREEN
open-accepted
5(default)
2013-12-08
2011-07-23
No

<gramGrp> is allowed as a child of both <form> and <sense>, but <gram> is allowed only as a child of <form>. I would like it added to <sense> as well in keeping with feature request 3266021 and in keeping with section 9.3.2, which implies that you can encode grammatical information either way.

Discussion

<< < 1 2 (Page 2 of 2)
  • Kevin Hawkins

    Kevin Hawkins - 2011-12-05
    • status: pending --> open
     
  • Kevin Hawkins

    Kevin Hawkins - 2011-12-05

    Oops. Some deprecated practice was corrected at revision 9848 but more remains to be fixed. Am working on that now.

     
  • Kevin Hawkins

    Kevin Hawkins - 2011-12-05

    Corrected another example at 9897.

     
  • Kevin Hawkins

    Kevin Hawkins - 2011-12-08
    • status: open --> closed-fixed
     
  • Kevin Hawkins

    Kevin Hawkins - 2012-07-23
    • labels: 1154492 --> Deprecated
    • status: closed-fixed --> open-accepted
     
  • Kevin Hawkins

    Kevin Hawkins - 2012-08-04

    Even before changing content models, I need to add status="deprecated" in the appropriate ODDs. But I can't figure out where to put this in order to carry out the intention of the ticket.

     
  • Kevin Hawkins

    Kevin Hawkins - 2012-09-20

    This is waiting on the formulation of a new TCW document by Lou and Kevin formulating a deprecation procedure. See http://wiki.tei-c.org/index.php/Deprecation and minutes from Sept. 2012 Oxford meeting. Then we can follow that procedure.

     
  • Kevin Hawkins

    Kevin Hawkins - 2013-06-21

    As discussed in Providence, this wasn't implemented propertly: <gram> is allowed inside <etym> but shouldn't be.

    Furthermore, since this is a deprecation according to http://www.tei-c.org/Activities/Council/Working/tcw27.xml , I can't figure out how to actually deprecate the use of <gram> when not in <gramGrp>. I think I need to deprecate model.morphLike as a member of model.formPart.

    If we're luckily, we'll even find a way to fix both of the problems above at once.

     
    Last edit: Kevin Hawkins 2013-06-21
  • Piotr Banski

    Piotr Banski - 2013-10-10
    • labels: Deprecated --> Deprecated, LingSIG
    • Priority: 5 --> 1(low)
     
  • Piotr Banski

    Piotr Banski - 2013-10-10

    (Resetting the priority back to "5", with apologies for the incident, while pointing my finger at the SF maintainers.)

     
  • Piotr Banski

    Piotr Banski - 2013-10-10
    • Priority: 1(low) --> 5(default)
     
  • James Cummings

    James Cummings - 2013-11-09

    Am I right that it seems that there is a problem in documentation of the deprecation and gram shouldn't be allowed inside etym? We should at least solve the latter asap if that is a problem.

     
  • Kevin Hawkins

    Kevin Hawkins - 2013-11-10

    Yes, that's right.

     
  • Piotr Banski

    Piotr Banski - 2013-11-10

    Just a reminder about Laurent's arguments for putting <gramGrp> into <etym>: http://tags.hypotheses.org/

     
    • Kevin Hawkins

      Kevin Hawkins - 2013-11-11

      The particular blog post that Piotr is referring to is http://tags.hypotheses.org/42 . (If Laurent keeps blogging and someone reads this ticket's comments in the future, they won't be sure which post we were reading!)

       
  • Piotr Banski

    Piotr Banski - 2013-11-11

    Right you are -- thanks, Kevin!

     
  • Martin Holmes

    Martin Holmes - 2013-11-12

    To clarify (per Council group discussion 2013-11-12): gram should be deprecated in all contexts except as a child of gramGrp, and as a child of entryFree and dictScrap (whose content models are loose by definition). gramGrp should replace it in any context where it is not yet available but gram is.

     
  • Martin Holmes

    Martin Holmes - 2013-11-12

    @Kevin, I suspect my comment was unintentionally confusing. We mean that gram should still be allowed in entryFree and dictScrap, because as you say their content models are different. The constraint should only apply in the structured contexts in which gramGrp should contain gram.

     
  • Kevin Hawkins

    Kevin Hawkins - 2013-11-12

    Ah yes, I see the syntactic ambiguity now. I think were fine then.

     
  • Kevin Hawkins

    Kevin Hawkins - 2013-12-08
    • assigned_to: Kevin Hawkins --> Syd Bauman
    • Group: AMBER --> GREEN
     
<< < 1 2 (Page 2 of 2)

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks