<tbaker> Expected: Tom, Emma, Karen, Jodi (joining late), Antoine (if he can join from the airport)

<emma_> Scribe: Emma

<emma_> scribenick: emma

<emma_> Karen: just sent a mail with an update

<emma_> ... jodi exported the docs

<emma_> ... karen does final editing

<emma_> ...and Peter will put it online

<emma_> ... links at the last moment

<emma_> ... remaining issues : what to do with Semantic Alignment annex

<emma_> ... very different from other appendices

<emma_> ... rather a section within appendix B

<emma_> into Appendix B, which now reads: 5.3.2 Discrete and bulk access to information 5.3.3 Front ends for mapping existing data stores to Linked Data and RDF 5.3.4 Semantic alignment

<kcoyle> had been app A - Sem alignment - app B

<emma_> Karen; actually this section doesn't really fit anywhere

<tbaker> Emma: originally, this was part of Appendix A on available data

<emma_> ... there aren't any sections describingthe technology at that level

<emma_> ... and I'm happy with result, question is whether other people will be

<tbaker> Karen: Think it is better in App B - do authors agree? App A is linked data "resources" - alignments are not a "resource"

<emma_> ... app A is a description of resources, Sem Alignment rather technology

<emma_> ... or we could have Semantic Alignment as appendix B, and Relevant Tech app C

<emma_> ... or remove it altogether.

<emma_> Emma: but it's a bit long for app B.

<emma_> ... editing again ?

<emma_> Karen: the content is fine

<emma_> ... there are a lot of other discussions of this kind that we didnt put in

<emma_> ... if people want to put it in, we have to put it somewhere

<emma_> TomB: splitting it into a separate appendix means less problems for appendices A or B

<emma_> ... is it harmful to have it in ?

<emma_> karen: editorially, I wouldn't want it to be in a separate appendix.

<emma_> TomB: cutting an entire section now is a problem. It's an important topic.

<emma_> ... it's important to have it somewhere in the report.

<emma_> ... it should be in recommendations

<emma_> Karen: we didn't use the term alignment there

<emma_> TomB: maybe we should

<emma_> Emma: could be a separate appendix with subtitles

<tbaker> Karen: Other two Appendixes referring to external report - this doesn't.

<emma_> ... it's about state of the art and issues

<tbaker> ...either belongs in the body or not sure what to do with it...

<emma_> ... put it in use cases

<dvilasuero> I wouldnt mind to add some text to the report

<emma_> TomB: in favor of making it a separate appendix or just remove it.

<emma_> ... if we put it last after appendix B

<emma_> Karen: could be a part of App A

<emma_> Emma: that's the way it was before

<emma_> ... and we changed it because it didnt fit

<tbaker> It's not http://www.w3.org/2005/Incubator/lld/wiki/Draft_Vocabularies_Datasets_Section2 ?

<emma_> Emma: agree with Tomb

<emma_> Karen: I'll make it appendix C

<tbaker> Tom: Peter will put the HTML documents online?

<emma_> Karen: Peter will make HTML links and then everybody can look at it

<tbaker> ...Peter, do you have write access?

<emma_> TomB: do we want to store them at their final destination ? they would be readable

<emma_> Karen: that's anavoidable, we need to test the links

<emma_> TomB: the final destination is a timestamp directory so we have to set a release date

<emma_> Karen: we need to talk to Peter about this

<tbaker> Peter, we need to decide when we think the report will be published and create a directory with a time-stamped name.

<tbaker> Jodi: Main question: how can I help with Karen's editing?

<tbaker> Karen: Main thing: take all links to wiki documents and turn them into absolute links.

<tbaker> ...hopefully a global change (Jodi agrees).

<tbaker> Jodi can handle the global change.

<emma_> TomB: let's meet again next week for an update on where things stand

<emma_> ... 2 more telecons then publish next monday

<dvilasuero> bye!

<dvilasuero> thanks

<emma_> *didn't work well though :-(

<emma_> scribenick: emma_

This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/dsecribing /describing/
Succeeded: s/I wouldn't it/I wouldn't want it/
Found Scribe: Emma
Found ScribeNick: emma
WARNING: No scribe lines found matching ScribeNick pattern: <emma> ...
Found ScribeNick: emma_

WARNING: 1 scribe lines found (out of 110 total lines.)
Are you sure you specified a correct ScribeNick?

ScribeNicks: emma, emma_

WARNING: No "Topic:" lines found.

Default Present: Emma, kcoyle, dvilasuero, Jodi
Present: Emma kcoyle dvilasuero Jodi
Agenda: http://www.w3.org/2005/Incubator/lld/wiki/FinalEditing
Got date from IRC log name: 29 Sep 2011
Guessing minutes URL: http://www.w3.org/2011/09/29-lld-minutes.html
People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report