Karen, Erik is right that: <http://openlibrary.org/works/OL262758W/> frbr:Manifestation <http://openlibrary.org/books/OL10236414M/>, <http://openlibrary.org/books/OL10636839M/>, <http://openlibrary.org/books/OL10681592M/>, <http://openlibrary.org/books/OL10686044M/>, <http://openlibrary.org/books/OL13268284M/>, <http://openlibrary.org/books/OL1937352M/>, <http://openlibrary.org/books/OL20352933M/>, <http://openlibrary.org/books/OL21968605M/>, <http://openlibrary.org/books/OL22836306M/>, <http://openlibrary.org/books/OL24374464M/>, <http://openlibrary.org/books/OL24375966M/>, <http://openlibrary.org/books/OL3969888M/>, <http://openlibrary.org/books/OL5416735M/>, <http://openlibrary.org/books/OL5526619M/>, <http://openlibrary.org/books/OL6363476M/>, <http://openlibrary.org/books/OL7261137M/>, <http://openlibrary.org/books/OL7262049M/>, <http://openlibrary.org/books/OL7262683M/>, <http://openlibrary.org/books/OL7603172M/>, <http://openlibrary.org/books/OL7851787M/> ; a frbr:Work .
isn't going to work (frbr:Manifestation being a class, not a property). While you're right that there is no (current) obvious way to go jump over frbr:Entities in the WEMI chain, there are some options here. For the version of the OL data that we host in the Platform, we're using dcterms:hasVersion/isVersionOf. http://api.talis.com/stores/openlibrary/meta?about=http://openlibrary.org/works/OL262758W&output=xml which isn't great, but the fact that both ends of the chain are frbr:Entities, we can infer the meaning. Even better would be add properties to http://open.vocab.org/: something like hasManifestation/manifestationOf. Perhaps even better would be to leverage http://vocab.org/frbr/core.html#Endeavour - associatedEntity as a property name perhaps? - that makes the modeling less complicated. That way we know that these are in the same WEMI chain, but we don't necessarily have to explicitly define /what/ it is in the relationship. -Ross. On Wed, Nov 10, 2010 at 9:28 AM, Karen Coyle <[email protected]> wrote: > Quoting Erik Hetzner <[email protected]>: > > >> What I meant to be getting at is that the rdf:type of the resources >> M1, M2, ... is (currently) workManifested, while the predicate linking >> W and M1, M2, ... is frbr:Manifestation. I think this is backwards; >> they rdf:type should be frbr:Manifestation, while the predicate should >> be workManifested. > > Thanks, Erik. From this conversation I have come to the realization > that there is no way to say: "this Work is Manifested as..." using > FRBR concepts. Instead, what I need to do is to create short "records" > for each manifestation that in effect each say: "manifests WorkX". I > don't think I can encapsulate the whole in a single rdf/xml unit > without creating some uber-structure that holds them together (which > would perhaps be a representation of FRBR Group 1 as a super-class, > something the the FRBR committee has rejected). I'll mock up something > and post it before I code it into the OL template. > > kc > >> >> As to which direction workManifested points, or its domain or range, I >> have no clue, but I assume you are correct here. >> >> best, Erik >> _______________________________________________ >> Ol-tech mailing list >> [email protected] >> http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech >> To unsubscribe from this mailing list, send email to >> [email protected] >> > > > > -- > Karen Coyle > [email protected] http://kcoyle.net > ph: 1-510-540-7596 > m: 1-510-435-8234 > skype: kcoylenet > > _______________________________________________ > Ol-tech mailing list > [email protected] > http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech > To unsubscribe from this mailing list, send email to > [email protected] > _______________________________________________ Ol-tech mailing list [email protected] http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech To unsubscribe from this mailing list, send email to [email protected]
