- From: Steve Harris <steve.harris@garlik.com>
- Date: Thu, 6 Oct 2011 11:09:46 +0100
- To: Andy Seaborne <andy.seaborne@epimorphics.com>
- Cc: public-rdf-wg@w3.org
On 2011-10-06, at 10:47, Andy Seaborne wrote: > > On 06/10/11 10:29, Steve Harris wrote: >> On 2011-10-06, at 08:35, Andy Seaborne wrote: >>> >>> On 05/10/11 23:16, Ian Davis wrote: >>>> I think 4.2 web crawling (or aggregation in general) is very >>>> important >>>> >>>> Also I don't see it on the existing list but being able to edit >>>> datasets at the granularity of the graph rather than the triple >>>> is very important. i.e. It is very convenient to be able to >>>> replace all the triples in one named graph with a new set when >>>> doing things like web crawling. >>> >>> Agreed. >>> >>> Some words added (section 1.7, to keep the numbering stable); Ian, >>> do feel free to refine them. >>> >>> This relates to 1.5 "Exchanging the contents of RDF stores". >> >> Agreed, on all counts. >> >> However I'd like it to be expanded in scope slightly to also cover >> information derived from non-RDF pages which are being crawled (pure >> self-interest, as this is where we get most of our data). It's >> slightly different from a modelling point of view, as foo.html >> doesn't typically contain any actual triples, just information which >> cause triples to be asserted. > > It's a wiki ... :-) Indeed, but it felt a little underhand to change the focus of a use-case after people had voted for it! If neither you or Ian feel it's an issue, I'll add a note to it. - Steve >> That, in combination with “1.3 Graph Changes Over Time”, and “1.5 >> Exchanging the contents of RDF stores” captures our most challenging >> data representation challenges. >> >> - Steve >> >> >>>> On 5 Oct 2011, at 20:49, Andy >>>> Seaborne<andy.seaborne@epimorphics.com> wrote: >>>> >>>>> I think that: >>>>> >>>>> 1.3 Graph Changes Over Time >>>>> >>>>> is also important. >>>>> >>>>> Andy >>>>> >>>>> On 05/10/11 19:56, David Wood wrote: >>>>>> Hi all, >>>>>> >>>>>> We would like to prioritize the use cases for named graphs >>>>>> [1] before FTF2. >>>>>> >>>>>> At today's telecon, the following use cases were deemed >>>>>> important to attendees: - 1.1 Slicing datasets according to >>>>>> multiple dimensions - 1.5 Exchanging the contents of RDF >>>>>> stores - 1.6 Versioning in SDMX and DDI - 5.2 OWL's “Ontology >>>>>> Documents” - 6.2 Reasoning over annotations >>>>>> >>>>>> Further, it was proposed to drop the following use case: - >>>>>> 4.8 Provenance Information and Data Retention ...and add >>>>>> Sandro's provenance use case [2] in place of several existing >>>>>> provenance use cases (to be determined). >>>>>> >>>>>> Please note that the numbers are for reference only until the >>>>>> page is modified. The numbers *will* change, no later than >>>>>> Friday. The numbers in this message are from revision 1473 >>>>>> [3]. >>>>>> >>>>>> If you object to these changes or have others to suggest, >>>>>> please respond to this message and/or update the wiki. >>>>>> Thanks. I will update the wiki no later than this weekend >>>>>> prior to the ftf. >>>>>> >>>>>> Regards, Dave >>>>>> >>>>>> [1] http://www.w3.org/2011/rdf-wg/wiki/TF-Graphs-UC [2] >>>>>> http://lists.w3.org/Archives/Public/public-rdf-prov/2011Sep/0003.html >>>>>> >>>>>> > [3] http://www.w3.org/2011/rdf-wg/wiki/index.php?title=TF-Graphs-UC&oldid73 >>>>>> >>>>>> >>>>> >>> >> > -- Steve Harris, CTO, Garlik Limited 1-3 Halford Road, Richmond, TW10 6AW, UK +44 20 8439 8203 http://www.garlik.com/ Registered in England and Wales 535 7233 VAT # 849 0517 11 Registered office: Thames House, Portsmouth Road, Esher, Surrey, KT10 9AD
Received on Thursday, 6 October 2011 10:10:16 UTC