[Shared-desktop-ontologies-bugs] [Bug 30263] New class nie:StoredDataObject to store data objects in the database directly
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Dec 19 22:00:44 PST 2010
https://bugs.freedesktop.org/show_bug.cgi?id=30263
--- Comment #1 from phreedom.stdin at gmail.com 2010-12-19 22:00:44 PST ---
An alternative is to use data:// URI scheme to store the data directly,
especially since such a stored object won't have any other URI(unless we come
up with something).
A related use case that we need to consider is storing a copy of data in the
database.
It can be implemented by 2 DOs: one with data:// URI and another the "real"
one, both linked together by copy relationship.
Alternatively, it can be implemented by a slight tweak of your proposal:
introduce also nie:CachedDataObject to differentiate cached DOs from the ones
primarily stored in the database; or change nie:textContent and
nie:binaryContent domain to nie:DataObject to let you freely store caches and
use StoredDataObject as a marker for DOs primarily stored in the database.
Caches, however, tend to get out of date, especially if we talk about remote
resources. Should we care? Should we store the last fetch date? Where should we
store it: DO itself or use existing graph metadata?
Ideas?
Sorry for derailing such a simple change request but it's really a close topic.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Shared-desktop-ontologies-bugs
mailing list