View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002558 | 10000-011: Historical Access | Spec | public | 2013-08-01 19:53 | 2017-06-13 15:44 |
Reporter | Assigned To | Rod Stein | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0002558: Annotations; How to Insert the first annotation? | ||||
Description | CMPWG Aug-1-2013: The "Annotation" property signals when annotations are available on a node. There is an inconsistency in the spec also. Part 11 section 5.12 Table 2 states "... is used to indicate that Annotation data exists ..." where 2 paragraphs below the text says "... whether or not a HistoricalDataNode supports Annotations." Which is correct? | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
|
CMPWG Aug-8-2013: Can a Client insert Annotations and specify a source timestamp where there is no history, e.g. history at 12:00 and 12:05, but client inserts annotation at 12:03. Is this allowed? or should the client insert a record first with bad quality data etc. so that it can annotate that? |
|
Discussed in telecon. Spec needs to be clarified that to enter the first annotation, the client must first add the Property. Also the text that describes the property needs to be more clear that nodes without the property may still support annotations. |
|
I was not able to be on the call when this was discussed, but my understanding is that the second paragraph quoted about is correct and the first one needs clarification. The Annotation property should exist on any node that supports annotations regardless of whether any currently exist. This is how a client knows if annotations can be added to a given node. Otherwise, the client has to let the user assume an annotation can be added to a node until the call to add the annotation fails. Also, not all servers support clients adding nodes or properties. |
|
Fixed in 1.04 Part 11 Draft 0 Added two basic parts. That the Annotation Property must exist to have annotations on a HistoricalDataNode and the property must be on any node that supports having annotations. Also that servers that support it can add the property to a HistoricalDataNode or remove it. Added errata to 1.03.4 |
|
Agreed to changes edited in telecon. |
Date Modified | Username | Field | Change |
---|---|---|---|
2013-08-01 19:53 |
|
New Issue | |
2013-08-01 19:54 |
|
Relationship added | related to 0002478 |
2013-08-08 16:40 |
|
Note Added: 0004910 | |
2013-08-13 16:58 | Jim Luth | Status | new => assigned |
2013-08-13 16:58 | Jim Luth | Assigned To | => Rod Stein |
2013-08-13 16:59 | Jim Luth | Note Added: 0004917 | |
2013-08-13 18:24 | Mark Rice | Note Added: 0004920 | |
2014-08-19 17:37 | Jim Luth | Category | (No Category) => Spec |
2014-08-19 17:37 | Jim Luth | Target Version | => 1.03 |
2015-06-01 22:20 | Rod Stein | Target Version | 1.03 => 1.04 |
2016-12-15 20:38 | Rod Stein | Note Added: 0007573 | |
2016-12-15 20:38 | Rod Stein | Status | assigned => resolved |
2016-12-15 20:38 | Rod Stein | Fixed in Version | => 1.04 |
2016-12-15 20:38 | Rod Stein | Resolution | open => fixed |
2017-06-13 15:44 | Jim Luth | Note Added: 0008228 | |
2017-06-13 15:44 | Jim Luth | Status | resolved => closed |