Opened 12 years ago

Closed 6 years ago

#409 closed defect (wontfix)

don't allow empty keys

Reported by: steve@… Owned by: steve@…
Priority: major Milestone:
Component: api Version:
Keywords: Cc:

Description

empty keys: ='foo' don't make sense and shouldn't be accepted by the API

Change History (4)

comment:1 Changed 12 years ago by lorp@…

On the contrary, empty keys do make sense.

The useful part of a key-value pair is always the value; the key is metadata. Normal 'tags', as understood by Flickr and the rest of Web 2.0, are the bare data without any metadata. Perhaps metadata will be added later (by someone else?), perhaps never (sometimes it's difficult to think of metadata). Another way of thinking of the 'key' part is as the predicate in an <a href="http://www.w3.org/TR/rdf-concepts/#section-Concepts">RDF-style subject-predicate-object triple</a>. Much as RDF and TBL crave predicates, communities love to associate subjects and objects without them!

comment:2 in reply to:  1 Changed 12 years ago by Immanuel Scholz

Replying to lorp@lorp.org:

On the contrary, empty keys do make sense.

The useful part of a key-value pair is always the value; the key is metadata.

the "Key" and the "Value" are both value. Only because some people don't like the fact that you can add something like "nice_and_cheap_pub_on_left_side"="yes" doesn't make it invalid.

And only because some people think there are only a specific set of keys "allowed" doesn't make it invalid either.

(Should we discuss stuff in a ticket system? Move to the list?)

comment:3 Changed 12 years ago by Tom Hughes

Component: rails_portapi

comment:4 Changed 6 years ago by iandees

Resolution: wontfix
Status: newclosed

Cleaning old tickets.

Note: See TracTickets for help on using tickets.