Robert Shanbaum

Moderators
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Robert Shanbaum's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. Hi, Yaron, I apologize for being so tardy in replying. I'll go through your suggestions one-by-one. 1. I'm indifferent to the ordering of the revision history, but since it has been done newest first, it would take some work to revise it. Do you want to volunteer to do it, if the group approves of of doing it that way? 2. a) I also like "enumerated" better than "specified"; although it might be possible for only one literal value to be specified for a particular record's field value(s), in which case "enumerated" would be inappropriate. "Specified" is the more general of the two terms. However, we're splitting hairs here. "Enumerated" would be OK with me. b) We have always tried to enforce a measure of "terseness" in various text features. Just because a particular requirement can be relaxed when necessary doesn't mean that it's "effectively" a nullity. 3. Limited is there for a reason (namely, to limit the lengths of certain elements). My preference is to allow the constraint to be relaxed on an exception basis - if that's actually necessary. I don't recall why we added the "unless otherwise noted in the record definition." However, as I wrote earlier, I don't think that allowing an "override" eliminates its utility when it's not explicitly relaxed. 4. I'll ask Paul to fix the reference errors (he's still on board for that). 5. Same as (4), Paul will fix the revision history. 6. It was not my intention (or anyone else's, as far as I know) that this revision would change the location of an engraving. I agree that that is unacceptable.
  2. Hello, everyone. I hope you are safe and well. With any luck, you'll find a link on this message to a draft of the proposed version 3.13 of the Data Communications Standard. The first draft posted has a draft ID of 30; if any changes are made, and posted here, the draft ID will be incremented. Please download it, review it, and post any questions, comments, or objections on this forum, in this topic. I do not expect task force meetings to take place at the next Vision Expo West. We should try to discuss any issues that you may have with the draft on this forum; if it becomes necessary, we can arrange Zoom or GoToMeetings. I would like to be able to approve this version prior to our next meeting, which I expect to occur at Vision Expo East. DCS v3.13_DRAFT-030.pdf
  3. I think if the new requirements are respected - which includes limiting record label length to 16 characters - this is unlikely to be a problem. The problem situations that I've seen (where records exceed 80 characters) have generally been due to excessively long proprietary labels coming from LDS (for transmission, usually, to generators). I suspect that most LMSs have already dealt with this. The kinds of devices that might have issues with long records - I'm thinking of tracers and blockers - are unlikely to be receiving any such records in the first place.