danm

alexander: Hey let me know what you think about my assertion modeling kit

2008-09-05T19:00:42.0017Z

http://www.freebase.com/view/user/avic/assertion_modeling_kit

Croatia: Get Spllit in Dalmatia

2008-09-05T18:52:48.0012Z

I totally am into dalmational artworks

Croatia: Get Spllit in Dalmatia

2008-09-05T18:51:34.0021Z

Baybeeee

Contributing Large Datasets: NNDB Links for People

2008-09-05T17:33:09.0000Z

I believe the normal limit is 10,000 writes. I'll see if I can get your limit increased.

Songwriter: Songs composed

2008-09-05T17:17:07.0012Z

Good morning, Cris, did you see my 3 wonderful philosophers on the front page today??

Sure, I can do that, but it is not nice to have empty spaces on the page. Look at Cage, please, what is the use of the "Songwriter" "Lyricist" boxes if we cannot put anything in them? It simply does not look good. Cage wrote songs...

Songwriter: Songs composed

2008-09-05T17:17:07.0012Z

Good morning, Cris, did you see my 3 wonderful philosophers on the front page today??

Songwriter: Songs composed

2008-09-05T16:11:46.0012Z

He has the Songwriter type, which as I said before is a shorthand for both Composer and Lyricist. Songwriter has no properties of its own.

He also has the Composer type with several “Works Composed” already entered. You can add to that list.

Songwriter: Songs composed

2008-09-05T16:11:46.0012Z

He has the Songwriter type, which as I said before is a shorthand for both Composer and Lyricist. Songwriter has no properties of its own.

He also has the Composer type with several “Works Composed” already entered. You can add to that list.

Songwriter: Songs composed

2008-09-05T05:41:45.0012Z

... then why does John Cage have the "Song composer" type without anything on it??

Songwriter: Songs composed

2008-09-05T05:41:45.0012Z

... then why does John Cage have the "Song composer" type without anything on it??

Songwriter: Songs composed

2008-09-05T04:32:42.0012Z

Please use the “Works Composed” property of the Composer type.

Songwriter: Songs composed

2008-09-05T04:32:42.0012Z

Please use the “Works Composed” property of the Composer type.

Songwriter: Songs composed

2008-09-05T03:52:57.0018Z

Cris, please give us "Songs composed," I need it for John Cage. Thank you

Songwriter: Songs composed

2008-09-05T03:52:57.0018Z

Cris, please give us "Songs composed," I need it for John Cage. Thank you

Contributing Large Datasets: NNDB Links for People

2008-09-05T03:28:16.0012Z

I've uploaded a new version of the data to the sandbox. If no one has any objections, I'll add it to the main site.

Is there a limit on how many writes I can do on the main site? Will I be able to make 19,000 writes in a day?

Architectural contractor: Contracting firm

2008-09-05T00:25:55.0012Z

similar issues exists with other properties of /architecture/structure: architectural firm, engineering firm, architect, engineer. you're right. it's not well normalized. i like your idea of a mediator/role. I think what I'd like to do is keep the properties that I currently have on /architecture/structure

architectural firm
contractor
engineering firm

and have the expected type for each one be a different mediator type with a whole bunch of information about the role:

project
client
firm
start date
end date

perhaps, in the case of the contractor role there could be someone way of "tagging" the role as one of sub or general contractor. other properties could be added as needed: list of staff members and their roles? there is some question about how much detail we really need, as with it comes schema complexity. anyhow, any other thoughts on this?

Architectural contractor: Contracting firm

2008-09-05T00:25:55.0012Z

architectural firm
contractor
engineering firm

and have the expected type for each one be a different mediator type with a whole bunch of information about the role:

project
client
firm
start date
end date

Military: casualites

2008-09-04T22:52:28.0012Z

I agree that this is probably the right choice for now, lacking a more comprehensive structure. Any thoughts on what the expected type of the property should be?

La rondine by Giacomo Puccini - Third version completed by Lorenzo Ferrero: Split

2008-09-04T21:12:21.0012Z

