[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsia][wsia-requirements][R413]
I *think* I understand the intent but not necessarily the motivation. Are
rich semantic descriptions of property values and relations a *requirement* or a
"nice to have" feature of a particular API? I can see the value of having
*human-readable* meta-information (aids the user of the Web Service). I can see
the value of type constraints a-la Schema (mainly helping the Consumer map
properties into programming constructs). Can anyone clarify the value of richer
constraints?
Or, maybe, can we perhaps define this requirement as open for
extensibility, for example:
This specification should permit the Producer to specify additional
machine-readable semantic information regarding properties.
...which would lead to a construct such as Schema's <app-info>
which allows arbitrary (but not specified) type constraints and
information.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC