W3C home > Mailing lists > Public > www-tag@w3.org > February 2011

RE: Short briefing/background doc't regarding RDFa, prefixes and HTML

From: <Misha.Wolf@thomsonreuters.com>
Date: Fri, 4 Feb 2011 01:04:23 +0000
To: <nathan@webr3.org>, <www-tag@w3.org>
CC: <newsml-g2@yahoogroups.com>
Message-ID: <A29ADE959C70A1449470AA9A212F5D801258A9C2@LONSMSXM06.emea.ime.reuters.com>
A catalog doesn't represent a registry.  There are many catalogs.  
Each large News provider uses their own catalog as well as the IPTC 
catalog.  That way large providers are able to use their own 
taxonomies, in addition to IPTC taxonomies.  Small News providers 
tend to rely on the IPTC catalog and the IPTC taxonomies.

If a recipient finds "medtop:234234" in a News Item, they must 
check the catalog to see what URI "medtop" maps to.

"medtop" is just a suggested alias.  It is perfectly legal to use 
"foo" in place of "medtop", as long as the catalog referenced by 
the News Item contains:

<scheme alias="foo" uri="http://cv.iptc.org/newscodes/mediatopic/" />


-----Original Message-----
From: Nathan [mailto:nathan@webr3.org] 
Sent: 03 February 2011 23:26
To: Wolf, Misha (M Cont Ent)
Cc: www-tag@w3.org
Subject: Re: Short briefing/background doc't regarding RDFa, prefixes
and HTML

Hi Misha,

Misha.Wolf@thomsonreuters.com wrote:
> A catalog entry looks like this:
> <scheme alias="medtop" uri="http://cv.iptc.org/newscodes/mediatopic/"

Am I correct in thinking that the catalog acts as a global scheme 
registry for all legal qcode schemes?

Such that there is only one qcode scheme catalog, and anybody 
encountering a qcode "medtop:234234" knows that it must correspond to 
the uri "http://cv.iptc.org/newscodes/mediatopic/234234"?

TIA for the clarification,


This email was sent to you by Thomson Reuters, the global news and information company.
Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters.
Received on Friday, 4 February 2011 01:05:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:37 UTC