• From: "Costello, Roger L." <costello@m...>
• To: "'xml-dev@l...'" <xml-dev@l...>
• Date: Wed, 4 Feb 2009 07:50:35 -0500

> > 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".
> 
> That would be a much better way of phrasing it.

Thanks Michael and Marcus. I changed the phrasing:

http://www.xfront.com/rules-of-thumb-for-creating-xml-vocabularies-for-workflow-applications.ppt

/Roger

• 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...>
  • 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...>