What do you call the concept of "classes" or "types" of resources in your RESTful designs? E.g. when you decide to turn each "customer" into its own...
I usually use "object type." It's not very accurate, but it seems to get the point across w/o much confusion. MikeA ... -- mca http://amundsen.com/blog/...
Hi Stefan, I think that the resources actually do not have a type (only an observable 'duck type' :-) and that what you refer to is actually the type of the...
... It's exactly for this reason that I feel uncomfortable with "type" and "class" - they imply a static relationship between the resources and their...
... I don't want to suggest there's this kind of coupling (in fact I view the lack of it as a strength, and this is why I'm unhappy with "type"). What does the...
Hiya, ... As other have pointed out, they're just "resources", pretty much typeless at the URI interface level. I'm keen to know why you ask? Many years ago...
... They are resources. But resources can be types (classes). And types need not be strongly coupled. That is what RDF [1] is all about btw. Assuming you have...
... Fair question: I'm trying to describe the process of RESTful application (or interface) design. Maybe I should just leave it "decide which kinds of...
... Good question. I think the answer is 'yes', but as such not defined within the REST scope itself. I tend to favor DDD (Domain-driven Design) these days, so...
Hi The package model[1] is useful to think about. REST is an interface / FACADE model and the templates form a package and you drill deeper and deeper by...
... Isn't the whole point that it does not make sense to say 'kinds of resources'? Talking about kinds of resources is misleading because grouping the...
... Not at all. This is perhaps the way you would like the world to be. But REST is just about resources and representations. You may think something ending in...
IMHO It's not about the user of the facade. Yes the user just discovers at runtime the representation-types and possible next application states and always...
Hi, ... Apache Sling [1] uses "resource type" (and even "supertype") and it seems to work fine for our users. -Bertrand [1] http://incubator.apache.org/sling...
... Yes. ... Because those implementations behind the interface are not the same as the resources exposed through the interface. Even in the simple case,...
... So maybe the relevant concept from the client's POV is representation type? E.g. media type?...
Bob Haugen
bob.haugen@...
Sep 2, 2008 3:54 pm
11240
Hi That was exactly my point! :) I don't like what I said for this reason .... that "packages" makes the developer think that pretty / intuitive URLs are...
A response to Bob and to Roy, concatenated here. (probably bad practice) ... No that is yet something else. (though also important) A resource can return...
... I'm curious what the assembled minds think about quotes like this from AtomPub: "A Resource whose IRI is listed in a Collection is called a Member ...
... I've fought a "battle" on the AtomPub list before about these issues (I think member resources is a terrible name), but I think consensus there is that...
Response below. ... I was using media types as an example, and I was thinking of types like application/EDIFACT, which could then go on to tell you that this ...
Bob Haugen
bob.haugen@...
Sep 2, 2008 6:08 pm
11245
... I'm with Alex, Roy and Henry on this. For me, the usage of terminology such as "resource types" or "kind of resources" is misleading. They are just...
... ...from the client perspective. How you map urls to things on a server when you build those urls need to match the type/instance topology, where a resource...
... So let's say we design a RESTful interface to a discussion group implementation. There are members, postings, threads, … in my world view, these map to...
... I tend to call these "entities", avoiding the bloated "objects" and the RESTful clash with "resources". I have ; - Containers of entities - Entities An...
Home page: http://bblfish.net/ ... from what you say: /postings refer to resources that are a collections of posts (an atom Feed perhaps?) /postings/1234...
... But awol:Feed and awol:Entry "are" owl:Class, right? If so, it appears that your answer to my question would be "class" (I am aware that this means...