 |
 |
Excellent! Thanks for working with the situation :-) //Ed On Thu, Dec 1, 2011 at 9:55 AM, Jason Ronallo <[log in to unmask]> wrote: > Ed, > I'd like to still fit the article into the next issue. I agree that > the cultural heritage community needs more exposure to these new web > standards. With the increased interest in linked data, the landscape > of choices for how to expose your data has become more complex, and I > hope the article can get the discussion going and provide some > guidance there. > > I also see this as an opportunity for me to get something out there > relatively early on this topic, and coming before my talk is good > timing. > > Jason > > On Thu, Dec 1, 2011 at 9:06 AM, Ed Summers <[log in to unmask]> wrote: >> Hi Jason, >> >> Let me just say again how bad I feel for dropping this on the floor. I >> feel even more guilty because more discussion about the use of >> html5/microdata in the cultural heritage community is desperately >> needed. >> >> So is it OK to still try to fit your article into the next issue, or >> should we push it to issue 17? >> >> //Ed >> >> On Thu, Dec 1, 2011 at 9:00 AM, Jason Ronallo <[log in to unmask]> wrote: >>> Hi, Ed, >>> I'm glad to hear from you and the journal. What I had when I submitted >>> a proposal to the journal was just a proposal and an implementation, >>> so I won't be able to have a draft to you before the end of the month. >>> I'll try to share something with you sooner than that, though. >>> >>> I'll be happy to license the article US CC-BY and the code as open >>> source (hopefully MIT). >>> >>> Thank you, >>> >>> Jason >>> >>> >>> >>> On Thu, Dec 1, 2011 at 3:59 AM, Ed Summers <[log in to unmask]> wrote: >>>> Hi Jason, >>>> >>>> I'm pleased to tell you that your recent proposal for an article about >>>> HTML5 Microdata has been provisionally accepted to the Code4Lib Journal. >>>> The editorial committee is interested in your proposal, and would like >>>> to see a draft. I have to apologize however, since through an >>>> oversight of my own this email should have been sent almost a month >>>> ago, and was not (more on this below). >>>> >>>> As a member of the Code4Lib Journal editorial committee, I will be >>>> your contact for this article, and will work with you to get it ready >>>> for publication. >>>> >>>> We hope to publish your article in issue 16 of the Journal, which is >>>> scheduled to appear Jan 30, 2012. Incidentally, this is good timing >>>> for your code4lib talk on the same topic! >>>> The official deadline for submission >>>> of a complete draft is Friday, December 2. But since I dropped the >>>> ball on getting this email out to you promptly I completely understand >>>> if you can't hit that date. Looking at the deadlines [1] for issue 16 >>>> I can see that the 2nd draft is due Dec 30th, which is perhaps a more >>>> realistic goal for a draft. Please send whatever you have as soon as >>>> you can and we can get started. Upon receipt of the draft, I will >>>> work with you to address any changes recommended by the Editorial >>>> Committee. More information about our author guidelines may be found >>>> at http://journal.code4lib.org/article-guidelines. >>>> >>>> Please note that final drafts must be approved by a vote of the >>>> Editorial Committee before being published. >>>> >>>> We also require all authors to agree to US CC-BY licensing for the >>>> articles we publish in the journal. We recommend that any included >>>> code also have some type of code-specific open source license (such as >>>> the GPL). >>>> >>>> We look forward to seeing a complete draft and hope to include it in >>>> the Journal. Thank you for submitting to us, and feel free to contact >>>> me directly with any questions. >>>> >>>> If you could drop me a line acknowledging receipt of this email, that >>>> would be great. >>>> >>>> //Ed >>>> >>>> [1] http://wiki.code4lib.org/index.php/Code4Lib_Journal_Deadlines