<eg:prop rdf:ID="issue" eg:p1="foo" />




M&S says (according to some):

_:a <eg:prop> <#issue>.

<#issue> <eg:p1> "foo" .


Propose should be:

_:a <eg:prop> _: b.

_:b <eg:p1> "foo" .

<#issue> <rdf:type> <rdf:Statement> .

<#issue> <rdf:subject> _:a.

<#issue> <rdf:predicate> <eg:prop>.

<#issue> <rdf:object> _:b.


On the grounds that M&S is confusing and the proposal is a consistent use of rdf:ID on property elements.


Actions: Jeremy - formalize test case

Jan - update test cases document

- with this test case

- review other test cases for side effects (empty-property-elements 005)

Issue closed

ISSUE http://www.w3.org/2000/03/rdf-tracking/#rdfms-nested-bagI


A bagID reifies the property attributes on the same element as the bagid, the type node and immediately arising from property elements that are immediate children of the element containing the bagId.

In particular a property element whose statement is part of the bag, which has property attributes, those statements are not part of the bag.


<rdf:Description about="a" bagID="bag1">

<some:prop rdf:ID="st1">

<rdf:Description about="b" bagID="bag2">

<some:otherProp rdf:ID="st2"> A literal </some:otherProp> </rdf:Description>



this generates two bags:






Actions: Dave to update syntax doc

bwm: review Dave's test case in detail.

jjc: generate more test cases

Issue closed.

action: on DaveB to emphasize that rdf:li is not allowed as an attribute in the syntax doc

Do we restrict rdf/rdfs names which are not syntactic?

Answer: No.

Question: what about other names in the rdf namespace: eg. rdf:foo





_:a <rdf:foo> "foo" .

An RDF processor SHOULD generate a warning.


Actions: DaveB update syntax doc

JanG ensure test cases created and added to test cases doc.

Issue rdfms-xml-base


<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:eg="http://example.org/" xml:base="http://example.org/dir/file">

<eg:type rdf:about="" />



<http://example.org/dir/file> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://example.org/type> .



daveB update syntax doc

janG update test cases

DanC Contact RFC 2396 editors to check they agree that RDF is a different context

jjc: write up a case that in the RDF context a different algorithm is needed

In case:

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:eg="http://example.org/" xml:base="http://example.org">

<eg:type rdf:about="relfile" />


Should generate:

<http://example.org/relfile> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://example.org/type> .

(test case 11)Approved


daveB update syntax doc

janG update test cases

DanC Contact RFC 2396 editors to check they agree this is what they meant

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:eg="http://example.org/" >

<rdf:Description xml:base="http://example.org/dir/file" rdf:ID="frag" eg:value="v" />

<rdf:Description rdf:ID="frag" eg:value="v" />


Propose is not an error


error case 1 approved

error case 2 dropped and action jeremy to create +ve test case

error case 3 dropped and action jeremy to create +VE TEST CASE

action wg: review other test cases tomorrow morning.

Replace value:

Propose the WG resolve:

- that rdf:value is a property defined in the rdf namespace

- the model theory must state that rdf:value is a property

- that no other model theory semantics is defined specificaly for it



- em ensure primer describes appropriate use of rdf:value

- bwm ensure rdf:value is defined as a property in the model theory


The current M&S document will be superceded by the primer, the syntax document, the model theory and the test cases document.



Propose given above, these are now not relevant to the current document set and this issue be closed.

Action: em Update M&S errata to indicate that M&S will be superceded by the new documents primer, syntax, model theory and test cases.


Frag Id's.

Proposed: RDF uses URI's with fragment ID's to identify resources.

Action: Graham draft text for the primer, including a "here be dragons" warning

Action: DanC Highlight this issue with the TAG