- From: Graham Klyne <GK@ninebynine.org>
- Date: Fri, 25 Apr 2003 11:31:15 +0100
- To: "Butler, Mark" <Mark_Butler@hplb.hpl.hp.com>, "'LYNN,JAMES (HP-USA,ex1)'" <james.lynn@hp.com>, "'Patrick.Stickler@nokia.com'" <Patrick.Stickler@nokia.com>, "Butler, Mark" <Mark_Butler@hplb.hpl.hp.com>, www-rdf-interest@w3.org, www-di@w3.org
At 15:38 24/04/2003 +0100, Butler, Mark wrote: >So to ask a subtly different question when we have two properties that are >aimed at different domains are we best creating separate properties and >relating them using something like RDFS or should we define them as being >the same? In my previous post, the example I gave was should we just use >expirationDate for pageExpirationDate and creditCardExpirationDate or should >we distinguish between them? Which is better modelling practice? > >The problem is often even though values seem to have the same semantics, >often we process those value in different ways and the nature of the >processing implies some semantics. I suspect there's often going to be an element of judgement about this. The case outlined here suggests to me that different properties would be appropriate, so that processing can easily be directed based on the property alone. In other cases, where a property may be used in different contexts but processed similarly, I think a common property may be easier. #g ------------------- Graham Klyne <GK@NineByNine.org> PGP: 0FAA 69FF C083 000B A2E9 A131 01B9 1C7A DBCA CB5E
Received on Friday, 25 April 2003 08:04:28 UTC