- From: Thomas Hoppe <thomas.hoppe@n-fuse.de>
- Date: Thu, 20 Feb 2014 20:37:17 +0100
- To: public-hydra@w3.org
>>> So this is why I would call them Parameters; >> Without thinking about it: I don't like it because this reminds me of a function call and >> as we are network transparent: RPC and we all know that this is the tabu word in the REST world. > Yes, I agree that might not be the best name; we definitely don't want to cause RPC confusion. > However, it can't be Property either if it's not a property. That's too confusing. > > Let's find another word. Here's my ordered list of preferences: > - Attribute > - Feature > - Aspect > >>> Example: the movie object has a parameter >> Hmm, objects cannot have parameters in my IT vocabulary. > Okay, it's really a "property", I know :-) > But we have to live with the fact that "property" > is reserved for something else in the RDF world. > > Do you like: > the movie object has an attribute > that corresponds to the property "foaf:maker", > but it is read-only. Yes, I like that! All other terms we discussed have to little connotation with IT. For me attribute and property were synonyms but according to Wikipedia (http://en.wikipedia.org/wiki/Attribute_%28computing%29) you are right with your second mail. So +1 > > Actually, I like "attribute" a lot. > It's neutral. It conveys the intended meaning. > > Best, > > Ruben
Received on Thursday, 20 February 2014 19:37:45 UTC