Cart
|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: menuml -restaurant menu xml prototype app
 thanks for taking the time to provide input, Michael.
Going points as always. It is an honor to get your
input.
I have always liked your input and am a big fan of
Saxon.
I hope people do take in the direction as you
suggested.
As in the write up this was meant to be a working sample
which i should have attached outside the zip i think.
it was designed to meet the basic/simple needs for a
small restaurant like my parents had.
For a full blown standard it should have the things you
suggested.
Perhaps from a human factors point of view making
too comprehensive vocabulary can make the XML too involved, and then
people may not want to mark up to such a large extent and then
people give up on the ending XML as being annoying. Also i recall
many times adding completeness which never got used in b2b
formats.
That is why design is an art rather than a
science.
This is just a small start so people can keep the effort
going.
Also when i started if I had this code it would have saved me time. best,
Dhruv From: Michael Kay [mailto:mike@saxonica.com] Sent: Saturday, September 26, 2009 5:55 PM To: Sharma, Dhruv; xml-dev@lists.xml.org Subject: RE: menuml -restaurant menu xml prototype app Designing a vocabulary that can be used across a whole
industry requires much more effort than a vocabulary that can be used in-house
by one small company. Your analysis doesn't seem to have considered menus from
many different establishments. Examples of things you don't
cover:
* dishes that can only be ordered for a minimum number of
persons
* attributes of each dish (vegetarian, contains nuts,
hot/medium/mild, available as child's portion)
* options for a dish that can be specially requested (e.g.
medium/rare, potatoes/rice) either at the standard price or at extra
cost
* description of the dish in multiple
languages
* pricing in multiple currencies
* meat or fish dishes where the price is per
Kg
* wines, where there are typically different prices per
bottle or per glass, sometimes with different sizes of bottle or
glass
I would also expect to see an XSD or RelaxNG schema with
extensive comments, not a plain uncommented DTD.
I'm afraid this looks more like a quick student exercise
than a professional schema design informed by methodical data
analysis.
Regards,
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! 
Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||
