 |
 |
Jenn, I had to go back and browse through the DCAP guidelines to see where this might fit in... the examples in the guidelines were mainly focused on re-use of properties that have already been declared elsewhere (and attempt to stay very very simple even in that). In that case, incorporation of the property in an AP would by its nature include the class relationship, or at least I viewed it that way. If you look at the DSP document, which goes into a great deal more detail (which we were trying to avoid in the guidelines), at 6.6.2 it includes a class membership constraint. This, however, is only present for non-literal values, and I have no explanation for that. Perhaps Appendix C of the guidelines should make some mention of classes, with a reference to W3C documentation for that level of detail? kc Quoting "Riley, Jenn" <[log in to unmask]>: > Thanks, Andy, that info is extremely useful. > > Perhaps SWAP could link to those RDF declarations from their AP > documentation? And the DCAP Guidelines could be a little clearer in > this area in their next revision? > > Jenn > >> -----Original Message----- >> From: DCMI Architecture Forum [mailto:[log in to unmask]] >> On Behalf Of Andy Powell >> Sent: Wednesday, April 07, 2010 10:08 AM >> To: [log in to unmask] >> Subject: Re: DC Application Profile - require formal properties but not >> classes? >> >> Irrespective of what the current DCAP guidelines say, my understanding >> is that DCAPs are expected to declare RDF classes for each of the >> "things" in the domain model. >> >> Re: SWAP classes... see: >> >> http://www.ukoln.ac.uk/repositories/digirep/index/Eprints_EntityType_Vo >> cabulary_Encoding_Scheme >> >> I'm not sure that we ever made available RDF declarations of these >> classes or not? It would certainly seem good practice to do so. >> >> Andy > -- Karen Coyle [log in to unmask] http://kcoyle.net ph: 1-510-540-7596 m: 1-510-435-8234 begin_of_the_skype_highlighting 1-510-435-8234 end_of_the_skype_highlighting Jenn,skype: kcoylenet