Freebase: Discussion about bjimba

Pia Fajelagutan: Real Name

2009-12-25T18:14:11.0013Z

The surname might be wrong, By the way. is it spelled like that?

Pia Fajelagutan: Real Name

2009-12-25T18:13:41.0006Z

Is that Pia Fajelagutan's real name? Simply that? No other aliases either? I was finding it hard to get more info on her. Please verify.

Musical Release: Barcode & Catalog Number

2009-12-25T08:31:41.0013Z

Thanks Tom for this explanation.

Phil.B

Musical Release: Barcode & Catalog Number

2009-12-24T23:24:13.0000Z

CVT = "compound value type"

If you're familiar with modeling in UML, it correlates to a UML Association Class. If you're not familiar with UML, it's basically a link + associated data. Rather than saying

CD --> ownedBy --> Phil

it says

CD --> ownedBy (fromDate, toDate) --> Phil.

In actual fact, at the most primitive level, it's just a set of nodes and arcs in the graph, but it's useful to think of this particular "clump" of nodes as a single object or link with attributes.

Musical Release: Barcode & Catalog Number

2009-12-24T23:22:13.0006Z

CVT = "compound value type"

If you're familiar with modeling in UML, it correlates to a UML Association Class. If you're not familiar with UML, it's basically a link + associated data. Rather than saying

CD --> ownedBy --> Phil

it says

CD --> ownedBy (fromDate, toDate) --> Phil.

In actual fact, at the most primitive level, it's just a set of nodes and arcs in the graph, but it's useful to think of this particular "clump" of nodes as a single object or link with attributes.

Musical Release: Barcode & Catalog Number

2009-12-24T20:46:16.0005Z

Yes Chris, I agree with you.

Nevertheless, I don't understand what a CVT means. Could you explain, please?

Your idea of ratings and review is very good but I don't know how to implement such 'personal' fields ...

Regards

Phil.B

Musical Release: Barcode & Catalog Number

2009-12-24T19:16:17.0013Z

I’m not going to say whether Freebase should be used for this. I think Freebase should be used for whatever the community successfully uses it. If I were to include personal ownership, I would have a release ownership type, a CVT that correlates a person with a release and things like purchase date. Otherwise, what does it mean to see that To Venus and Back was purchased on 1999-10-20, 2002-05-30, and 2005-07-16? To see that Jane purchased it on 1999-10-20, Bill purchased it on 2002-05-30, and Joe purchased it on 2005-07-16 is arguably a little more useful. Even more useful, users could associate ratings or reviews with their ownership, as well; it would be a way to provide some access control via whatever app is creating those ownership nodes.

Musical Release: Barcode & Catalog Number

2009-12-24T17:47:58.0006Z

Dear Chris,

I admit that my type 'Musical Release (Details)' is redundant. Actually this type is a kind of test and will probably be erased in a near future.

You've noticed that I've included a 'Puchases Date' field because I would like to enter individual ownership information but I realize that FreeBase may not be intended for this purpose. What would be the best way to handle this 'Purchase Date' information?

Regards

Phil.B

Musical Release: Barcode & Catalog Number

2009-12-24T17:05:06.0000Z

I hadn’t noticed the Barcode type. That would be good. However, rather than linking your own Musical Release (details) to Barcode and then co-typing Musical Releases , I think it would be better to co-type Musical Releases as Barcoded Items. In general, your Musical Release (details) seems largely redundant. Original Release Date is present already. What does “Year of this Edition” gain? And “Purchase Date” confuses me; are you proposing to enter individual ownership information? The MusicBrainz ID is already present, as well, via a key, and AMG and Discogs links are best handled as keys into a namespace.

Musical Release: Barcode & Catalog Number

2009-12-24T16:54:31.0013Z

Hi Crism,

and thank you very much for pointing me to the location of the catalog number. Now I understand the goal of the 'Local Release' topic.

I notice that Barcode already exist in FreeBase : http://www.freebase.com/type/schema/base/barcode/barcode This type allow to link an item (i.e. a Musical Release) to a Barcode.

Once again, many thanks for helping me on this topic.

Regards

Phil.B

Musical Release: Barcode & Catalog Number

2009-12-24T14:53:19.0005Z

First, I misspoke above; we do have the catalog number, just not the barcode. Moreover, we have the date and place of Release Events. That really should be enough. See To Venus and Back for an example. I don’t believe we imported this information from MusicBrainz initially.

Musical Release: Barcode & Catalog Number

2009-12-24T14:19:05.0013Z

Yes you're right, the release date could be one way to distinguish 2 releases, but the how to differentiate a UK release and a French release which should be different but released a the same date ?

I think that, as it is implemented at MusicBrainz, the only way to differentiate 2 releases is to specify BarCode, Catalog Number and even Release Date.

Regards

Phil.B

Christopher Jones: Delete - Wikipedia disambiguation page

2009-12-22T22:15:16.0013Z

Movie data has been moved to the actor. The remainder can be deleted.

Music: Thematic catalogs

2009-12-21T22:38:15.0012Z

