#RDF DATA MODEL HOW TO#

Types and Roles are examples of category A and Schemes of category B. Two categories of qualifier are widely useful, which we called A and B. We shall define a namespace for each such logically related set of terms (eg for the set of Relation Types). These will be grouped into logically related sets of terms (eg the set of Relation Types). Some of the terms (eg IsBasedOn) to be used with DC qualifiers (eg RelationType) will be defined by the DC community. The corresponding recommended abbreviation is 'dcq'. The corresponding recommended abbreviation is 'dc'.ДЇor the DC qualifiers (eg RelationType) the namespace we shall use is:

#RDF DATA MODEL HOW TO#

Understanding the 'rdf' namespace includes understanding how to extract unqualified DC values from qualified DC constructs by following the chain of 'rdf:value's.ДЇor the 15 DC elements defined in RFC 2413, the namespace we shall use is: 'simple' DC agent MUST understand the 'simple' Dublin Coreв„ў namespace (often abbreviated as 'dc') and the RDF M&S namespace (here shown as 'rdf'). In documentation we shall use the abbreviations 'DC' and 'DCQ'. We shall have two DC namespaces: one for the 15 elements and one for qualification. We refer the 'Personal vs Corporate' issue to the Sub-elements WG and ask them for information on whether/where support for this distinction is required when not handled by external name authorities. using a URI to point to a remote name file (which uses vCard or LCNAF etc).using in-line RDF from other appropriate namespaces (eg vCard or LCNAF) once use of such RDF has been sanctioned by the organisations owning the particular standards (eg vCard or LCNAF),.using a string to hold the agent's name,.We recommend that agents be described in any of the following ways: we DO NOT change any element labels (eg 'Contributor'),.we DO NOT add or remove any elements at this time,.we DO change some of the element definitions,.we DO change some of the descriptive names (eg 'Other Contributor'),.Re the Contributor/Creator/Publisher question, we advise that: The URI may be either the URI of an RDF node or a URI which should be resolved in order to obtain a value. If an explicit dc:Identifier is used, its value may be a string or a URI. The semantic purpose of a dc:Identifier is satisfied by the Resource's own URI. The value of each of the following properties may be a string or a URI. In other words, at inner levels, we do not use the fifteen DC element names to name properties. In RDF, we do not use the fifteen DC element names except as the names of properties that apply to actual resources. In other words, at the outermost level, we do not use any property names other than the fifteen DC element names. In RDF, we use only DC element names as the names of properties of nodes which represent actual resources. We shall use the term 'structural node' to denote a resource in an RDF graph that does not have an independent existence in the real world. The RDF data model is the foundation for the DC data model. This applies in particular to terminology, schemas, vocabularies etc. The DC community will 'borrow or steal' from other communities where reasonable.