Thank you, Bryan, we are discussing this now with Jeff per email and will let you know about the outcome. Cheers

La rondine by Giacomo Puccini - Third version completed by Lorenzo Ferrero: Split

2008-09-04T20:35:53.0012Z

I agree with Jeff. I am sure it was a tremendous event, but in terms of freebase, I don't think the topics should be conflated. The production of the opera and the opera itself should be discrete topics.

La rondine by Giacomo Puccini - Third version completed by Lorenzo Ferrero: Split

2008-09-04T18:27:17.0012Z

...because it was a tremendous event! It was the premiere of the third version of the opera, after more than 70 years of waiting for it. Besides,describing it separately does not duplicate any of the productions presented above! Please let us continue this discussion per email, there is a lot more to say about this!

Publishing: Possible revision for Journal Articles

2008-09-04T18:09:52.0012Z

If Jounal Article were linked directly to Journal Issue, it would remove the need for co-typing it with Published Work. But otherwise, what you suggest would work. But if we do keep the existing Journal Issue model (as opposed to the CVT version under review), I'd be reluctant to undermine the existing Published Work/Publication model by creating a special type that used a different method of publication. (I realize that I'm already proposing this with the CVT model, and I do recognize the inconsistency; I guess my argument is that if the needs of modeling Journal Articles are significantly different from other types of publications the different model is justified, but if it's just a question of copying the current model onto different types, I'm not sure that it is justified.)

La rondine by Giacomo Puccini - Third version completed by Lorenzo Ferrero: Split

2008-09-04T17:59:17.0012Z

The opera itself is not the same thing as a production of the opera, and so they really shouldn't share the same topic. I note that you've already added several other productions of this opera as separate topics -- why do you want this one production to be treated differently?

La rondine by Giacomo Puccini - Third version completed by Lorenzo Ferrero: Split

2008-09-04T08:46:12.0012Z

Jeff, please don't split it !! One would never be able to find the pieces again. It is better to have everything at a glance. I beg you not to touch it, this is a big, complicated thing with many productions, which took 2 months to compile

cheunger: Storie di neve

2008-09-04T05:59:01.0012Z

Thank you. It is incredible that someone would want to delete them!

I am jolly glad that they are not on the delete list.

cheunger: Storie di neve

2008-09-04T05:33:55.0012Z

Chris already diagnosed and remedied the problem before I even had a chance to read this post - he's that good. I am checking on Munich and Paris - they have been flagged, but I don't see them in topics for voting. I'll keep you posted on their status.

Publishing: Possible revision for Journal Articles

2008-09-04T04:37:43.0012Z

You could make a Journal Article type that includes the published work type. then make the contents of the Journal Issue type link to Journal article. That way any new objects that get linked to from a Journal Issue will automatically be created as Journal Article types. So users won't have to manually add the Journal Article type. The problem is that all existing articles that are presently of the published work type would have to be migrated over to being of the journal article type.

cheunger: Storie di neve

2008-09-04T04:25:56.0012Z

Thank you all.

I would like to add that I never write randomly. Bryan helped me the other day with an enormous problem I had in a matter of seconds!! I thought he was a bug expert and that's why I wrote to him directly.

Bryan, let us hope we save Munich and PARIS as well...

Ship: Owner

2008-09-04T03:59:43.0018Z

How do we put in the Owner of a ship?

La rondine by Giacomo Puccini - Third version completed by Lorenzo Ferrero: Split

2008-09-03T22:23:57.0017Z

The opera itself should be split into a separate topic from the production of the opera.

Publishing: Possible revision for Journal Articles

2008-09-03T22:07:06.0012Z

At that point, Journal Article would be nothing more that what we sometimes call a "bucket" -- a type that has no properties, and is therefore just a place to collect things that can be said to be of that type. There are a number of these here and there, but we try to avoid them as much as possible. In order for it to be useful, users would have to remember to add it themselves to each topic that is published in a journal; we're already asking users to manually add a lot of types in the publishing domain, just to use the basic functionality, and I have doubts about how much this type would ever be used.