The changes under consideration are discussed on our wiki, here. I'm not sure how much of what you're considering would affect or be affected by them (although certainly just creating a schema for thematic catalogs shouldn't affect anything).

Music: Thematic catalogs

2009-12-21T22:14:34.0023Z

A further thought: if big changes to the music structures are planned for the next few months should I hold off doing this?

Music: Thematic catalogs

2009-12-21T22:13:27.0002Z

I think anyone who creates a thematic catalog is almost certainly, in fact, a musicologist but most musicologists do not create catalogs, so I'll change 'musicologist' in the schema to 'thematic catalog creator'.

'Thematic Catalog creator' could then be usefully picked up by anyone who wants to build a base of musicologists.

Music: Thematic catalogs

2009-12-21T20:09:58.0006Z

I second Phil's comment about musicologist. Most musicologists haven't created a thematic catalog, so it would seem a bit odd to have a type for musicologists with only one property which didn't related to the majority of them. (There are lots of commons types with properties that only apply to some of the instances, but those properties aren't typically the only property of the type.) In general, though, I think this would be a useful schema to have in the commons.

Music: Thematic catalogs

2009-12-20T22:40:29.0000Z

One more thought: is someone who creates a thematic catalog automatically a musicologist? (I have no opinion on this due to a complete lack of knowing what I'm talking about). If not, references to "musicologist" should probably become "thematic catalog creator".

Music: Thematic catalogs

2009-12-19T10:14:13.0018Z

If you haven't already, it's definitely worth reading the Commons page on the wiki. Generally, this looks good to me, but a few mostly nitpick comments:

Documentation: none of the properties of thematic catalog are documented. Musicologist isn't documented at all.
Documentation part 2: the type description for thematic catalog doesn't really tell me anything that the name of the type doesn't. What is this type for? What sort of things should be typed as this type?
Musicologist should probably include /people/person.
Are we sure there are no thematic catalogs which refer to more than one composer?
Consider if any of the properties should be disambiguators.
I don't really see the value in having the underscore in the musicologist_s key.

Hope this helps!

Music: Thematic catalogs

2009-12-19T05:57:26.0037Z

I've built a base of thematic catalogs (for classical composers) http://www.freebase.com/type/schema/user/simonhill/default_domain/thematic_catalog

Does this belong in music commons and/or should there a reciprical link to it for composers?

I'd like to get reference to the database showing up under each composers - without having to have separate (duplicative) composer topics in my db.

I'd be grateful for any help or ideas.

Simon

Composition: adopus number and catalog numbers

2009-12-19T05:38:49.0028Z

How about adding opus number and catalog number(s).

I am building a base of thematic catalog numbers http://www.freebase.com/type/schema/user/simonhill/default_domain/thematic_catalog which can be used to validate against!

I could then write a Songbird add-on to pick up and show work names, dates etc. for the music I am playing!

Country: Incorrect ID

2009-12-14T15:11:19.0013Z

Thanks for the clear explanation!

I understand that each URI is really just a GUID of sorts, and the data works fine when requested by that name. It just looked erroneous to be using that one as the primary ID when I queried for http://rdf.freebase.com/rdf/music.genre . It was an odd one out. I was a bit concerned that something with a UserID in the path may be sandbox data rather than canonic. Is there a way to promote http://www.freebase.com/view/en/country_music to being the 'preferred' or primary ID? ... Or not ... I see that is actually meaning a specific album name :-( . Dang.

FYI, the issue is: I'm testing a facility to import and reference shared vocabularies, and was planning to use the supplied URI/GUIDs as a primary key in an internal RDF triplestore. (Maybe I shouldn't do that, and just internalize the sameAs relations)

The given URI will still work (thanks for clearing that up) but just looked out of place in the diagnostic logs I was seeing. Partially (my fault) because my code is using the key found at the end of an URL as a temporary name for placeholder topics that haven't been individually fully retrieved yet. This is an ugly short-cut, but was returning sane results most of the time. My data queue listed : [ ... pop_music, trance_music, 00b3-10cd, breakbeat, black_metal ... ] ... I'll eventually be able to resolve that as I get the preferred name I guess. Just something to know! Thanks again. I think I'll be able to work with this..

Country: Incorrect ID

2009-12-14T14:08:44.0013Z

This is entirely expected. Each entity in Freebase can be referred to either by its GUID, or by an arbitrary number (possibly zero) of other IDs; there's then an algorithm which chooses the "primary" ID for each topic. Put simply, this algorithm chooses the shortest ID from the ones available, or uses the GUID if none exist.

In this case, the topic had not been assigned another ID (note that both /en/country and /en/country_music are used elsewhere), so when it was given an ID in Arthur's personal namespace, it started using that as its primary ID. However, nothing has changed here: you can still refer to this topic by its GUID or even by a number of Wikipedia keys, or even by its Wikipedia numeric article ID if you want. (The /wikipedia keys are never allowed to become the primary ID for a topic, which is why you weren't seeing those before). In the same way, you'll see raw GUIDs for any topics which don't have any other ID set.

Is this change of primary ID causing you a problem?

Country: Incorrect ID

2009-12-14T13:07:16.0014Z

Something has happened to this topic (Country Music). When the ID /user/avh/ellerdale.00b3-10cd was added to it, it seems to have taken over the identity of this resource. Now listings that include the concept of 'Country Music" Now instead include the concept of this odd User-defined Id

eg http://rdf.freebase.com/rdf/music.genre http://rdf.freebase.com/ns/type.type.instance [ http://rdf.freebase.com/ns/en.pop_music. http://rdf.freebase.com/ns/en.trance_music. http://rdf.freebase.com/ns/user.avh.ellerdale.00b3-10cd. http://rdf.freebase.com/ns/en.breakbeat. http://rdf.freebase.com/ns/en.black_metal ]

I can see when the erroneous ID was added http://www.freebase.com/history/view/user/avh/ellerdale/00b3-10cd But I can't see how to undo it.

I'm spotting a few other oddities (raw GUDs) in instances under music.genre as well.