Leave a note about which properties are acceptable to use for OrderedCollection
Really, it needs to not change, and somehow fit "reverse chronological" order!
This commit is contained in:
parent
9eda0afd9f
commit
2acda78e9d
13
index.html
13
index.html
|
@ -674,6 +674,19 @@
|
||||||
MUST be presented consistently in reverse chronological order.
|
MUST be presented consistently in reverse chronological order.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
|
<p class="note">
|
||||||
|
What property is used to determine the reverse chronological order
|
||||||
|
is intentionally left as an implementation detail.
|
||||||
|
For example, many SQL-style databases use an incrementing integer
|
||||||
|
as an identifier, which can be reasonably used for handling
|
||||||
|
insertion order in most cases.
|
||||||
|
In other databases, an insertion time timestamp may be preferred.
|
||||||
|
What is used isn't important, but the ordering of elements must
|
||||||
|
remain intact, with newer items first.
|
||||||
|
A property which changes regularly, such a "last updated" timestamp,
|
||||||
|
should not be used.
|
||||||
|
</p>
|
||||||
|
|
||||||
<section id="followers">
|
<section id="followers">
|
||||||
<h2>Followers Collection</h2>
|
<h2>Followers Collection</h2>
|
||||||
<p>
|
<p>
|
||||||
|
|
Loading…
Reference in New Issue