OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Is Resource/Representation a fruitful abstraction?

[ Lists Home | Date Index | Thread Index ]

Paul Prescod wrote,
> Miles Sabin wrote:
> > I also think that "Resource Oriented Programming", or something
> > similar, is a useful design methodology or organizing principle.
> > But that's _all_ it is, and like you I see no reason why it should
> > be promoted at the expense of all other methodologies or organizing
> > principles.
> That's motherhood and apple pie. You would have a hard time finding
> anyone who would claim that there is one true design methodology.

You'd have thought so. But then you go on to say,

> What _I_ would claim is that when you build an information system
> (like the Web) you must choose a set of principles that will hold
> common for all objects in that system. COM has such a set of
> principles. Java has such a set. The TAG's job is to define those
> principles for the Web. If you deny them the right to exclude you
> deny them the ability to succeed.

I think this is your problem. The web isn't *an* information system. 
It's many information systems, and much else besides, loosely knitted 
together by a mixture of practices, conventions, protocols and 
software. The assertion that there's a *single* design methodology or 
organizing principle as specific as REST which is adequate for all of 
these is precisely the spurning of motherhood and apple pie you claim 
to be disclaiming.




News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS