On May 13, 2009, at 12:05 PM, Julian Reschke wrote:
Nikunj Mehta wrote:
...
On the other hand, applications may use Atom's category term
attribute to ascribe computer-readable meaning to the specific
link. For example, CMIS shows a good number of such examples where
a single folder entry can have children of four different kinds -
policies, relationships, documents, and descendants [1].
...
As far as I can tell, @term is only allowed on atom:category? Are
you proposing to change that?
No I am not
If so: -1 -- we shouldn't introduce a new dimension on links; the
name of the relation plus the link target (media type, XML
namespace, whatnot) should be sufficient.
Intermediaries such as libraries, synchronization tools, and
aggregators won't understand 10,000 new link relations that every
vendor dealing with AtomPub is currently producing. IMHO, the rel
value should be understandable to intermediaries not only end points.
How is introducing another dimension for application-specified text
worse than creating a huge number of non-standard rel values? It
doesn't break any existing clients or servers.
We have encountered this issue while building synchronization tools,
but I suspect similar issues crop up for other intermediaries too.
Nikunj
