Re: XG Talk during the W3C Advisory Committee Meeting -- IPTC andCURIEs

Dear Misha,

> Please remove from your slides any association between
the IPTC
> and CURIEs.  IPTC standards do not use CURIEs and will
not be
> using CURIEs.

Thanks for your comments. I have removed this association in
the latest version of the slides.
Sorry for the confusion, I didn't aim to make such a
shortcut association and let people believe that IPTC will
make use of CURIEs.
The context is that Tim B.Lee has mentionned yesterday this
extensive discussion W3C and IPTC had on this topic. My goal
was therefore
just to mention the kind of discussion we can have with
other standardisation bodies on particular subjects (not
saying that we
necessarily agree). But I agree that at this point, it will
rather confuse the audience.

>  The new generation of IPTC standards is based on
> the use of Qualified Codes (QCodes) which are very
different
> from CURIEs.  Confusion between the two doesn't do
anyone any
> good.

I agree and I'm even now writing some text for highlighting
the differences 
Best regards.

    Raphaël

--
Raphaël Troncy
CWI (Centre for Mathematics and Computer Science),
Kruislaan 413, 1098 SJ Amsterdam, The Netherlands
e-mail: raphael.troncycwi.nl & raphael.troncygmail.com
Tel: +31 (0)20 - 592 4093
Fax: +31 (0)20 - 592 4312
Web: http://www.cwi.nl/~troncy/

[Apologies for the earlier typo in the name of the
yahoogroup]

Hi Raphaël,

> >  The new generation of IPTC standards is based on
> > the use of Qualified Codes (QCodes) which are very
different
> > from CURIEs.  Confusion between the two doesn't do
anyone any
> > good.
> 
> I agree and I'm even now writing some text for
highlighting the 
> differences 

That's good.  The main differences are ...

CURIEs (as I understand them) are a mechanism for
abbbreviating URIs 
by splitting the URI at an arbitrary point into two parts, 
associating the left part with an alias and then writing (I
don't 
know the current syntax), something like:

   alias:right/hand/side

For example, the URI:

   http://www.w3
.org/2005/Incubator/mmsem/

could be written as any of these:

   x:/

   x:sem/

   x:mmsem/

   x:/mmsem/

   x:bator/mmsem/

   x:Incubator/mmsem/

   etc

QCodes, on the other hand, are very much like QNames.  A
QCode is a 
tuple, made up of:

   a scheme URI, mapped to a scheme alias

   a code

So this could be a legal QCode:

   Scheme = http://www.ipt
c.org/NewsCodes/Subject/ -> "ncs"

   Code   = 17003001 ("weather news")

   QCode  = ncs:17003001

These, however, would *not* be legal QCodes:

            ncs:Subject/17003001

            ncs:Codes/Subject/17003001

            ncs:NewsCodes/Subject/17003001

            etc

Unlike both QNames and CURIEs, QCodes require that both the
scheme 
URI and the code URI be dereferenceable.

Misha Wolf
News Standards Manager, Reuters
Chair, News Metadata Framework WG, IPTC

This email was sent to you by Reuters, the global news and
information company. 
To find out more about Reuters visit www.about.reuters.com

Any views expressed in this message are those of the
individual sender, 
except where the sender specifically states them to be the
views of Reuters Limited.

Reuters Limited is part of the Reuters Group of companies,
of which Reuters Group PLC is the ultimate parent company.
Reuters Group PLC - Registered office address: The Reuters
Building, South Colonnade, Canary Wharf, bond E14 5EP,
United Kingdom
Registered No: 3296375
Registered in England and Wales