• From: "Michael Kay" <mike@s...>
• To: "'Marcus Carr'" <mcarr@a...>
• Date: Tue, 3 Feb 2009 23:55:16 -0000

> > 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/

• Follow-Ups:
  • Re: Re: Rules of Thumb for Creating XML Vocabularies forWorkflow Applications [Was: Keep business-process-specific data separate?]
    • From: Marcus Carr <mcarr@a...>

• References:
  • RE: Re: Rules of Thumb for Creating XML Vocabularies for Workflow Applications [Was: Keep business-process-specific data separate?]
    • From: "Michael Kay" <mike@s...>
  • RE: RE: Re: Rules of Thumb for Creating XML Vocabularies for Workflow Applications [Was: Keep business-process-specific data separate?]
    • From: "Michael Kay" <mike@s...>
  • Re: Re: Rules of Thumb for Creating XML Vocabularies forWorkflow Applications [Was: Keep business-process-specific data separate?]
    • From: Marcus Carr <mcarr@a...>