On 29 March 2012 17:44, Tom Morris <[email protected]> wrote:
> On Wed, Mar 28, 2012 at 3:45 AM, Karen Coyle <[email protected]> wrote:
>> On 3/27/12 10:06 PM, Ben Companjen wrote:
>>
>> This is the beginning of the discussion about RWO's vs. bibliographic
>> entities:
>>
>> http://www.mail-archive.com/[email protected]/msg00076.html
>>
>> It's an ontological question - what is the entity that is being modeled?
>
> I think you need to model both the author and the bibliographic entry
> for the author, but the vast majority of the data will be associated
> with the author. It's only stuff like the "last updated" field which
> will be associated with the record.
Am I simplifying too much when I say bibliographic entries are
containers for (partial) views of people (and works etc.)?
Open Library stores everything in JSON documents (the containers)
including modification dates etc. The current architecture seems to
sufficiently support the storing of bibliographic data, although I
think we need changes to the datamodel to support e.g. author or
entity type. And some definition of the semantics of the datamodel
cannot hurt, I think :)
The RDF view already gives information about the subject of an entry -
modeled as agent, work, or manifestation - and the entry itself
(creation date, last modification date, revision number).
I tried to improve the semantics of what is output as RDF by changing
the templates, but it seems not everyone (with the "authority" to make
changes) is convinced that (all) the changes are for the better :/
Meanwhile I see some easy to fix problems that have not been resolved
in the past two months. I have therefore created a new branch in my
GitHub fork ("entityaware") that contains the complete changeset, and
reverting the branch that I requested to be pulled from ("patch-1") to
a point that people hopefully can agree on. :)
Please have another look at
https://github.com/internetarchive/openlibrary/pull/136
The "entityaware" branch looks at the "entity_type" (currently
discussed on GitHub) value of an author to determine the type (person,
org, other) and uses the more appropriate properties
(nameForThePerson, nameForTheCorporateBody) for each type.
See
https://github.com/bencomp/openlibrary/blob/entityaware/openlibrary/plugins/openlibrary/templates/type/author/rdf.html
for code :)
Ben
>
> Tom
_______________________________________________
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]