I can't think of a way, through the UI, to filter out only those works that were published in Journal Issues. How often do you think people would be looking for journal issues but not other types of academic or scholarly papers?

Publishing: Possible revision for Journal Articles

2008-09-03T21:10:00.0012Z

Okay, let me see if I understand. Currently, you can enter the journal article in the contents of a journal issue where it links in as a publication. And in published work type, there is the "published in" property which gets filled in with the journal issue. So there is no specific Journal Article type because there doesn't need to be one separate from publication. Sorry about the confusion.

So now I'm having trouble figuring out what to do if you want to search for only journal articles? I start by searching for published work, but when I try to filter it by the "published in property", it wants me to put in the name of a specific publication, it doesn't accept the type Journal Issue. I suppose that the sandbox version would solve this problem, but at the expense of not being able to record issue level information. It might still be more user friendly to have a journal article type under the current system even if the journal article type has no extra properties above and beyond published work. It would simply allow for distinguishing journal articles from other publications at a glance.

cheunger: Storie di neve

2008-09-03T19:50:47.0012Z

This was by design in the old age of primitive conservation. I have made /common/topic an included type of /music/composition, and am running a script to garden existing instances.

Publishing: Possible revision for Journal Articles

2008-09-03T19:17:23.0012Z

The issue isn't about having both an article type and an issue type -- we already have those (see the help topic Entering Scholarly Works and Citations for an explanation of the current model). The issue is how to best represent the publication information of an article -- whether by omitting the issue type entirlely, and just using a CVT to capture the basic bibliographic information, like you would see in a bibliography (or bibtex or similar format), or whether to have an explicit topic for every journal article.

There is not, alas, a way to display the information in chained links. You can display disambiguating properties from the expected type of a property only. So in the sandbox version, the volume, issue, etc. are properties on the Journal Publication type, and so can be displayed on the article and journal types the connect to it. But the way we otherwise handle publications is by using the "published work" and "publication" types, which have to be set as co-types on the article and issue. Because the expected type is not explicitly "journal issue", properties on "journal issue" are not displayed on the article or journal.

Let me know if this doesn't make sense.

cheunger: Storie di neve

2008-09-03T17:56:41.0012Z

Chris -- the type /music/composition does not have /common/topic as an included type. I have no idea how this happened, but I have seen one or two other types where topic was missing.

cheunger: Storie di neve

2008-09-03T16:05:11.0012Z

Storie di neve is working perfectly!

I have a similar problem at Opera composer - Opera composed, please...

Computer is not storing new information

cheunger: Storie di neve

2008-09-03T15:56:16.0012Z

Cris, now I got back the pictures but the short description is lost. Never mind, I will write it again and see what happens. Thank you very much indeed

cheunger: Storie di neve

2008-09-03T15:47:19.0012Z

Cris, I am almost sure it is a bug.

I created it normally, as a work in "Works composed." I put a YouTube video, filled up the spaces, uploaded the picture, added a short description and then I saw that nothing was being stored except the video. I had this problem before when I wanted to correct the description on the main page. The computer is not storing what I do...

cheunger: Storie di neve

2008-09-03T15:33:07.0012Z

Please post about problems on the actual affected topics, not randomly selected users. It is much easier to find the problem that way.

The problem with “Storie di neve” was that somehow it was a Composition but not a Topic. The article and pictures are properties of Topic, so they weren’t showing up.

How did you create “Storie di neve”? There may be a bug in our system; if you can tell us how you created it, we can correct the problem.

cheunger: Storie di neve

2008-09-03T08:02:12.0018Z

Good morning, Bryan

there is something very wrong on my L. Ferrero page at Composer-Works composed-Storie di neve. The computer would not let me save/store new photographs and the information I wrote at "Add description." Could you, please, have a look? Thank you, and let us hope we can save Munich from deletion!

Publishing: Possible revision for Journal Articles

2008-09-03T00:31:03.0012Z

