Altova Mailing List Archives

Re: [xml-dev] The triples datamodel -- was Re: [xml-dev] Semantic Web permathread, iteration n+1

From: Robert Koberg <rob@------.--->
To: Elliotte Rusty Harold <elharo@-------.---.--->
Date: 6/7/2004 11:49:00 PM
I am all for learning new things, as I am sure most people here are. Can 
you describe the system and/or provide a case study? I have only heard 
you describe a philosophy so far.

Most of my users don't even know they are using a schema (or XML, for 
that matter). The hardest part for them to grasp is that styling is 
separate from the content. They love having appropriate lists of 'valid 
things' to add at certain place -- they even get excited about not 
having to guess (they are busy people): Think of it like a busy 
intersection with a stoplight. If they need something different/new it 
can be changed/removed/added.


Elliotte Rusty Harold wrote:

> At 11:00 PM +0200 6/7/04, Henrik Martensson wrote:
>> What would you have done if you had to deal with information from fifty
>> different sites, and all fifty made their own, frequently incompatible,
>> changes? (This is a far more common situation in my line of work than
>> having to deal with only one data provider.)
>> Writing fifty different XSLT stylesheets does not sound like a good
>> solution.
> It's easier than getting 50 different organizations to agree, and then 
> to conform to that agreement. 50 different stylesheets is not that hard, 
> especially when most of them are likely to be simple variations of each 
> other. I can easily write 50 stylesheets in 50 days, probably less. I'd 
> be very surprised if 50 companies could agree to anything in 50 days.
>> For me it is different. I work with fairly large companies. The data
>> providers are either departments or subcontractor. In such situations,
>> trying to adapt to everyone else simply does not work.
> Why not? Have you tried it and watched it fail? If so, please do 
> elaborate on your experience. If you'd like I can probably get you a 
> slot at SD 2005 West to talk about it. (They love case studies.) But 
> like extreme programming, nobody believes this approach can possibly 
> work, until they try it and see that it does. And then they can hardly 
> believe they ever did it any other way.


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.