Ambiguity in section 2.3.2 of the specification describing the EntryFactory
Legacy Issue Number: 4737
Source: Research Collaboratory Structural Bioinformatics ( Douglas Greer)
In section 2.3.2 of the specification describing the EntryFactory
Interface, there is a subtle ambiguity that if interpreted the
wrong way would might require indefinite locking of the underlying
data source. In particular the "get_entry_from_id()" method does
not specify a behavior if the id given was not in the list of
ids returned by the method "get_entry_id_list()" or
I propose that this be resolved by:
1) adding the following sentence at the end of the first paragraph
of the subsection labeled "Obtaining an Entry Object".
"This method may successfully return an Entry object even when
the id specified was not included in the list returned by
2) In the first two sentences of the subsection labeled "Retrieving
Lists of Entries" the word "known" be inserted after the word "all"
So that they read:
"get_entry_id_list() retrieves a list of all known entries.
The get_entry_modification_dates() method retrieves a list of all
known entries along with the date they were last modified.
Reported: MACSTR 1.0b1 — Wed, 5 Dec 2001 05:00 GMT
Disposition: Resolved — MACSTR 1.0
Make the two changes to the text as described below to remove the ambiguity
Updated: Fri, 6 Mar 2015 20:58 GMT