Cart
[Home] [By Thread] [By Date] [Recent Entries]
Michael Kay wrote: >> A decade later, it still makes for strange conversation when >> the XML and Web communities wander into each other's turf, though. > > I don't think I understand what you mean by the "Web community". Whom does > it exclude? By "Web community" I mean the people for whom the Web is their first (and often exclusive) development target. Its borders are complex, but if you want a reasonable guideline, I'd point to the set of technologies on which the Web Standards Project focuses: http://www.webstandards.org/about/mission/ That's typically HTML, CSS, JavaScript, and the DOM. That's the core set of technologies I find discussed on web design and web development lists, and the core set on which the ever-growing set of web frameworks build. Web folks I know who care about data exchange often know about XML, but find JSON an easier fit for most applications. It also includes many sub-communities on the server side, who generate all that stuff using a wide variety of tools. Some of those subcommunities are XML-centric (or even XSLT-centric), but I can't imagine it's a large proportion of people. As for who it excludes, I don't think it excludes anyone who works with those core technologies - but degree of focus, priorities, and expectations certainly offer opportunities for culture clashes. It's not a simple binary, at least until argument is joined and people choose sides. (Who's in the XML community? The Web Services community? Who do they exclude?) -- Simon St.Laurent http://simonstl.com/
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
