Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Mike Orr
On Thu, Dec 16, 2010 at 8:57 PM, Mark Ramm wrote: > It would go something like this: > > Pyramid dispatch is based on a two phase system. > > The first phase is called Resource Location, and in it we use the URL > (Universal Resource Locator) to find a resource.  This is done by > taking items fro

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Daniel Holth
+1 'resource' is awesome. I retract all my previous objections. Thanks wordsmiths Mark and Chris. -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group,

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Mike Orr
By the way, I earlier suggested reorganizing the manual to put the URL Dispatch chapter first and then the Traversal and Hybrid chapters. Putting Traversal first is a significant stumbling block for those who aren't used to it. The outline I suggested is here: http://groups.google.com/group/pylons

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Mike Orr
On Fri, Dec 17, 2010 at 10:09 AM, Christoph Zwerschke wrote: > Am 17.12.2010 15:42 schrieb Graham Higgins: >> >> For example, "model graph" (used in the Pyramid docs) suffers from >> the same difficulty as does "little baby". It unnecessarily >> complicates the narrative with a tautological concep

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Robert Smallshire
As a relative newcomer to Python web development (although I'm an experienced developer in other respects) I don't find the word 'model' confusing so long as it is qualified with the word 'traversal' as in 'traversal model'. Almost any non-trival application uses the word model contextually, with

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Christoph Zwerschke
Am 17.12.2010 15:42 schrieb Graham Higgins: For example, "model graph" (used in the Pyramid docs) suffers from the same difficulty as does "little baby". It unnecessarily complicates the narrative with a tautological conceptual entity. This btw is another reason why I don't like the term "model

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Chris Withers
On 17/12/2010 12:37, Marius Gedminas wrote: On Thu, Dec 16, 2010 at 11:57:42PM -0500, Mark Ramm wrote: The main reason behind me asking Chris about this is that I can imagine writing a simple explanation of the "traversal" model which makes sense to a variety of TG, Zope, and even Django users.

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Graham Higgins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17 Dec 2010, at 12:05, Graham Higgins wrote: As did Tim Berners-Lee ... Sorry about the noise. Periodically, Googlegroups plays silly beggars with my posts, marking them down as likely spam --- even for the Shabti group for which I am the /

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Graham Higgins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 /me tries yet again (good grief Google, get a grip) On 17 Dec 2010, at 04:57, Mark Ramm wrote: I think resource is a good term for items in the graph As did Tim Berners-Lee when he coined the referents "URI" and "URL". Note that a URI is still t

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Graham Higgins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17 Dec 2010, at 04:57, Mark Ramm wrote: I think resource is a good term for items in the graph As did Tim Berners-Lee when he coined the referents "URI" and "URL". Note that a URI is still termed a "resource" even if it does not have a corr

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Graham Higgins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17 Dec 2010, at 04:57, Mark Ramm wrote: I think resource is a good term for items in the graph As did Tim Berners-Lee when he coined the referents "URI" and "URL". Note that a URI is still termed a "resource" even if it does not have a corre

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Graham Higgins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (tries again...) On 17 Dec 2010, at 04:57, Mark Ramm wrote: I think resource is a good term for items in the graph As did Tim Berners-Lee when he coined the referents "URI" and "URL". Note that a URI is still termed a "resource" even if it does

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Kent Tenney
> The ones I don't like because they're meaningless: > > - "atom" > > - "entity" > > - "node" > > The meaningless ones above aren't disqualified because they're > meaningless, though.  I would just rather have something with some sort > of meaning. I don't think "node" is as meaningless as the oth

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Thomas G. Willis
On Dec 17, 6:16 am, blaflamme wrote: > +1 for your wording Mark additional +1 I recently experienced the pain of having to explain traversal and why it was so cool and necessary for the app we are building. It was very much like showing a dog a card trick. -- You received this message because

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Paul Everitt
Me too. Of course, when something makes sense to me (e.g. XSLT) it is usual a sign of impending doom. --Paul On 12/17/10 9:05 AM, Chris Rossi wrote: Sold. +1 Chris On Thu, Dec 16, 2010 at 11:57 PM, Mark Rammwrote: So, I will confess to being the one who asked for this change, and while

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Chris Rossi
Sold. +1 Chris On Thu, Dec 16, 2010 at 11:57 PM, Mark Ramm wrote: > So, I will confess to being the one who asked for this change, and > while I'm definitely open to other options, I think resource is a good > term for items in the graph. The graph itself I'm not sure what to > call, but I thi

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Mark Ramm
On Fri, Dec 17, 2010 at 3:51 AM, Andrey Popp <8may...@gmail.com> wrote: > Hello, > > On Fri, Dec 17, 2010 at 7:57 AM, Mark Ramm > wrote: >> I think resource is a good term for items in the graph. > > Why you think resources are need to be bound to locations in graph? I > think it's better to thin

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Marius Gedminas
On Thu, Dec 16, 2010 at 11:57:42PM -0500, Mark Ramm wrote: > The main reason behind me asking Chris about this is that I can > imagine writing a simple explanation of the "traversal" model which > makes sense to a variety of TG, Zope, and even Django users. > > It would go something like this: >

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread blaflamme
+1 for your wording Mark -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more optio

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread AD.
On Dec 17, 5:57 pm, Mark Ramm wrote: > The main reason behind me asking Chris about this is that I can > imagine writing a simple explanation of the "traversal" model which > makes sense to a variety of TG, Zope, and even Django users. > > It would go something like this: > > Pyramid dispatch is b

Re: pyramid terminology: "model"->"resource"

2010-12-17 Thread Andrey Popp
Hello, On Fri, Dec 17, 2010 at 7:57 AM, Mark Ramm wrote: > I think resource is a good term for items in the graph. Why you think resources are need to be bound to locations in graph? I think it's better to think that graph consist of locations and each location has associated resource. For examp