#172 "overriden" as a valid value for curStatus

Mike Jarmy Tue 6 May 2014

It was brought to my attention at the Niagara Summit that "overridden" is not one of the valid values for the curStatus tag. Why is that? I mentioned it to a couple of people and there was general agreement that it would be really useful.

Its worth noting that NHaystack currently will report "overridden" as a value for curStatus. This is arguably a bug, since it doesn't follow the haystack spec.

So should we fix NHaystack, or should we add "overridden" as an allowable curStatus value? What are the pros and cons?

Brian Frank Tue 6 May 2014

I don't think we can say what the final decision should be without making a decision on how overrides should work. But in all the discussions so far, there was no options to make it part of curStatus. Long discussion at topic 103

Mike Jarmy Tue 6 May 2014

Hmm. Well that is a very interesting and complex discussion. Apparently the subject is a little more complicated than I thought :-). It looks like a resolution was never reached though.

For the time being I will change NHaystack to follow the spec. I guess this means that an AX status of "overridden" will be treated as an "ok" -- I'm not sure what else to do with curStatus. Perhaps I should include an axOverridden tag as well?

Brian Frank Tue 6 May 2014

AX status of "overridden" will be treated as an "ok" -- I'm not sure what else to do with curStatus. Perhaps I should include an axOverridden tag as well?

I agree that seems safest approach - gives you future proofing in nhaystack, but still you have the flexibility to add whatever we define for overrides formally

Login or Signup to reply.