On Tue, 2004-10-19 at 09:40, Federico Sacerdoti wrote: > I just read this one again. I have a comment: since the [, ] characters (or > whatever 'open/close' symbols you use) dont match up, things seem wierd. > When I say dont match up, I mean in the "the number of opens != number of > closes" which is counter intuitive in some way, and feels unnatural: > > /[country/China/]group/cpu/]metric/number > > Of course I have a computer scientist's bias, I admit to that. However, I > suggest a simpler notation, like that of ldap: > > /Country=China/group=cpu/metric=number > > You could have the outer space class names capitalized, while the inner > space class names are all lowercase. > > Does this seem cleaner?
it looks cleaner but it doesn't give us the flexibility of a
class/instance directory structure.
how can we get a list of all groups for china?
/{country/China/{group/
would work to do that.
how would we do it with your scheme?
/Country=China/Group=*/ ?
implementing that would not be simple.
i guess we could do something like
/country=China/?group=*
using GET variables or something like that. again.. implementing that
would not be as simple.
we could drop the {} [] etc special characters so that it doesn't look
like open and close. for example, a . (dot) directory is usually
considered a "hidden" directory... we can also use '_' for inner space.
/.country/China/.group/cpu/_metric/number
it doesn't look as much like open and close tags.
-matt
--
PGP fingerprint 'A7C2 3C2F 8445 AD3C 135E F40B 242A 5984 ACBC 91D3'
They that can give up essential liberty to obtain a little
temporary safety deserve neither liberty nor safety.
--Benjamin Franklin, Historical Review of Pennsylvania, 1759
signature.asc
Description: This is a digitally signed message part
