10000-011: Historical Access - Change Log

10000-011: Historical Access - 1.03

Released 2013-08-06
View Issues1.0310000-011: Historical Access
  • 0003236: [Spec] Aggregate Configuration type missing from Historical capabilities (Paul Hunkar)
  • 0002887: [Spec] Continuation point handling for large HistoryRead requests (Rod Stein)
  • 0002477: [Spec] 6.4.5.2 ReadAtTime when SimpleBounds=TRUE/FALSE (Rod Stein)
  • 0003091: [Spec] OperationLimitsType - MaxNodesPerHistoryUpdateXxx issues (Rod Stein)
  • 0002471: [Spec] HistoryUpdate: Validation on inserting records exceeding the bounds of the database (Rod Stein)
  • 0002985: [Spec] Typo in 5.6.4 AuditHistoryDeleteEventType (Rod Stein)
  • 0002784: [Spec] What does 'ProcessingInterval=0' mean (Rod Stein)
  • 0002667: [Spec] Description of Continuation Point (6.3) does not match general concept (Rod Stein)
  • 0002584: [Spec] 6.8.7.2 DeleteAtTimeDetails "all entries" clarification (Rod Stein)
  • 0002531: [Spec] 6.8.3.2 Uniqueness of Annotation records - do not include message for uniqueness (Rod Stein)
  • 0002517: [Spec] "Subtype of" for "Inherit the properties" (Rod Stein)
  • 0002469: [Spec] ServerTimestamp support, possibly make available as a property for clients to discover? (Rod Stein)
  • 0002446: [Spec] 6.4.3.3 Read Modified Functionality: Para 1 is confusing; should original value be returned? (Rod Stein)
  • 0002445: [Spec] 4.3 Timestamps: Client requests TimestampsToReturn.Both, what if server supports Source only? (Rod Stein)
  • 0002373: IEC comment: Is A.1 normative? Or informative? (Rod Stein)
15 issues View Issues