From looking at the code I think this would add a lot of overhead. One way
to get around this and provide the same function is to provide:
Item #1 http://purl.org/dc/elements/1.1/title [link]
[further-refinements-link]
rdf:type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property [link]
rdfs:label Title
rdfs:isDefinedBy http://purl.org/dc/elements/1.1/ [link]
rdfs:comment A name given to the resource.
eor:comment Typically, a Title will be a name by which the resource is
formally known.
The following is already there - we just need to change the human-readable
label:
Item #17 &dcqns;alternative[link]
rdf:type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property [link]
rdfs:label Alternative
rdfs:isDefinedBy &dcqns; [link]
rdfs:comment A alternative name given to the resource.
eor:comment Typically, a Alterntive Title...
refines: &dcmes;title [link]
What do you think? Harry
> -----Original Message-----
> From: Eric Miller [mailto:[log in to unmask]]
> Sent: Wednesday, August 22, 2001 1:55 PM
> To: [log in to unmask]
> Subject: Re: Prototype Changes
>
>
> At 01:29 PM 8/22/2001 -0400, Wagner,Harry wrote:
> >Eric,
> >Let me make certain I understand you before I make the
> schema changes...
> >You are proposing we add 2 new properties to the eor schema;
> 'refines' and
> >'isRefinedBy'. Is this correct?
>
> No. "is refined by" is a human readable label reflecting the
> rdfs:subPropertyOf | rdfs:subClassOf relationships in one direction,
> "refines" is a human readable label reflecting these
> relationships in the
> other direction.
>
> The data is (or should be) already in the schema... you just
> need to query
> for it and reflect this in the interface.
>
> --
> eric miller http://www.w3.org/people/em/
> semantic web activity lead mailto:[log in to unmask]
> w3c world wide web consortium tel:1.614.763.1100
> 200 technology square, ne43-350 fax:1.208.330.5213
> cambridge, ma 02139 usa
>
|