> From [log in to unmask] Fri Oct 18 16:30 MET 2002
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> X-Priority: 3 (Normal)
> X-MSMail-Priority: Normal
> Importance: Normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
> Date: Fri, 18 Oct 2002 15:35:18 +0100
> From: Jon Hanna <[log in to unmask]>
> Subject: Re: Namespace prefixes
> To: [log in to unmask]
>
> > I seem to remember that somewhere there is a recomendation that dcterms:
> > should be used rather than dcq: but I can't find this on the web site.
> >
> > Is there a reference to this anywhere?
> >
> > Is the following statment correct (if not I'll fix it):
> >
> > For a while the namespace prefix dcq was suggested by the DCMI for
> > refined elements, however this should not be used, dcterms is the
> > correct namespace prefix to use.
> >
> > http://purl.org/rss/1.0/modules/dcterms/#namespace_prefix
>
> It's a namespace prefix. It is inherently non-normative and up to whoever or
> whatever coded the thing.
Yupp!
>
> Recommendations will just lead to people writing lazy parsers that think
> "dcterms:" means something in itself.
>
> I normally use dcq: or qdc: when hand-coding for obvious reasons.
My favorites are dct or dcq.
>
>
There is reason in (X)HTML metatagging to follow a convention:
<meta name="dcterms:modified" content="2013-13-13"/>
versus
<meta name="dc.date.modified" content="2013-13-13"/>
In the dcq-rdf-xml paper we used "dcterms" as prefix constantly
to faciliate reading for humans.
rs
