2011/02/23-rdf-wg RESOLVED: use http://www.w3.org/2010/01/Turtle/ as the starting point for the Turtle work
2011/03/02-rdf-wg RESOLVED: accept last week's minutes
2011/03/09-rdf-wg RESOLVED: accept previous minutes http://www.w3.org/2011/rdf-wg/meeting/2011-03-02
2011/03/09-rdf-wg RESOLVED: Action 12 closed
2011/03/09-rdf-wg RESOLVED: Action 15 closed
2011/03/09-rdf-wg RESOLVED: Action 7 closed
2011/03/16-rdf-wg RESOLVED: accept last week's minutes
2011/03/23-rdf-wg RESOLVED: Minutes http://www.w3.org/2011/rdf-wg/meeting/2011-03-16 accepted
2011/04/06-rdf-wg RESOLVED: minutes accepted
2011/04/13-rdf-wg RESOLVED: (1) Incubate on something like JSON-LD, (2) make a REC on something like Talis RDF/JSON, and (3) make a Note on current practice stuff like Linked Data API.
2011/04/13-rdf-wg RESOLVED: Allow dots inside local part and namespace part of qnames in Turtle, aligning with SPARQL syntax
2011/04/13-rdf-wg RESOLVED: close ISSUE-18 by requiring digits after the decimal point, as in "18.0"
2011/04/13-rdf-wg RESOLVED: Mark xs:string as archaic for use in RDF, recommending use of plain literals instead. Recommend that systems silently convert xs:string data to plain literals.
2011/04/14-rdf-wg RESOLVED: Close ISSUE-26 doing nothing.
2011/04/14-rdf-wg RESOLVED: Close ISSUE-27, not marking rdf:value as archaic, but with the understand that the modeling advice in RDF Primer will be revisited.
2011/04/14-rdf-wg RESOLVED: Named Graphs in SPARQL associate IRIs and graphs *but* they do not necessarily "name" graphs in the strict model-theoretic sense. A SPARQL Dataset does not establish graphs as referents of IRIs (relevant to ISSUE-30)
2011/04/27-rdf-wg RESOLVED: Close issue-34 without adding any features (syntactic sugar) to Turtle over what is in the submission
2011/04/27-rdf-wg RESOLVED: to accept the minutes of TC 2011-04-20
2011/04/27-rdf-wg RESOLVED: to accept the minutes of the F2F (both days)
2011/04/27-rdf-wg RESOLVED: "to not add any features to Turtle over what is in the submission"
2011/05/04-rdf-wg RESOLVED: ACTION-42 herewith closed
2011/05/04-rdf-wg RESOLVED: closing ACTION-34
2011/05/04-rdf-wg RESOLVED: davidwood: closing ISSUE-42
2011/05/04-rdf-wg RESOLVED: davidwood: closing ISSUE-43
2011/05/04-rdf-wg RESOLVED: davidwood: enough DISagreement to leave this open
2011/05/04-rdf-wg RESOLVED: davidwood: ISSUE-45 closed
2011/05/04-rdf-wg RESOLVED: davidwood: ISSUE-47 closed
2011/05/04-rdf-wg RESOLVED: davidwood: ISSUE-48 closed
2011/05/04-rdf-wg RESOLVED: davidwood: ISSUE-50 postponed
2011/05/04-rdf-wg RESOLVED: davidwood: not enough agreement to postpone
2011/05/04-rdf-wg RESOLVED: http://lists.w3.org/Archives/Public/public-rdf-wg/2011May/0011.html Point 2-7 are agreed leaving \u processing
2011/05/04-rdf-wg RESOLVED: ISSUE-44 closed.
2011/05/04-rdf-wg RESOLVED: no objections. propsal accepted
2011/05/11-rdf-wg RESOLVED: Accept the minutes of the 04 May telecon http://www.w3.org/2011/rdf-wg/meeting/2011-05-04
2011/05/11-rdf-wg RESOLVED: Close ISSUE-51 noting that it's a duplicate of work the WG is already doing with multiple graphs
2011/05/11-rdf-wg RESOLVED: Close ISSUE-53 with no change, and with the explanation that RDF semantics establishes that RDF statements can be used to make claims about the world. Figuring out who exactly is making those assertions is beyond the scope of the core technology. Some of these concerns may be addressed by the 'named graph' activity; others by W3C's new Provenance WG - http://www.w3.org/2011/prov/wik
2011/05/11-rdf-wg RESOLVED: Close ISSUE-54 with no change, noting that this WG has no plans for substantially changing RDF/XML or the collection mechanism at this time.
2011/05/11-rdf-wg RESOLVED: to close ISSUE-52 - this is the responsibility of the enclosing document
2011/05/18-rdf-wg RESOLVED: Resolve ISSUE-40 by adding text to RDF Concepts, per the “Updated Proposal” from http://www.w3.org/2011/rdf-wg/wiki/Skolemization#Updated_Proposal with action-49 on Peter to propose edits
2011/05/18-rdf-wg RESOLVED: second F2F to be held at MIT in Oct 12
2011/05/25-rdf-wg RESOLVED: for short names we would use rdf11-X where rdf-X stands for the current recommendations
2011/05/25-rdf-wg RESOLVED: minutes from last meeting accepted
2011/05/25-rdf-wg RESOLVED: resolve ISSUE 8 by keeping IRI-s and their punycode equivalent separate as different URI References in RDF
2011/05/25-rdf-wg RESOLVED: The thing we're working on is "RDF 1.1"
2011/05/25-rdf-wg RESOLVED: We'll use genid as the .well-known name
2011/06/01-rdf-wg RESOLVED: Close ISSUE-56, we have no intention of addressing this.
2011/06/01-rdf-wg RESOLVED: minutes from last meeting accepted
2011/06/01-rdf-wg RESOLVED: Resolve ISSUE-64 by updating RDF concepts per Richard's proposal
2011/06/01-rdf-wg RESOLVED: To close ISSUE-55 as this is not considered the duty of this group
2011/06/01-rdf-wg RESOLVED: to close ISSUE-57 by stating that it's not in our charter and we have no intention of doing it.
2011/06/08-rdf-wg RESOLVED: accept minutes of last meeting
2011/06/08-rdf-wg RESOLVED: by consensus to close ISSUE-60 and redirect to ISSUE-37
2011/06/08-rdf-wg RESOLVED: close ISSUE-58, as being archaic.
2011/06/08-rdf-wg RESOLVED: close ISSUE-61 stating that the answer is "no"
2011/06/15-rdf-wg RESOLVED: Issue-59 was CLOSED because it was opened in error by the last RDF WG. See: http://www.w3.org/2011/rdf-wg/track/issues/59
2011/06/15-rdf-wg RESOLVED: Issue-62 was OPENED because we need to consider it properly. See: http://www.w3.org/2011/rdf-wg/track/issues/62
2011/06/15-rdf-wg RESOLVED: to accept the proposal at http://www.w3.org/2011/rdf-wg/wiki/StringLiterals/AbolishUntaggedPlain with the modification that preferred output form (SHOULD) is "foo" not "foo"^^xsd:string in RDF; recommends that SPARQL and other WGs does the same
2011/06/15-rdf-wg RESOLVED: to accept the summer telecon schedule.
2011/07/06-rdf-wg RESOLVED: accept minutes for June 22
2011/07/06-rdf-wg RESOLVED: minutes June 29 acceptted
2011/07/06-rdf-wg RESOLVED: Move http://dvcs.w3.org/hg/rdf/raw-file/tip/rdf-turtle/index.html to Working Draft.
2011/07/20-rdf-wg RESOLVED: accept last week's minutes http://www.w3.org/2011/rdf-wg/meeting/2011-07-06
2011/07/20-rdf-wg RESOLVED: accept turtle status text as proposed
2011/08/03-rdf-wg RESOLVED: move RDF-Concepts to 1st public working draft
2011/08/03-rdf-wg RESOLVED: the working group agrees that the RDF/XML document will have to undergo a minimal, editorial change to fit into the new set of recommendations (update of references, terms, etc)
2011/08/31-rdf-wg RESOLVED: Create a UTF version of ntriples in the Turtle REC, while making clear that the ASCII version of ntriples is still acceptable for use. ASCII ntriples would continue to live in the test cases document. File extensions and media types should be in conformance to the proposal at http://lists.w3.org/Archives/Public/public-rdf-wg/2011Aug/0170.html
2011/09/07-rdf-wg RESOLVED: to accept the minutes from 31 Aug telecon
2011/09/14-rdf-wg RESOLVED: accept the minutes of the 7 Sep telecon
2011/09/28-rdf-wg RESOLVED: accept minutes of 21 Sep http://www.w3.org/2011/rdf-wg/meeting/2011-09-21
2011/10/12-rdf-wg RESOLVED: In our documents, we'll use the terms "RDF Graph" for g-snap, "Graph Container" for g-box, and "Graph Serialization" for g-text
2011/10/13-rdf-wg RESOLVED: Close issue-1 saying they should be the same except for well-motivated (and small) exceptions.
2011/10/13-rdf-wg RESOLVED: Close ISSUE-46 with no action.
2011/10/13-rdf-wg RESOLVED: close ISSUE-50 stating that this WG will not revisit this issue because it is not chartered to do so.
2011/10/13-rdf-wg RESOLVED: Mark rdf:Alt as an archaic features of RDF
2011/10/13-rdf-wg RESOLVED: Mark rdf:Alt as an archaic features of RDF
2011/10/13-rdf-wg RESOLVED: Mark rdf:Bag as an archaic features of RDF
2011/10/13-rdf-wg RESOLVED: Resolve ISSUE-71 by adopting the phrasing in http://lists.w3.org/Archives/Public/public-rdf-wg/2011Sep/0083.html
2011/10/13-rdf-wg RESOLVED: The primer should have a section on each of our syntaxes
2011/10/13-rdf-wg RESOLVED: The primer should have examples in each of our syntaxes
2011/11/02-rdf-wg RESOLVED: minutes are accepted
2011/11/09-rdf-wg RESOLVED: accept the minutes of the 2 Nov telecon
2011/11/16-rdf-wg RESOLVED: resolve ISSUE-37 and ISSUE-69 by accepting new RDF Concepts section 7 as described in http://lists.w3.org/Archives/Public/public-rdf-wg/2011Nov/0056.html
2011/11/30-rdf-wg RESOLVED: resolve ISSUE-74 with -- The set of character escapes for the local part of prefix names is ~.-!$&'()*+,;=:/?#@%_ (token: PN_LOCAL); i.e., the set of URI-legal, non-alphanumerics (path, query and fragment).
2011/12/21-rdf-wg RESOLVED: Within a single RDF dataset, regardless of syntax, a single graph IRI MUST NOT be used to label more then one graph
2012/01/04-rdf-wg RESOLVED: to accept the minutes of the 21 Dec telecon
2012/01/18-rdf-wg RESOLVED: accept the minutes of the 11 Jan telecon http://www.w3.org/2011/rdf-wg/meeting/2012-01-11
2012/02/01-rdf-wg RESOLVED: accept the minutes of the 25 Jan telecon
2012/02/01-rdf-wg RESOLVED: to close ISSUE-79 http://www.w3.org/2011/rdf-wg/track/issues/79
2012/02/15-rdf-wg RESOLVED: last weeks minutes accepted
2012/02/22-rdf-wg RESOLVED: accept minutes of 15-Feb, http://www.w3.org/2011/rdf-wg/meeting/2012-02-15
2012/03/07-rdf-wg RESOLVED: take the 'B' version to solve issue-67
2012/03/14-rdf-wg RESOLVED: http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#sec-escapes should be reflected in the grammar. Eg, remove \u escaping from Prefixed Local Name
2012/03/14-rdf-wg RESOLVED: to accept the minutes of the 7 Mar telecon
2012/03/21-rdf-wg RESOLVED: Resolve Issue-73 by changing the following productions in Turtle: IRI_REF => IRIREF, IRIRef => iri, IRIRefOrFunction => iriOrFunction, VarOrIRIref => VarOrIri
2012/03/28-rdf-wg RESOLVED: accept minutes from last week
2012/03/28-rdf-wg RESOLVED: Close ISSUE-4, keeping N-triples as not deprecated
2012/04/04-rdf-wg RESOLVED: accept minutes of 2012-03-28, http://www.w3.org/2011/rdf-wg/meeting/2012-03-28
2012/04/04-rdf-wg RESOLVED: remove XML namespace and localname definitions (from 2004 draft) from current doc
2012/04/18-rdf-wg RESOLVED: accept the minutes from last week.
2012/04/18-rdf-wg RESOLVED: Use application/n-triples for content type of N-Triples
2012/04/25-rdf-wg RESOLVED: to accept the minutes of April 18 telecon
2012/05/02-rdf-wg RESOLVED: accept the minutes of the 25 Apr telecon http://www.w3.org/2011/rdf-wg/meeting/2012-04-25
2012/05/02-rdf-wg RESOLVED: RDF-WG will work on an HTML datatype that would be defined in RDF Concepts.
2012/05/02-rdf-wg RESOLVED: Resolve ISSUE-66 by adding xsd:dayTimeDuration, xsd:yearMonthDuration and xsd:dateTimeStamp to the table of recommended XSD types in RDF Concepts ED Section 5.1 (RDF Semantics has a redundant list of the same types; this also needs to be changed accordingly, or removed in favour of normatively referencing RDF Concepts.)
2012/05/02-rdf-wg RESOLVED: Resolve ISSUE-86 as proposed in http://lists.w3.org/Archives/Public/public-rdf-wg/2012May/0011.html
2012/05/09-rdf-wg RESOLVED: in RDF 1.1: [a] XMLLiterals are optional; [b] lexical space consists of well-formed XML fragments; [c] the canonical lexical form is http://www.w3.org/TR/xml-exc-c14n/, as defined in RDF 2004; [d] the value space consists of (normalized) DOM trees.
2012/05/16-rdf-wg RESOLVED: accept the minutes of the 9 May telecon:
2012/05/16-rdf-wg RESOLVED: Add an AT RISK feature to Turtle, which gives SPARQL-like alternatives to @prefix and @base, namely case-insensitive PREFIX and BASE, with no period at the end of those lines.
2012/05/16-rdf-wg RESOLVED: Close ISSUE-87 without further action as per http://lists.w3.org/Archives/Public/public-rdf-wg/2012May/0221.html
2012/05/16-rdf-wg RESOLVED: Resolve ISSUE-88 by adding xsd:duration to the list of supported XSD datatypes in RDF 1.1 as per http://lists.w3.org/Archives/Public/public-rdf-wg/2012May/0221.html
2012/05/16-rdf-wg RESOLVED: to accept the resolution to ISSUE 63 as proposed in http://lists.w3.org/Archives/Public/public-rdf-wg/2012May/0222.html but without the definition of the canonical mapping
2012/05/23-rdf-wg RESOLVED: Accept minutes from last week.
2012/05/23-rdf-wg RESOLVED: accept the minutes of the 16 May telecon
2012/05/23-rdf-wg RESOLVED: Close ISSUE-28 ("Do we need syntactic nesting of graphs (g-texts) as in N3?"), saying No, we do not -- the use cases presented to the WG can be addressed without, and making syntactic nesting pay off would require additional logic machinery that's beyond this WG's timeframe
2012/05/23-rdf-wg RESOLVED: Close ISSUE-29 (Do we support SPARQL's notion of "default graph"?'), Yes, we do.
2012/05/23-rdf-wg RESOLVED: Close ISSUE-30 ("How does SPARQL's notion of RDF dataset relate our notion of multiple graphs?"), saying we will use SPARQL's notion of RDF dataset as much of the foundation of our handling of multiple graphs.
2012/05/23-rdf-wg RESOLVED: Close ISSUE-33 ("Do we provide a way to refer sub-graphs and/or individual triples?"), with the understanding that datasets can be used to refer to sub-graphs and individual triples. This does NOT rule out sharing blank nodes between named graphs.
2012/05/23-rdf-wg RESOLVED: Close ISSUE-5 ("Should we define Graph Literal datatypes?"), saying No, we should not.
2012/05/23-rdf-wg RESOLVED: Publishing a revised version of RDF Concepts
2012/05/23-rdf-wg RESOLVED: Split the Turtle document into two - turtle and n-triples
2012/05/23-rdf-wg RESOLVED: to accept the resolution to ISSUE 63 as proposed in http://lists.w3.org/Archives/Public/public-rdf-wg/2012May/0222.html but without the definition of the canonical mapping
2012/05/30-rdf-wg RESOLVED: Accept the minutes of the 23 May telecon.
2012/05/30-rdf-wg RESOLVED: RDF-WG to publish JSON-LD syntax spec, and stripped-down version of JSON-LD API spec with framing and normalization removed, as FPWD, with intention to go on recommendation track
2012/06/13-rdf-wg RESOLVED: to accept the minutes of the 30 May telecon:
2012/06/27-rdf-wg RESOLVED: Accept minutes from June 20th 2012 telecon.
2012/06/27-rdf-wg RESOLVED: Publish the current version of the TURTLE Editors Draft as a Last Call Working Draft: http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html
2012/06/27-rdf-wg RESOLVED: Publish the JSON-LD Syntax 1.0 (shortname: json-ld-syntax) and JSON-LD API 1.0 (shortname: json-ld-api) as First Public Working Drafts on July 12th, 2012 with the caveat that publication will not occur if the proper Community Group IPR commitments are not made before that date. c.f.: http://lists.w3.org/Archives/Public/public-rdf-wg/2012Jun/0117.html
2012/07/11-rdf-wg RESOLVED: The RDF Working Group resolves to publish the JSON-LD Syntax and the JSON-LD API specifications as FPWDs on July 12th, 2012.
2012/08/08-rdf-wg RESOLVED: accept minutes for 11 and 25 July
2012/08/22-rdf-wg RESOLVED: accepted last week's minutes http://www.w3.org/2011/rdf-wg/meeting/2012-08-08
2012/08/22-rdf-wg RESOLVED: The WG thinks a diagram like http://www.w3.org/2012/08/rdf-spaces-relationships.svg is very helpful, and we should probably have something like that (probably with different terms) in RDF Concepts
2012/09/12-rdf-wg RESOLVED: Close ISSUE-21 saying Yes, Node IDs are document scope in the multi-graph syntax (TriG, etc)
2012/09/12-rdf-wg RESOLVED: minutes accepted by consensus
2012/10/03-rdf-wg RESOLVED: In our TriG dataset syntax, a "=" MUST NOT appear between the name and the graph.
2012/10/03-rdf-wg RESOLVED: In our TriG dataset syntax, the case-insensitive keyword "graph" MUST NOT appear before the name, in a name-graph pair. This is to be an "at risk" feature.
2012/10/03-rdf-wg RESOLVED: Our dataset syntax will allow for the expression of empty named graphs, whatever their semantics might be.
2012/10/03-rdf-wg RESOLVED: This Working Group will not provide a Formal Semantics for RDF Datasets or for our Dataset Syntax (eg trig). The WG may publish some information about dataset semantics in WG NOTES.
2012/10/03-rdf-wg RESOLVED: We'll request a media-type for this syntax which is different from the media-type for Turtle. (That is, we will not consider this language to supplant Turtle and take over the name, becoming the new "Turtle", as was once proposed.)
2012/10/03-rdf-wg RESOLVED: We will call a recommended dataset syntax "TriG", but informally and in the media type, "trig".
2012/10/03-rdf-wg RESOLVED: We will produce a W3C Recommendation for a dataset syntax, similar to TriG and to SPARQL's named graph syntax. This does not preclude recommending a syntax like n-quads.
2012/10/10-rdf-wg RESOLVED: accept the minutes of 2012-10-03 (http://www.w3.org/2011/rdf-wg/meeting/2012-10-03)
2012/10/10-rdf-wg RESOLVED: add example of non-ASCII IRI
2012/10/10-rdf-wg RESOLVED: i18n-178 wedge in a not-too-contrived ref in section 7 Parsing: "and an optional language tag [BCP47] or datatype IRI" per editor's draft.
2012/10/10-rdf-wg RESOLVED: i18n-179 Turtle will not add a method to declare the language of the document.
2012/10/10-rdf-wg RESOLVED: i18n-180 add this markup [[ (#005E)"]] to the first reference to each character per the editor's draft .
2012/10/10-rdf-wg RESOLVED: i18n-182 -- No change
2012/10/10-rdf-wg RESOLVED: i18n-183 -- EricP to respond with "no change unless you have further input"
2012/10/10-rdf-wg RESOLVED: i18n-184 -- Use the text U+xx form [[ U+B7, U+300 to U+36F and U+203F to U+2040 are permitted anywhere except the first character. ]] per the editor's draft
2012/10/10-rdf-wg RESOLVED: i18n-185 Alter the text introducing the 4th example in §3 to say " The line breaks in this example are LINE FEED characters (U+0A)." per editor's draft
2012/10/10-rdf-wg RESOLVED: i18n-186 : keep Turtle as UTF-8
2012/10/10-rdf-wg RESOLVED: i18n-187 Turtle will continue to use \u \U escape syntax.
2012/10/10-rdf-wg RESOLVED: i18n-188 no change -- special handling of % in IRI
2012/10/10-rdf-wg RESOLVED: i18n-190 -- No change - follow XML ed 5
2012/10/10-rdf-wg RESOLVED: i18n-191 as per http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0017.html
2012/10/10-rdf-wg RESOLVED: i18n-192 Update ReSpec for doc.
2012/10/10-rdf-wg RESOLVED: i18n-193 - no change
2012/10/10-rdf-wg RESOLVED: Leave Turtle in HTML in appendix, add stuff about escaping
2012/10/17-rdf-wg RESOLVED: In TriG, triples of the dataset's default graph MUST be surrounded by curly braces.
2012/10/17-rdf-wg RESOLVED: We reply to the Prov WG that we don't see any technical incompatibilities between their work and RDF 1 or RDF 1.1 as we currently imagine it. If a suitable example is eventually included in our docs, we will try to use PROV output therein.
2012/10/24-rdf-wg RESOLVED: Accept the minutes of the 17 Oct telecon
2012/10/24-rdf-wg RESOLVED: Add a normative section to the JSON-LD Syntax specification stating (=defining) how the JSON-LD data model aligns with the RDF data model described in RDF Concepts.
2012/10/24-rdf-wg RESOLVED: JSON-LD syntax MUST support serialization of all RDF graphs.
2012/10/29-rdf-wg RESOLVED: Close ISSUE-14. We're sticking with the SPARQL definition of Named Graphs. Informative text will explain that “named” isn't to be taken too literally, and that “named graph” often refers only to the graph part of the pair.
2012/10/29-rdf-wg RESOLVED: Close ISSUE-15, the relationship is undefined.
2012/10/29-rdf-wg RESOLVED: Close ISSUE-17 -- there is no general purpose way to merge datasets; it can only be done with external knowledge.
2012/10/29-rdf-wg RESOLVED: Close ISSUE-32 -- We do not provide a standard way to identify g-boxes or g-snaps.
2012/10/29-rdf-wg RESOLVED: Close ISSUE-35 and ISSUE-38 saying we're not going to do these in a REC, but might something like this in a WG NOTE
2012/10/29-rdf-wg RESOLVED: Close ISSUE-77 marking rdf:Seq as Archaic (saying folks shouldn't use it for new vocabs)
2012/10/29-rdf-wg RESOLVED: New Note: "RDF 1.1 New Features and Migration Guide"
2012/10/29-rdf-wg RESOLVED: Our CR exit criterion for Turtle will be: two or more implementations passing all the approved tests in the test suite.
2012/10/29-rdf-wg RESOLVED: Semantics editors accept an action to add the missing inference rule as pointed out in ISSUE-9; this closes ISSUE-9
2012/10/29-rdf-wg RESOLVED: The Semantics document will make the notion of semantics extension more explicit, and will refer to the POWDER and the SPARQL Entailment Regimes as good examples
2012/10/30-rdf-wg RESOLVED: Hold the resolution at http://www.w3.org/2011/rdf-wg/meeting/2012-10-29#resolution_2 in abeyance pending further study.
2012/10/30-rdf-wg RESOLVED: The RDF 1.1 n-triples grammar will not allow line breaks within triples
2012/10/30-rdf-wg RESOLVED: The RDF WG intends to produce a NOTE on the semantics of datasets.
2012/10/30-rdf-wg RESOLVED: The RDF WG will not publish a Note like RDF/JSON.
2012/10/30-rdf-wg RESOLVED: The WG intends to produce a NOTE: Practical Use Cases of RDF Datasets. This Note may include information from ISSUEs 32, 35 and 38.
2012/10/30-rdf-wg RESOLVED: We'll do N-Quads on the REC Track, as another Dataset serialization syntax, in line with existing, in-the-wild N-Quads.
2012/10/30-rdf-wg RESOLVED: We'll do N-Triples and N-Quads in one REC-track documents, title to be decided
2012/11/07-rdf-wg RESOLVED: close ISSUE-103
2012/11/07-rdf-wg RESOLVED: close ISSUE-91
2012/11/07-rdf-wg RESOLVED: close ISSUE-93
2012/11/07-rdf-wg RESOLVED: close ISSUE-94
2012/11/07-rdf-wg RESOLVED: close ISSUE-96
2012/11/07-rdf-wg RESOLVED: close ISSUE-97
2012/11/07-rdf-wg RESOLVED: minutes of F2F3 accepted
2012/11/07-rdf-wg RESOLVED: minutes of the 24 Oct telecon accepted
2012/11/21-rdf-wg RESOLVED: Delete four informative Notes from Concepts as described in http://lists.w3.org/Archives/Public/public-rdf-wg/2012Nov/0131.html
2012/11/21-rdf-wg RESOLVED: Informally call g-boxes “RDF sources” in Concepts
2012/11/21-rdf-wg RESOLVED: to accept the minutes of the 7 Nov telecon
2012/11/28-rdf-wg RESOLVED: publish revised WD of RDF Concepts under the condition that editors reach agreement with reviewers
2012/12/05-rdf-wg RESOLVED: accept the minutes of the 28 Nov telecon: http://www.w3.org/2011/rdf-wg/meeting/2012-11-28
2012/12/12-rdf-wg RESOLVED: Accept the minutes of the 05 December telecon: http://www.w3.org/2011/rdf-wg/meeting/2012-12-05
2012/12/12-rdf-wg RESOLVED: provide At Risk text which notes: 1 change from prior publication; 2 that the WG wants "<><><>;;;." to be legal; 3 that we will look for a grammar representation which produces no S/R conflicts in LL(1) or LALR(1)
2012/12/12-rdf-wg RESOLVED: that the Rdf WG ask the director for a transition of the Turtle Spec from Last Call to Candidate Rec
2012/12/19-rdf-wg RESOLVED: Close ISSUE-108 by converting it to an action on PatH
2012/12/19-rdf-wg RESOLVED: Given the resolution that RDF 1.1 Semantics will have a new entailment regime, ISSUE-90 can be closed as editorial
2012/12/19-rdf-wg RESOLVED: RDF 1.1 Semantics will define a new entailment regime that encompasses simple entailment and the equality of literal values.
2012/12/19-rdf-wg RESOLVED: RDF 1.1 Semantics will define a new entailment regime that encompasses simple entailment and the equality of literal values.
2013/01/09-rdf-wg RESOLVED: minutes of 19 Dec telecon accepted http://www.w3.org/2011/rdf-wg/meeting/2012-12-19
2013/01/09-rdf-wg RESOLVED: the Turtle CR will have one feature at risk: the grammar productions for SPARQL prefix and base
2013/01/16-rdf-wg RESOLVED: Accept the minutes of the 9 January telecon: http://www.w3.org/2011/rdf-wg/meeting/2013-01-09
2013/01/16-rdf-wg RESOLVED: Close ISSUE-23; we are indeed defining new formats and new media types for multi-graph.
2013/01/16-rdf-wg RESOLVED: Resolve ISSUE-16 by saying that this WG uses JSON-LD to address the charter, which internally uses RFC4627
2013/01/16-rdf-wg RESOLVED: Resolve ISSUE-92 by saying that it has been done
2013/01/23-rdf-wg RESOLVED: Close ISSUE-25 by saying that this WG will not deprecate reification of statements. We will note informatively in the RDF Schema spec that named graphs and RDF datasets are another mechanism to accomplish the same goals.
2013/01/30-rdf-wg RESOLVED: accept minutes from last meeting
2013/01/30-rdf-wg RESOLVED: Close http://www.w3.org/2011/rdf-wg/track/issues/25 by saying that this WG will not deprecate reification of statements. We will note informatively in the RDF Schema spec that named graphs and RDF datasets are another mechanism to accomplish the same goals.
2013/01/30-rdf-wg RESOLVED: to close Issue 62 (see http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jan/0107.html):
2013/02/06-rdf-wg RESOLVED: Add a non-normative statement to RDF Concepts explaining that if a RDF serialization format supports expressing both datasets and graphs, that a consumer should use the default graph if it is expecting a graph. (Actual wording to be handled by editor)
2013/02/06-rdf-wg RESOLVED: Define only dataset isomorphism normatively in RDF concepts. Possibly define other dataset operations in Dataset Semantics WG Note.
2013/02/06-rdf-wg RESOLVED: To accept the minutes of the 30 January telecon: http://www.w3.org/2011/rdf-wg/meeting/2013-01-30
2013/02/13-rdf-wg RESOLVED: add text [[ Note that concatenation of Turtle files does not necessarily produce the RDF graph merge of the two serialized graphs and can lead to unexpected results. For instance, @base may change the BASE URI, re-used blank node labels will be merged, and @prefixes may differ. ]]" to http://www.w3.org/TR/turtle/#sec-parsing-example
2013/02/13-rdf-wg RESOLVED: in accordance with our recollection of earlier decisions, the WG had elected to keep the section on "Turtle in XHMTL " as a non-normative appendix in the Turtle spec
2013/02/20-rdf-wg RESOLVED: accept the minutes of the 13 February telecon: http://www.w3.org/2011/rdf-wg/meeting/2013-02-13
2013/02/27-rdf-wg RESOLVED: closing Issue 109 as described by Pat back in November in http://lists.w3.org/Archives/Public/public-rdf-wg/2012Nov/0195.html The proposal is, roughly, to make ill-typed literals not denote anything, which (due to the very picky details of the wording of the rest of the semantics) means that any triple with an ill-typed literal is false (and not ill-typed itself, which you might have thought).
2013/03/06-rdf-wg RESOLVED: Accept the minutes of the 27 February telecon: http://www.w3.org/2011/rdf-wg/meeting/2013-02-27
2013/03/13-rdf-wg RESOLVED: Publish Semantics as FPWD marking the section on blank node scope as an ISSUE
2013/03/13-rdf-wg RESOLVED: reopen and close ISSUE-97 to make RDF interpretations interpret all IRIs as per http://lists.w3.org/Archives/Public/public-rdf-wg/2013Mar/0041.html
2013/03/13-rdf-wg RESOLVED: take TriG, n-triples and n-quads to FPWD according to http://lists.w3.org/Archives/Public/public-rdf-wg/2013Mar/0091.html
2013/03/13-rdf-wg RESOLVED: to accept the minutes of the 06 March telecon: http://www.w3.org/2011/rdf-wg/meeting/2013-03-06
2013/03/20-rdf-wg RESOLVED: bnodes generated from parsing two different RDF serializations are distinct for any current W3C syntax (draft or REC). For use cases which want something like that, try genid, or some non-standard local override, or some possible new syntax that allows specifying bnode scope.
2013/03/20-rdf-wg RESOLVED: to accept the minutes of the 13 March telecon: http://www.w3.org/2011/rdf-wg/meeting/2013-03-13
2013/03/27-rdf-wg RESOLVED: accept tests-ttl revision 1bd3ae36aebf as the presumed final Turtle test suite.
2013/03/27-rdf-wg RESOLVED: minutes of March 20 accepted
2013/04/03-rdf-wg RESOLVED: Minutes from the 2013-03-27 are accepted
2013/04/04-rdf-wg RESOLVED: approve JSON-LD test fromRdf-0001
2013/04/10-rdf-wg RESOLVED: Arnaud is willing to serve as editor for this putative note.
2013/04/10-rdf-wg RESOLVED: Minutes accepted from April 3 telecon
2013/04/10-rdf-wg RESOLVED: publish Last Call WDs of the JSON-LD documents.
2013/04/24-rdf-wg RESOLVED: Accept http://lists.w3.org/Archives/Public/public-rdf-wg/2013Apr/0118.html, changing "is an ill-typed literal, but is syntactically permissable." to "is an ill-typed literal".
2013/04/24-rdf-wg RESOLVED: Accept minutes of the 17 April Telecon, https://www.w3.org/2013/meeting/rdf-wg/2013-04-17
2013/04/24-rdf-wg RESOLVED: Close ISSUE-107 as per http://lists.w3.org/Archives/Public/public-rdf-wg/2013Apr/0115.html, up until "Note:" (We're not characterizing the relationship to RDF 1.0)
2013/04/24-rdf-wg RESOLVED: Close ISSUE-109 by making ill-typed literals not denote and requiring that RDF implementations accept ill-typed literals and produce RDF graphs from them, possibly producing a warning. http://lists.w3.org/Archives/Public/public-rdf-wg/2013Apr/0117.html
2013/05/01-rdf-wg RESOLVED: close issue-63: we'll specifying rdf:HTML by deferring the semantics (lexical-to-value mapping) to whatever is latest/greatest HTML standard. This only comes up for people trying to do D-Entailment on rdf:HTML literals --- determining equality of value, and checking for ill-typed.
2013/05/01-rdf-wg RESOLVED: to accept the minutes of the 24 April telecon
2013/05/01-rdf-wg RESOLVED: to resolve ISSUE-118 according to Pat's proposal in http://lists.w3.org/Archives/Public/public-rdf-wg/2013May/0014.html [17:55] hahah
2013/05/08-rdf-wg RESOLVED: Publish JSON-LD 1.0 API as a Second Last Call document on May 14th 2013 with a 3 week Last Call period.
2013/05/15-rdf-wg RESOLVED: Datasets can use blank nodes as graph names, not just IRIs.
2013/05/15-rdf-wg RESOLVED: Publish the latest (https://dvcs.w3.org/hg/json-ld/raw-file/default/spec/WD/json-ld-api/20130516/index.html) JSON-LD Algorithms and API 1.0 specification as a 2nd Last Call
2013/05/15-rdf-wg RESOLVED: to accept the minutes of the 08 May telecon: https://www.w3.org/2013/meeting/rdf-wg/2013-05-08
2013/05/22-rdf-wg RESOLVED: accept minutes of last meeting
2013/05/22-rdf-wg RESOLVED: resolution about blank nodes from last week [ http://www.w3.org/2013/meeting/rdf-wg/2013-05-15#resolution_2 ] is withdrawn and ISSUE-131 is opened to track the question
2013/05/22-rdf-wg RESOLVED: The value space of rdf:langString has the language tag in lower case; in the lexical form, the language tag MAY be converted to lower case (as RDF 1.0 says, but not everyone does).
2013/05/29-rdf-wg RESOLVED: accept the minutes of the 22 May telecon: https://www.w3.org/2013/meeting/rdf-wg/2013-05-22
2013/05/29-rdf-wg RESOLVED: Allow PREFIX and BASE in Turtle, and thus keep the feature in the document. This is based on the poll results at https://www.w3.org/2002/09/wbs/46168/at-sign/results
2013/06/05-rdf-wg RESOLVED: Accept the minutes of https://www.w3.org/2013/meeting/rdf-wg/2013-05-29
2013/06/12-rdf-wg RESOLVED: Close ISSUE-136 adopting Option 2; the formal interpretation (truth conditions) of a datasets is the formal interpretation (truth conditions) of its default graph
2013/06/12-rdf-wg RESOLVED: Close ISSUE-23 without general comment. We have been deciding on a case-by-case basis (YES for Turtle/TriG, NO for JSON-LD) and we expect to continue to do so.
2013/06/12-rdf-wg RESOLVED: We change the definition of RDF Datasets to allow blank node graph names. We note (in rdf-concepts) that earlier definitions of datasets did not include blank node graph names, and Skolemizaiton may be useful in providing compatiblity. This closes issue-131
2013/06/19-rdf-wg RESOLVED: accept the minutes of the 12 June telecon: https://www.w3.org/2013/meeting/rdf-wg/2013-06-12
2013/06/26-rdf-wg RESOLVED: accept the minutes of the 19 June telecon
2013/07/03-rdf-wg RESOLVED: accept all tests in http://www.w3.org/2013/TurtleTests/
2013/07/03-rdf-wg RESOLVED: accept the minutes of the 26 June telecon
2013/07/03-rdf-wg RESOLVED: Close ISSUE-113 saying that this WG's work on datasets and OWL-2's introduction of keys addresses the reported concern.
2013/07/03-rdf-wg RESOLVED: LC period for Concepts and Semantics ends 2013-09-06
2013/07/03-rdf-wg RESOLVED: Publish rdf11-concepts as a Last Call Working Draft https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html
2013/07/03-rdf-wg RESOLVED: Publish rdf11-mt as a Last Call Working Draft https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-mt/index.html
2013/07/03-rdf-wg RESOLVED: Close ISSUE-118 (datatypes) as specified in Semantics (datatype maps have been removed)
2013/07/10-rdf-wg RESOLVED: Resolve ISSUE-137 using at risk text proposed by sandro http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0138.html and a grammar based on ericP's changes http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0099.html
2013/07/10-rdf-wg RESOLVED: The WG will pursue N-Triples/N-Quads as a Rec instead of a Note
2013/07/10-rdf-wg RESOLVED: The WG will pursue publication of RDF/JSON as a Note
2013/08/07-rdf-wg RESOLVED: Accept minutes https://www.w3.org/2013/meeting/rdf-wg/2013-07-24
2013/08/21-rdf-wg RESOLVED: Accept the minutes of the 07 August telecon: https://www.w3.org/2013/meeting/rdf-wg/2013-08-07
2013/08/21-rdf-wg RESOLVED: (as in spec draft) Before this specification exits Candidate Recommendation, two or more independent implementations must pass each test, although no single implementation must pass each test. The working group will decide when the test suite is of sufficient quality to test interoperability and will produce an implementation report (hosted together with the test suite).
2013/08/21-rdf-wg RESOLVED: Close ISSUE-140 by accepting Pat's suggested change documented in http://lists.w3.org/Archives/Public/public-rdf-wg/2013Aug/0022.html
2013/08/21-rdf-wg RESOLVED: Publish both JSON-LD 1.0 and JSON-LD 1.0 Processing Algorithms and API as CR.
2013/08/21-rdf-wg RESOLVED: Publish N-Triples as LCWD.
2013/08/21-rdf-wg RESOLVED: The test are all on JSON-LD Processing Algorithms, but we consider them to cover both JSON-LD documents in their entirety.
2013/08/21-rdf-wg RESOLVED: The WG will request a duration of three (3) weeks for the JSON-LD implementation period.
2013/08/28-rdf-wg RESOLVED: Accept minutes from 2013-08-21
2013/08/28-rdf-wg RESOLVED: http://www.w3.org/mid/898EEEF1-9B7F-476B-821A-21E3A24B785F@w3.org to be WG response to ITS 2.0 review request
2013/09/04-rdf-wg RESOLVED: Close ISSUE-139 using David Booth's proposed solution at http://lists.w3.org/Archives/Public/public-rdf-wg/2013Aug/0002.html. Exact wording will be considered editorial.
2013/09/04-rdf-wg RESOLVED: Minutes of 28 August approved
2013/09/04-rdf-wg RESOLVED: Publish N-Quads as a LCWD pending the inclusion of a clarification that the Datasets referred to in the document are a subset of RDF Datasets due to the lack of support for empty graphs and to include links to the test suite.
2013/09/18-rdf-wg RESOLVED: accept https://www.w3.org/2013/meeting/rdf-wg/2013-09-11 as a record of the meeting of the 11 September meeting
2013/09/18-rdf-wg RESOLVED: moving https://dvcs.w3.org/hg/rdf/raw-file/default/drafts/trig/Overview.html to LC with the intention of skipping CR
2013/09/25-rdf-wg RESOLVED: accept minutes of last meeting
2013/10/02-rdf-wg RESOLVED: Accept the minutes https://www.w3.org/2013/meeting/rdf-wg/2013-09-25
2013/10/02-rdf-wg RESOLVED: This WG leaves semantics for datasets and naming graphs undefined and to be addressed by another WG in the future.
2013/10/09-rdf-wg RESOLVED: Accept the minutes of the 9 Oct telecon: https://www.w3.org/2013/meeting/rdf-wg/2013-10-02
2013/10/16-rdf-wg RESOLVED: Close issue-142 over Jeremy's (planned) formal objection
2013/10/16-rdf-wg RESOLVED: CR Exit for Semantics will be to have at least two implementations passing each approved new (RDF 1.1 only) test.
2013/10/16-rdf-wg RESOLVED: CR of 3 weeks (the minimum)
2013/10/16-rdf-wg RESOLVED: Remove "AT RISK" designation for "GRAPH Keyword" in TriG, keeping the feature
2013/10/16-rdf-wg RESOLVED: Remove "AT RISK" designation for "Unenclosed Triples" in TriG, keeping the feature
2013/10/16-rdf-wg RESOLVED: Resolve all AT RISK flags in JSON-LD documents as per recommendation of JSON LD Task Force, shown in http://lists.w3.org/Archives/Public/public-rdf-wg/2013Oct/0167.html
2013/10/16-rdf-wg RESOLVED: To handle Promises dependency, we make the json-ls-api be non-normative. We do not believe this needs another Last Call, given the AT RISK flag and the comments received.
2013/10/23-rdf-wg RESOLVED: close issue-127 -- we believe we've addressed it, and are timing out on confirmation from commenter
2013/10/23-rdf-wg RESOLVED: close ISSUE-145, ISSUE-147, ISSUE-159 with changes from the CR publication as agreed in email.
2013/10/23-rdf-wg RESOLVED: Consider ISSUE-148 non-blocking -- we can publish while leaving it open to handle later, as it is editorial and the commenter agrees with this plan
2013/10/23-rdf-wg RESOLVED: For Trig, N-Triples and N-Quads: each approved test (in the respective test suite) passed by two or more implementations. AND RDF 1.1 Concepts (like 2004 RDF Concepts) does not have a test suite and is not directly implemented in software.
2013/10/23-rdf-wg RESOLVED: open an "stronger semantics for datasets?" issue and postpone
2013/10/23-rdf-wg RESOLVED: Pat sends response to ISSUE-165 as in draft email. We don't really expect this to satisfy commenter, but we can handle this during CR, given it's not a substantive change. Commenter agrees we can handle this during CR.
2013/10/23-rdf-wg RESOLVED: to accept http://www.w3.org/2013/meeting/rdf-wg/2013-10-09 as a record of 9 Oct
2013/10/23-rdf-wg RESOLVED: to accept http://www.w3.org/2013/meeting/rdf-wg/2013-10-16 as a record of 16 Oct
2013/10/23-rdf-wg RESOLVED: to request the Director to advance five RDF 1.1 documents to CR (rdf11-concepts, rdf11-mt, n-quads, n-triples, trig)
2013/10/23-rdf-wg RESOLVED: to request the Director to advance JSON-LD ( http://www.w3.org/TR/json-ld/ http://www.w3.org/TR/json-ld-api/ ) to PR
2013/10/23-rdf-wg RESOLVED: We believe the json-ld and json-ld-api CR Exit Criteria have been met. We have more than two implements passing each test.
2013/10/30-rdf-wg RESOLVED: accept minutes from last week
2013/10/30-rdf-wg RESOLVED: addres TCR1 and 2 with http://www.w3.org/mid/20131002122510.GC1493@w3.org
2013/10/30-rdf-wg RESOLVED: addres TCR3 with http://www.w3.org/mid/20131002124541.GD1493@w3.org
2013/10/30-rdf-wg RESOLVED: We'll use names like "RDF 1.1 Turtle" for Turtle, TriG, N-Triples, N-Quads. Okay to informally call it "Turtle 1.1" but formally it's "RDF 1.1 Turtle".
2013/10/30-rdf-wg RESOLVED: WG will not copy the RFC3987 production for IRIs into Turtle
2013/10/30-rdf-wg RESOLVED: WG will not create a normalized NTriples bnode form for RDF test reference graphs
2013/11/06-rdf-wg RESOLVED: to accept the minutes of the 30 Oct telecon
2013/11/13-rdf-wg RESOLVED: to accept the minutes of the 6 Nov telecon: https://www.w3.org/2013/meeting/rdf-wg/2013-11-06
2013/11/20-rdf-wg RESOLVED: accept minutes of last week's telecon
2013/11/27-rdf-wg RESOLVED: accept the minutes of the 20 Nov telecon
2013/11/27-rdf-wg RESOLVED: The WG approves the test suites for TriG, N-Triples and N-Quads
2013/12/04-rdf-wg RESOLVED: Change the semantics tests to use an explicit contradiction marker, in the test manifest, instead of having everything following from a contradiction.
2013/12/04-rdf-wg RESOLVED: close issue-172 issue-173 issue-174 issue-175 as per http://lists.w3.org/Archives/Public/public-rdf-wg/2013Nov/0159.html
2013/12/04-rdf-wg RESOLVED: minutes 27 Nov accepted
2013/12/11-rdf-wg RESOLVED: accept the minutes of the 04 Dec telecon: https://www.w3.org/2013/meeting/rdf-wg/2013-12-04
2013/12/11-rdf-wg RESOLVED: close issue-156, taking no action
2013/12/11-rdf-wg RESOLVED: mark rdf:HTML and rdf:XMLLiteral as non-normative
2013/12/11-rdf-wg RESOLVED: publish Primer as FPWD, pending a proposal from the editors to provide a new multi-graph example to be used
2013/12/11-rdf-wg RESOLVED: publish What's new in RDF 1.1 as a FPWD
2013/12/11-rdf-wg RESOLVED: remove appendix A from Concepts doc and replace with a pointer to the What's new in RDF 1.1 doc
2013/12/11-rdf-wg RESOLVED: remove the Section "Using RDF/XML with HTML and XHTML" [1], as it is now obsolete.
2013/12/11-rdf-wg RESOLVED: request Director to move RDF schema to Proposed Edited Rec
2013/12/11-rdf-wg RESOLVED: request the Director to advance Turtle, TriG, N-Triples and N-Quads to Proposed Recommendation, pending updates by the editors and confirmation by the chairs
2013/12/18-rdf-wg RESOLVED: accepted the minutes of the 11 Dec telecon
2013/12/18-rdf-wg RESOLVED: Allow PREFIX and BASE in Turtle, and thus keep the feature in the document. This is based on the poll results at https://www.w3.org/2002/09/wbs/46168/at-sign/results ←
2013/12/18-rdf-wg RESOLVED: Close ISSUE-102 doing nothing as the WG is out of time
2013/12/18-rdf-wg RESOLVED: close issue-119, Turtle has a link to test suite https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html
2013/12/18-rdf-wg RESOLVED: Make reference from Concepts to Semantics non-normative
2013/12/18-rdf-wg RESOLVED: next meeting 15 Jan, and every other week following
2013/12/18-rdf-wg RESOLVED: Request W3M to extend for 2/3 months, with voluntary biweekly meetings in that period
2013/12/18-rdf-wg RESOLVED: Resolve ISSUE-148 by changing the "IRIs have global scope" bullet point in section 1.3 in Concepts to "By design, IRIs have global scope. Thus, two different appearances of an IRI denote the same resource. Violating this principle constitutes an IRI collision [WEBARCH]." http://www.w3.org/TR/webarch/#URI-collision
2013/12/18-rdf-wg RESOLVED: the RDF WG petition the Director to take JSON-LD to Recommendation immediately after the publication of the Proposed Recommendations for the rest of the RDF 1.1 work. over objection from pfps
2013/12/18-rdf-wg RESOLVED: the WG decides it has met the CR Exit Criteria for RDF 1.1 Turtle, TriG, NiTriples, and N-Quads (see statistics in PR Request
2013/12/18-rdf-wg RESOLVED: the WG decides it it has met the CR Exit Criteria for RDF 1.1 Semantics (see implementation report, https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-mt/reports/index.html )
2013/12/18-rdf-wg RESOLVED: the WG decides to rescinded the two tests below as they are not helpful to interoperability, for the reasons outlined in http://lists.w3.org/Archives/Public/public-rdf-wg/2013Dec/0305.html -- https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-mt/reports/index.html#test_datatypes-intensional-xsd-integer-string-incompatible ; https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-mt/reports/index.html#test_xmlsch-02-whitespace-face
2013/12/18-rdf-wg RESOLVED: the WG resolves to close this issue, with the rationale stated in the last response to the commenter (http://lists.w3.org/Archives/Public/public-rdf-comments/2013Dec/0098.html), noting the objection from the commenter in the Transition Request, over objection of AZ
2013/12/18-rdf-wg RESOLVED: to accept the resolution text in http://lists.w3.org/Archives/Public/public-rdf-wg/2013Dec/0283.html but delegate to the chairs and editors (of RDF Concepts) the authority to change on this matter
2013/12/18-rdf-wg RESOLVED: to request the Director to advance Concepts and Semantics to Proposed Recommendation
2014/02/12-rdf-wg RESOLVED: Close ISSUE-138 as being partially addressed in Primer, with a few editorial changes
2014/02/12-rdf-wg RESOLVED: Close ISSUE-78 as being addressed in Primer and Datasets notes
2014/02/12-rdf-wg RESOLVED: republish What's New as WG Note on 25 Feb without changes.
2014/02/12-rdf-wg RESOLVED: to accept the minutes of the 29 Jan telecon:
2014/02/12-rdf-wg RESOLVED: to ask the Director to advance eight P(E)Rs to REC, over Antoine's objection
2014/02/12-rdf-wg RESOLVED: to publish Primer as WG Note on 25 Feb with editorial changes
2014/02/12-rdf-wg RESOLVED: to publish RDF 1.1 Test Cases as WG Note
2014/02/19-rdf-wg RESOLVED: testto accept the minutes of the 12 Feb telecon: https://www.w3.org/2013/meeting/rdf-wg/2014-02-12