Re: FW : CC/PP Components

Hi Art and All,

> ... (RDF itself certainly does not care.)

I don't agree at all. RDF does not impose formal constraints (e.g. if a
property has domain rdf:Resource, then for each resource can be asserted
that property, provided that everything pertains to this type because of
class specialization transitiveness). But in all case it's intended that a
property has its own identity that is associated with a precise meaning. For
semantic consistency it's not possible that a property has different
meanings when applied to subjects of different types. This kind of
polymorphism is not issued in the RDF-RDFS domain (I think). This could work
within a certain application domain, but not within the standard RDF-RDFS
domain.

> If CC/PP does not permit an Attribute (e.g. ExpirationDate) to
> be in different Components (i.e. CreditCard and Session) then
> it seems to me that CC/PP is broken.

CC/PP does permit that an attribute pertains to different components. What
you must do is just associate the attribute with your components' superclass
(e.g. ccpp:Component). But for whatever type of profile component you assert
that attribute, it's always the same vocabulary attribute that you instance,
with the same semantic. You cannot use the same attribute and intend
different thinks when it's asserted for profile components that are
instances of different component classes that extend the component
superclass with which you associated the attribute in your vocabulary. For
these goals you should define different attributes.

Regards,
Francesco

Received on Monday, 14 April 2003 08:25:04 UTC