#2534 NORM Untriag: Datastore property naming policy needed

[Zarro Boogs per Child]

#2534: Datastore property naming policy needed
--------------------+-------------------------------------------------------
 Reporter:  bert    |       Owner:  dcbw     
     Type:  defect  |      Status:  new      
 Priority:  normal  |   Milestone:  Untriaged
Component:  sugar   |     Version:           
 Keywords:          |    Verified:  0        
--------------------+-------------------------------------------------------
 Certain names for properties may not be used in the datastore because they
 are used to define query parameters ("limit", "order_by", "mountpoints")
 or are only present on return ("uid", "mountpoint").  Others are reserved
 for Journal use ("ctime", "activity", etc.). Some are required, some
 optional. A single journal object may be opened by differing activities,
 which might want to add differing metadata.

 So we need something to avoid name clashes. Simplest seems to be setting a
 policy on names. For example, upper/lower case first letter could signify
 sytem/private properties. Or a special character, like an "_" prefix
 signifies query parameters. Or activity-specific properties could be
 required to use an org.domain.key scheme. Etc. But some policy seems to be
 needed.

 I documented the current expected behavior as best as I could here:

 http://wiki.laptop.org/go/Activity_DBus_API#Datastore

 Assigning this to sugar since if this is policy only, the datastore should
 not care about what keys are used. OTOH it might enforce policy ...

-- 
Ticket URL: <http://dev.laptop.org/ticket/2534>
One Laptop Per Child <http://laptop.org/>