- From: Marc Carrion <marc_carrion@yahoo.es>
- Date: Fri, 31 Jan 2003 08:02:26 -0800 (PST)
- To: Brian McBride <bwm@hplb.hpl.hp.com>, "Stephen K. Rhoads" <rhoads@thrupoint.net>, www-rdf-interest@w3.org
--- Brian McBride <bwm@hplb.hpl.hp.com> wrote:
>
> As you point out, sometimes one can have properties
> that are pretty general
> in nature. Lets take name as an example. One
> option is, for each such
> property, is to define a class for its domain, say
> Nameable. Then you, or
> anyone else, can define, each class that can take a
> name to be a subclass
> of Nameable. This approach can support data
> validation and adaptive user
> interfaces, but its not much good for inferring
> types of things from their
> properties.
>
You will be able to define abstract class in order
to don't let people to create an instance of Nameable
Class if you want to use the adaptive user interface.
Marc
=====
......\|||/................................................
(. .)
-oOOo---0---oOOo-------
|marc_carrion@yahoo.es|
| ooO Ooo |
----( )--( )-----------
() ()
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
Received on Friday, 31 January 2003 11:02:32 UTC