- From: Tadej Stajner <tadej.stajner@ijs.si>
- Date: Tue, 05 Mar 2013 16:06:50 +0100
- To: "Lieske, Christian" <christian.lieske@sap.com>
- CC: "public-multilingualweb-lt@w3.org" <public-multilingualweb-lt@w3.org>
- Message-ID: <51360A0A.9020201@ijs.si>
Hi, the revision is good. I made some minor changes: * Expanded use case to better reflect presentation & poster * Mentioned word sense disambiguation as another use case * Updated implementation status * Added URL to source code -- Tadej On 3/4/2013 6:32 AM, Lieske, Christian wrote: > > Hi Tadej, > > While editing the section on "Named Entity Recognition" the following > specific questions came up. Hopefully, it is alright to contact you > with them ... > > 1.Did I revise the "description" properly? > > 2.Did I revise the "data category use" properly? > > Thanks in advance for your help. > > Of course, you are welcome to modify my current draft to come up with > an enhanced version: > > http://www.w3.org/International/multilingualweb/lt/wiki/Use_cases_-_high_level_summary#Text_Analysis:_Named_Entity_Recognition_and_Enrichment > > Cheers, > > Christian > > *From:*Felix Sasaki [mailto:fsasaki@w3.org] > *Sent:* Saturday, February 16, 2013 2:34 AM > *To:* public-multilingualweb-lt@w3.org > <mailto:public-multilingualweb-lt@w3.org> > *Subject:* [All] high level use cases not yet ready to publish, please > have another look > > Hi all, esp. Christian, > > I had a brief look at > http://www.w3.org/International/multilingualweb/lt/wiki/Use_cases_-_high_level_summary > and I think this is not yet ready even for a first public working draft. > > I won't point to specific sections here, but please have another look > at "your" section with the following in mind: > > - Don't mention something that is not in the spec anymore, e.g. > "Disambiguation". Call this "Text Analysis Annotation". > - The "More Information and Implementation Status/Issues" sections are > extremely heterogenous. Please, re-write them following this simple > pattern taken from ENLASO: > > > [ > > Tool: Okapi Framework (ENLASO). > > * Detailed slides at http://tinyurl.com/8tmg49d > <http://tinyurl.com/8tmg49d> > * Running software: http://code.google.com/p/okapi/downloads/list > <http://code.google.com/p/okapi/downloads/list> > * Source code: http://code.google.com/p/okapi/source/browse/ > <http://code.google.com/p/okapi/source/browse/> > * General documentation: http://www.opentag.com/okapi/wiki/ > <http://www.opentag.com/okapi/wiki/> > > ] > > - Don't just "list" data categories. Describe their benefit in your > implementation. > - Use a simple & sweet language style like e.g. in > http://www.w3.org/International/multilingualweb/lt/wiki/Use_cases_-_high_level_summary#Simple_Machine_Translation > > > The document should be a *high level* overview. Currently it has 20 > pages - that's too long. We can provide details & more text in other > publications. > > NOTE for the EC project folks: this document is an important part for > us to raise awareness for Rome and to give input for the Luxembourg > review. Please invest the time to take above considerations into account. > > Please, do that by *Tuesday EOB 19 February.* > > Christian, what are your thoughts on editing this and making this > ready for publication, also in terms fo timing. > > Best, > > Felix >
Received on Tuesday, 5 March 2013 15:07:27 UTC