OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: Representation Types Alternatives

> b)  If the purpose is to constrain the value space *and* provide the
> analyst/modeler with a level of abstraction and higher level of
> reusability than the types offered by the Specification Schema, XML, or
> UML, then we should define a set of types rather than adopt one.  When
> defining the set, we should fully specify all of the relevant fields for
> each type (for example - measure has both value and units).

I would strongly object to ebXML defining "yet another set of datatypes".
What they should do is to formally define Representation Types in terms of
the data types defined by the Business Process team.

Martin Bryan

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC