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


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [xml-dev] Should XML ever be presented to 'users' (Was: Re:[xml-dev] ANN: a portable data component -- length)

This isn't "data" in the sense of the discussion up to now, but we're training editors of procedure manuals to use oXygen to maintain their content (in a Documentum repository).  These folks are all attorneys, experts in industrial property law.  They've had about four days of training in oXygen and XML and, so far, have overcome all the obstacles to taking full ownership of their content.  They aren't permitted to change the schema or style sheets, since they are common to several manuals, but they advise developers on changes that might be needed.  Let's face it, XML itself isn't rocket science, even if good schema design requires an artist.

Don't spreadsheets routinely store calculated values along with formulas so that the answer can be rendered even where there is no processor to perform the calculations?  So, it isn't always the case that "just don't do that" is practical.

Bruce B Cox
Director, Policy and Standards Division, OCIO, USPTO

-----Original Message-----
From: Bill Kearney [mailto:wkearney99@hotmail.com] 
Sent: 2011 April 9, Saturday 22:12
To: xml-dev OASIS
Subject: Re: [xml-dev] Should XML ever be presented to 'users' (Was: Re: [xml-dev] ANN: a portable data component -- length)

Because, in that analogy, the passengers aren't paying for a engine room tour.  They're paying for the cruise experience, not the behind the scene infrastructure necessary to make it happen.  Arguably the same thing goes for many, if not all, situations where a 'user' might interact with a system that utilizes XML behind the scenes.  The users aren't paying for the the thrill of seeing XML parsing in action, they're expecting an application of some sort to do it's job.

That said, just because a system is 'designed' to operate without users seeing the raw data, it doesn't mean the system shouldn't be programmed to 
ward off problems users interaction might cause.   Assume the data could 
suffer all manner user-inflicted problems.  Never assume otherwise.  For at some point someone will decide it's worth mucking around with the data.

-Bill Kearney

-----Original Message----- 
> From: Simon St.Laurent Why bury the good stuff in the engine room?  Or 
> at least, why lock tourists out of the engine room?

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

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

Copyright 1993-2007 XML.org. This site is hosted by OASIS