[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [obix] pre-meeting comments - version & retrievalDate
Ok – that is what my original example had – I took out the dual specification based on my (apparently incorrect) interpretation of the call last week. I will replace the example with both specified, to reinforce the notion that one is required, both are allowed.
Also- for the time of retrieval attribute name:
And should we stick with requiring abstime? The exact time seems unlikely to be important, but abstime seems a more common data primitive than date, since date is a 1.1 construct in OBIX.
My understanding, as a conformance issue, is that it is mandatory to have at least one (formal rev or retrieval time) but optional to have both.
“The single biggest problem in communication is the illusion that it has taken place.”
– George Bernard Shaw.
On your comment about line 769, it looks as though you are suggesting that the retrieval time be included EVEN IF the version information is also available. This is different than my understanding of our intent, which was retrievalDate exists ONLY if version info is NOT available.
Just throwing this out for others to weigh in.
Attached to this message as .rtf.