guus: owl:sameAs is semantically not stricter than skos:exactMatch, strange domain/range constraints of skos are problematic

Jun: context is necessary to determine source of owl:sameAs inference

stefan: waht to record on the whiteboard?

ivan: maybe now/later: identity-vocabulary

jeremy: maybe never

Afternoon Wrap-up

david: we should have some results tomorrow...

sandro: we should have micro-charters
... as results that say what kind of group should do what to work out some features

mikeUshold: we should prioritize (not enough people to do breakouts on all) issues

ivan: we should only work on Core tomorrow, not on Infrastructure

(disagreement)

david: let's better go through one by one
... named graphs might be the easiest one to start with.

most people think named graphs is "maybe now", few "maybe later"

scribe: standardise Turtle?

most people for it

scribe: follow your nose (formalise HTTP Get)?

more maybe nows than maybe later... not as clear as the previous

scribe: json RDF serialisation?

14-15 maybe now, frewer maybe later

scribe: ATOM

more maybe later than maybe now

scribe: canonical RDF/XML fixing RDF/XML

majority maybe never

scribe: literals as subject?

majority maybe never

bnodes?

majority maybe now (15 now, 8 later, 5 never)

scribe: consolidate RDF RDFS namespaces?

majority never

ivan: alternative would be RDFa profiles.

axel: could be mentioned as a feature of a Turtle standardisation charter

RDF URIs vs IRI (vs Qnames???)

majority never

scribe: n-ary predicates?

maybe later

RDF URIs vs IRI (vs Qnames???)

change from before maybe now, but needs no discussion

scribe: binary?

never

revise RDF semantics?

now

lists?

maybe later

RDFa profiles?

now

Rule based querying?

later

ivan, guus: infrastructure topics could go into another WG such as SWEO, Best practices, etc.

next feature ...

identity for non-RDF resources?

<sandro> For infrastructure issues, the questions is: Does anyone want to fight for one of these to be in a Core group's charter

(the following features are in question whether we need to discuss that tomorrow)

identity, not tomorrow

provenance vocabularies, not tomorrow

annotations for RDF graphs, tomorrow

standard APIs, not tomorrow

Unified query layer, not tomorrow

context was merged into annotations

change vocabularies, not tomorrow

isolation APIs, not tomorrow

identity vocabularies, not tomorrow

petermika, guus: think it's important for linked data

david, ivan: important issue, but not necessarily in the resulting working group

jjc: argument against, we shouldn't guess what the LOD community will do/use

richard: owl:sameAs was used because it was the closest available... if we want to fix that, we need to offer something.

ian: LOD community uses owl:sameAs as a vocabulary.

Lin: does the use of RDF depend on vocabularies? for defining vocabuaries we need to make sure whether that is essential.

identity vocabularies: discussed tomorrow

change vocabulary: later

weakly deprecation?

maybe now

<pfps> Main Entry: deprecate

<pfps> Part of Speech: verb

<pfps> Definition: belittle, condemn

<pfps> Synonyms: cut down to size, depreciate, derogate, detract, disapprove of, discommend, discountenance, disesteem, disfavor, disparage, expostulate, frown, mudsling, not go for, object, pooh-pooh, poor mouth, protest against, put down*, rip*, run down, take dim view of, take down, take exception to

s/weakly deprecation+bestpractices/

<pfps> I like belittle or derogate or disesteem

<pfps> but there are lots of other good candidates

agenda tomorrow

stefan: suggest to group in 1) syntax 2) semantics 3) other

Syntax:

json, turtle ... breakout group lead by dajobe

(named graphs go under other, though they have both syntax and semantics bits)

RDFa profiles fo under syntax as well

Semantics:

RDF Semantics doc, RDFS/pfps, Bnodes, follow-your-nose

NamedGraphs:

Named graphs vs n-quads, annotations

(further minutes/notes on tomorrow's agenda will be collected and pasted to the minutes by david Wood ...)

<Anchakor> /me thanks all scribes

<dwood> Groups:

<dwood> 1. Syntax (Dave Beckett, TBD)

<dwood> - Turtle

<dwood> - JSON

<dwood> - RDFa profiles

<dwood> 2. Semantics (Paul Gearon)

<dwood> - Bnodes

<dwood> - Revising RDF Semantics

<dwood> - Weak deprecation

<dwood> 3. Graph Metadata (Elisa Kendall)

<dwood> - Named Graphs

<dwood> - Annotations

<dwood> 4. Linked Data (David Booth)

<dwood> - Identity vocabulary

<dwood> - FYN

<dwood> rssagent, draft minutes

This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

FAILED: s/weakly deprecation+bestpractices//
No ScribeNick specified.  Guessing ScribeNick: AxelPolleres
Inferring Scribes: AxelPolleres

WARNING: No "Present: ... " found!
Possibly Present: Anchakor Definition FabGandon Groups Jun Lin NamedGraphs Semantics Synonyms Syntax axel david dbooth dwood guus ian ivan james jeremy jjc mikeUshold pfps richard sandro stefan tomlurge
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

Guessing minutes URL: http://www.w3.org/2010/06/27-rdfn-minutes.html
People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)