I'm splitting this thread as not to confuse the issue of how to name
properties and classes from how to best organize these declarations.
> Sigfrid Lundberg, Lub NetLab <[log in to unmask]> wrote:
>
> > - Is there hooks for this in EOR toolkit merging and
> splitting schemas in
> > the EOR and/or SWAG
and Aaron writes...
> Currently SWAG finds subproperties by a (messy) substring
> search. It'd be
ouch... Collection management based on URI inspection, is as you say, messy
:)
As I recall, there was brief discussion at one time in RDF Schema Working
Group about requiring isDefinedBy relations on all declarations (err...
can't seem to find a link corroborating this) to facilitate this kind of
management. RDF in the end (and rightly so) did not decide to do this, but
left the decision to the communities using these technologies. Some
communites care about this, some don't. I certainly hope, however, in
somewhere DCMI's or SWAG's "good policy guide for designing RDF namespaces"
document, this issue would be recognized and the following strongly
encouraged:
(a) A means for describing vocabularies
e.g.
<eor:Schema rdf:about="http://purl.org/dc/elements/1.1/">
<!-- dumb down rule... use rdf:value for a simple default name -->
<rdf:value>The Dublin Core Element Set v1.0</rdf:value>
<dc:title>The Dublin Core Element Set v1.0</dc:title>
<dc:publisher>The Dublin Core Metadata Initiative</dc:publisher>
<dc:description>The Dublin Core metadata vocabulary is a simple vocabulary
intended to facilitate discovery of resources. </dc:description>
<dc:language>English</dc:language>
<dc:date>2000-03-13</dc:date>
</eor:Schema>
and
(b) rdfs:isDefinedby relations for all semantic declarations back to these
vocabularies
<rdf:Property rdf:ID = "http://purl.org/dc/elements/1.1/title">
<rdfs:label>Title</rdfs:label>
<rdfs:comment>A name given to the resource.</rdfs:comment>
<rdfs:isDefinedBy rdf:resource = "http://purl.org/dc/elements/1.1/" />
</rdf:Property>
Aaron continues...
> very nice to convert it over to following ifDefinedBy arcs
> which I think
> would do what you want.
Absolutely! An example of this kind of searching is as follows:
http://wip.dublincore.org/registry/OpenRegistry?subject2=&predicate2=http%3A
%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23type&object2=http%3A%2F%2F
dublincore.org%2F2000%2F03%2F13-eor%23Schema&db=registry1&next=/jsp/schema.j
sp
--eric
|