Skip to Content.
Sympa Menu

cc-uk - [Cc-uk] (no subject)

cc-uk AT lists.ibiblio.org

Subject: Cc-uk mailing list

List archive

Chronological Thread  
  • From: Enrico Silterra <es287 AT cornell.edu>
  • To: cc-uk AT lists.ibiblio.org
  • Subject: [Cc-uk] (no subject)
  • Date: Mon, 26 Apr 2004 12:21:42 -0400

I am a little unclear on the range of the prohibits, permits
properties.

I am proposing to encode a set of data base permissions in
RDF/CC, some thing like this:

There is a permission to interlibrary loan via fax
So,
I would create
<Permission rdf:about="http://www.ermi.example/ermi/InterLibraryLoanFax";>
<dc:title>Ill load via fax</dc:title>
<dc:description>Inter Lib Loaning via fax</dc:description>
</Permission>

But? Sometimes loaning is forbidden.
Do I need to create a corresponding prohibition?
<Prohibition rdf:about="http://www.ermi.example/InterLibraryLoanFax";>
<dc:title>Ill load via fax</dc:title>
<dc:description>Inter Lib Loaning via fax</dc:description>
</Prohibition>

Am I missing something?
What if someone AllowsCommercialUse?
The schema seems to me to say, that since this is a Prohibition, it can not
be the target of permits, that one can never allow this?


The fact that the range of the permits property is permissions,
and the range of prohibits is prohibitions,
seems to require that the same "Actions" be entered into the schema twice?

Of course, in reality, I have been unable to find an RDF validator that actually enforces the
range of the permits, or prohibits, so I never find any syntax errors during "validation".

confusedly yours,

Rick Silterra


******************************
Enrico Silterra
Meta Data Engineer
107-E Olin Library
Cornell University
Ithaca NY 14853

Voice: 607-255-6851
Fax: 607-255-6110
E-mail: es287 AT cornell.edu
http://www.library.cornell.edu/cts/
******************************



  • [Cc-uk] (no subject), Enrico Silterra, 04/26/2004

Archive powered by MHonArc 2.6.24.

Top of Page