I like the way the sandbox version looks, but I'm not sure I understand the concern about the schemata coming apart if you have both and issue type and an article type. You wouldn't store the issue information separately in the article type, you'd just link to the issue, and the issue in turn links to the Journal.

i.e.,

Object of Article type has a property "Published in" linking it to an object of Journal Issue type

Object of Journal Issue type has a property "Journal" linking it to a journal.

What I'm not sure about, because I'm new to freebase, is whether there is a good way to display the information if links are chained in this way. If you set up the types in the way I've suggested, can you look at a journal article and see both the issue and the journal that that issue links to?

Maybe there's something I'm not getting about your concern about schema getting out of sync. Please let me know as I'm anxious to learn more about how things work around here.

Publishing: Possible revision for Journal Articles

2008-09-03T00:07:30.0012Z

The proposed schema is on sanbox again, here this time:

https://sandbox.freebase.com/type/view/book/journal_publication

Publishing: Possible revision for Journal Articles

2008-09-02T21:57:56.0012Z

I see your point about the theme and target-article issues, and why it would be useful to be able to view the contents at the issue level in those cases. Although if you know the issue/volume/date information, you could use the filter view of the CVT to recreate a table of contents (there would be nothing anywhere that said, however, that "This is the X-themed issue of Y journal". I am more than a bit concerned about using both schemata simultaneously -- I worry both that the two schemata would fall out of synch very quickly, making it harder for users to use the bibliographic data, and also that someone might figure out a way to keep them in synch (via some automated process), which would eat up a lot of extra space.

I'd be curious to hear more of your thoughts on this.

I'll repost the schema to sandbox either later today or tomorrow (the data on sandbox is due to be refreshed in an hour or so).

Publishing: Possible revision for Journal Articles

2008-09-02T20:04:54.0012Z

I think it might be going too far to eliminate the issue type, although I agree that for most purposes the article is what matters. Some journal issues deal with a set theme or with responses to a target article. For example, The American Journal of Bioethics always sets one or more target articles that other contributors respond to. So it might be useful to keep journal issue as its own type to enable tacking this kind of issue-level information. I don't know the system well enough yet to know whether this information can be stored in a CVT or if it needs a standard type. It might make more sense to eliminate the issue type for newspapers, since generally there is no theme to the content of a single newspaper issue.

Military: casualites

2008-09-02T18:33:28.0000Z

We have no plans for another way to represent citation data. We always have to be careful about schema bloat, but in this case it seems useful and important to source casualty statistics.

I do think the source in this case should be "who estimated it" (the government or organization), rather than "who printed it" (the book or journal).

Military: casualites

2008-09-02T18:19:44.0012Z

My concern is that modeling it this way sets a precedent for putting sourcing data in a CVT for any property, since a great deal of the information we store is similarly dependent. Certainly, many numeric values are going to vary based on who's doing the measuring and how, and I can envision people wanting citation information on practically any kind of assertion. I think the data team has been working on ways of handling attributions, but I don't know if they've addressed this case.

Architecture firm: Projects not just structure type?

2008-09-02T10:53:33.0012Z

Agreed! Also, many times the design consultant is not the architect of record. An architecture firm might be working for the owner, or for the contractor, or even another architecture firm. The architectural consultant can provide many different services including things like interior design or specifications. Technically the master plan can include structures even if they are not yet built. However, there needs to be something more. I have been working on this myself. How do we edit this table? Paul Shanks

Architectural contractor: Contracting firm

2008-09-02T08:36:59.0018Z

I think the "architectural contractor" table should be a mediator - not a topic. A contractor is a role, not a company. This role requires a client, a project and a contracting firm. Also, a distinction is often made between the general contractor and sub contractors - neither fo which are architectural. Thoughts?

Architectural contractor: Contracting firm

2008-09-02T08:36:59.0018Z

Military: casualites

2008-09-01T18:07:49.0000Z

Why not just handle casualty souces in exactly the same way? Cite the text that the caualty number was drawn from.In many cases tht is what is needed to make it a useful number, since the context of the text is required to make sense of what the number means and how it was estimated.