We're scheduled to remove @degree in 7.5 months. Should we be removing it from examples now? It occurs in 6 of them, all in "Certainty, Precision, and Responsibility": .../div[1]/div[2]/div[4]/specGrp[1]/elementSpec[1]/exemplum[1]/teix:egXML[1]/teix:precision[1] .../div[1]/div[2]/div[4]/specGrp[1]/elementSpec[1]/exemplum[1]/teix:egXML[1]/teix:precision[2] .../div[2]/p[5]/teix:egXML[1]/teix:precision[1] .../div[2]/p[5]/teix:egXML[1]/teix:precision[2] .../div[2]/p[6]/teix:egXML[1]/teix:residence[1]/teix:precision[1] .../div[2]/p[7]/teix:egXML[1]/teix:precision[1]
I think it's too close to the freeze to do this at the last minute. When we remove examples we should replace them with well-thought-out alternatives, and it's not so easy to do that under the gun. It's likely that @degree will just about survive into the release after this one, so how about raising a ticket to fix the examples as soon as this release is out, and then although it will still be there in the next, there'll be no examples of it? Cheers, Martin On 15-03-29 04:55 PM, Syd Bauman wrote:
We're scheduled to remove @degree in 7.5 months. Should we be removing it from examples now?
It occurs in 6 of them, all in "Certainty, Precision, and Responsibility":
.../div[1]/div[2]/div[4]/specGrp[1]/elementSpec[1]/exemplum[1]/teix:egXML[1]/teix:precision[1] .../div[1]/div[2]/div[4]/specGrp[1]/elementSpec[1]/exemplum[1]/teix:egXML[1]/teix:precision[2] .../div[2]/p[5]/teix:egXML[1]/teix:precision[1] .../div[2]/p[5]/teix:egXML[1]/teix:precision[2] .../div[2]/p[6]/teix:egXML[1]/teix:residence[1]/teix:precision[1] .../div[2]/p[7]/teix:egXML[1]/teix:precision[1]
Yeah. I was on the fence, but I'm mildly happier not trying to rush it in, despite the fact that the change is probably pretty trivial: in those 6 examples that have degree=, change it to precision= with a reasonable value. So in the end I'm with Martin on this. But personally, I tihnk we should have a better mechanism than raising a ticket to make sure we deal with deprecated items.
I think it's too close to the freeze to do this at the last minute. When we remove examples we should replace them with well-thought-out alternatives, and it's not so easy to do that under the gun.
It's likely that @degree will just about survive into the release after this one, so how about raising a ticket to fix the examples as soon as this release is out, and then although it will still be there in the next, there'll be no examples of it?
We could have a Jenkins job that runs every time the Guidelines builds, and fails if it finds something that will run out in the next X months. Easy to do. Cheers, Martin On 15-03-31 01:55 PM, Syd Bauman wrote:
Yeah. I was on the fence, but I'm mildly happier not trying to rush it in, despite the fact that the change is probably pretty trivial: in those 6 examples that have degree=, change it to precision= with a reasonable value. So in the end I'm with Martin on this.
But personally, I tihnk we should have a better mechanism than raising a ticket to make sure we deal with deprecated items.
I think it's too close to the freeze to do this at the last minute. When we remove examples we should replace them with well-thought-out alternatives, and it's not so easy to do that under the gun.
It's likely that @degree will just about survive into the release after this one, so how about raising a ticket to fix the examples as soon as this release is out, and then although it will still be there in the next, there'll be no examples of it?
Keep in mind that previously we decided (per the third bullet under "Deprecated" at http://www.tei-c.org/Activities/Council/Working/tcw27.xml ) to remove examples of deprecated practice immediately. In this case, you've decided not to do so because of an imminent release. That's a different matter. On 3/31/15 5:18 PM, Martin Holmes wrote:
We could have a Jenkins job that runs every time the Guidelines builds, and fails if it finds something that will run out in the next X months. Easy to do.
Cheers, Martin
On 15-03-31 01:55 PM, Syd Bauman wrote:
Yeah. I was on the fence, but I'm mildly happier not trying to rush it in, despite the fact that the change is probably pretty trivial: in those 6 examples that have degree=, change it to precision= with a reasonable value. So in the end I'm with Martin on this.
But personally, I tihnk we should have a better mechanism than raising a ticket to make sure we deal with deprecated items.
I think it's too close to the freeze to do this at the last minute. When we remove examples we should replace them with well-thought-out alternatives, and it's not so easy to do that under the gun.
It's likely that @degree will just about survive into the release after this one, so how about raising a ticket to fix the examples as soon as this release is out, and then although it will still be there in the next, there'll be no examples of it?
participants (3)
-
Kevin Hawkins -
Martin Holmes -
Syd Bauman