Patrick Stickler wrote: > Also, from a management perspective, it's not scalable. Each time > a new model or a new version of a model is defined which uses some > term, one would have to go back and modify the namespace document > for the namespace name of that term -- but what if the owner of > the model is not the same as the owner of the namespace document? The what the heck are they doing putting their model in a namespace they don't own? Perhaps you can elaborate, but I just don't see a problem here. Evolving vocabularies is a tough job, certainly, but I don't see any way that namespace documents make it any harder to do than not having namespace documents. -- Elliotte Rusty Harold elharo@metalab.unc.edu XML in a Nutshell 3rd Edition Just Published! http://www.cafeconleche.org/books/xian3/ http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosimReceived on Friday, 18 February 2005 10:21:03 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:55:57 GMT