• reification issue is currently shown as a vocabulary issue. It had to go somewhere and whilst its unclear about whether

  it is a fundamental part of the Abstract Syntax, then I've shown it not in it in the interests of keeping the abstract syntax minimal.

• Anything that M&S does not support is shown under futures.

Abstract Syntax and Semantics

• rdfms-xmllang: Why isn't xml:lang information represented within the RDF data model?
• rdfms-literal-is-xml-structure : A literal containing XML markup is not a simple string, but is an XML structure.
• rdfms-resource-semantics: What is a resource and how does it relate to other concepts such as URI and entity?
• rdfms-fragments: Confusing semantics of # fragments
• mime-types-for-rdf-docs: What mime type should RDF Schema and other RDF documents have?
• rdfms-identity-anon-resources: What URI, if any, identifies an anonymous resource?
• rdf-graph: Formal description of the properties of an RDF graph.
• rdf-equivalent-representations: RDF Model and Syntax employs various representations when describing the RDF abstract model. Are they really equivalent?
• rdf-formal-semantics: The RDF Model and Syntax Rec and RDF Schema CR do not provide a formal specification of the semantics of RDF.
• rdfms-assertion: RDF is not just a data model; an RDF statement is an assertion.
• rdfms-logical-formalism: RDF as currently defined, cannot be expressed as a logical formalism.
• rdfms-logical-terminology: RDF terminology conflicts with the well established terminology used by logicians.

Syntax Issues

• rdfms-formal-grammar: A formal grammar for RDF.
• rdfms-not-id-and-resource-attr: The propertyElt production 6.12 of the grammar does not allow both an ID attribute and a resource attribute to be specified
• rdf-containers-syntax-ambiguity : Containers match both the container specific grammar productions 6.25 through 6.31 and the typed node production 6.13.
• rdf-containers-syntax-vs-schema: The RDF Model collection classes (Bag, Seq, Alt) require parsers to have special knowledge of container semantics, making it difficult to subclass these.
• rdfms-reification-required: MUST a parser create bags of reified statements for all Description elements?
• rdfms-difference-between-ID-and-about: What is the difference between using an rdf:ID attribute to 'create' a new resource and an rdf:about attribute to refer to it?
• rdfms-abouteach: processing rdf:aboutEach requires a processing of sub-property relations.
• rdfms-xml-base: How does xml-base affect RDF?.
• rdfms-validating-embedded-rdf: RDF embedded in XHTML and other XML documents is hard to validate.
• rdfms-xml-literal-namespaces: How should a parser process namspaces in a literal which is XML markup?
• rdfms-propElt-id-with-dr : Clarify the interpretation of an ID attribute in the propertyElt production within a Description element with a distributive referrant.
• rdfms-nested-bagIDs: What triples are generated for nested description elements with bagIDs?
• rdfms-qname-uri-mapping: The mapping of QNames to URI's generates incorrect URI's.
• rdfms-uri-substructure: xmlns, uri+name pairs or just uris..? Clarification needed.
• rdfms-aboutEach-on-object How should an rdf:aboutEach attribute on an object of a statement be handled?

RDF Schema Issues

• rdfs-constraining-containers: Should it be possible to constrain the members of a container to be of a given type?
• rdfs-xml-schema-datatypes: A suggestion that the RDF Schema Spec might usefully use XML Schema datatypes in examples and/or in some formal specification of the mapping of these datatypes into the RDF model.
• rdfs-primitive-properties: A suggestion that properties such as rdfs:subClassOf, rdf:type and others should not be instances of rdf:Property, but should be primitive
• rdfs-no-cycles-in-subClassOf: Cycles of subClassOf properties are prohibited.
• rdfs-domain-and-range: Should a property be allowed more than one rdfs:range property? What should the semantics of multiple domain and range properties be?
• rdfs-subPropertyOf-semantics: The inheritance semantics of the subPropertyOf relationship needs to be clarified.
• rdfs-subClassOf-a-Property: Clarify whether a Property can have a subClassOf property, and if so, what that would mean?
• rdfs-online-char-encoding: There is problem with the character encoding of the online RDF Schema.
• rdfs-versioning: RDF Schema does not deal adequately with versioning.
• rdfs-domain-unconstrained: The rdfs:domain and rdfs:range constraints for rdfs:domain are missing from the RDF Schema for RDF Schema
• rdfs-transitive-subSubProperty: Is a sub-property of rdfs:subPropertyOf necessarily transitive?
• rdfs-clarify-subClass-and-instance: Suggestion of clearer discussion of use of subClass and instance relationships simultaneously.
• rdfs-isDefinedBy-semantics: Must the value of an rdfs:isDefinedBy property be a schema?
• rdfms-boolean-valued-properties: Suggestion for a standard way to represent boolean valued properties.
• rdfms-replace-value: Suggestion that the rdf:value property be replaced by rdf:toString.

RDF Vocabulary Issues

• rdfms-seq-representation: The ordinal property representation of containers does not support recursive processing of containers in languages such as Prolog.
• rdfms-identity-of-statements: Does the model allow different statements with the same subject/predicate/object?

RDF FAQ Issues

This section lists issues raised against Frequently Asked Questions about RDF

• faq-html-compliance: The suggested way of including RDF meta data in HTML is not compliant with HTML 4.01 or XHTML

Editorial Issues

• rdfms-editorial: General editorial comments.
• rdfms-syntax-desc-clarity: The language describing the syntax is unclear.
• rdfs-editorial: General editorial comments.
• rdfms-editorial: General editorial comments
• rdf-terminologicus: The RDF community needs a precise terminology to enable it to discuss issues.

Issues Postponed till a future Version of RDF

• rdfms-abouteachprefix
• rdf-containers-otherapproaches: The design of the RDF Model collection classes exhibit various awkward features. Might these be augmented with a 'better' design?
• rdf-equivalent-uri's: Should RDF have a mechanism for declaring two uri's to be equivalent?
• rdfms-literalsubjects: Should the subjects of RDF statements be allowed to be literals?
• rdfms-contexts: Suggestion that the concept of context is missing from RDF.
• rdfms-qnames-as-attrib-values: Suggestion that Qnames should be allowed as values for attributes such as rdf:about.
• rdfms-literals-as-resources: Consider replacing literals with resources whose URI uses the data: URI scheme.
• rdfms-quoting: The syntax needs a more convenient way to express the reification of a statement.