XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
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] Re: Rules of Thumb for Creating XML Vocabularies for Workflow Applications [Was: Keep business-process-specific data separate?]


> > No, the question was what they need from the specification of the 
> > data. Even if they are not consumers of the data, they are 
> certainly 
> > consumers of its specification.
> 
> No, I don't think so - Roger's post said:
> 
> > 2. An XML vocabulary must support the data needs of both the data 
> > producers and the data consumers.
> 
> Perhaps you would rephrase Roger's point, but I don't think 
> that I've misunderstood what he wrote.
> 

Well, if you read "support the data needs of data producers" as "provide the
data needed by data providers" then it's clearly nonsense, so I assume
that's not what Roger meant. I read it as a precis of:

"The design of an XML vocabulary must take into account the need of data
providers to supply the data and the need of data consumers to use the
data".

Michael Kay
http://www.saxonica.com/



[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