W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > October 2005

RE: CURIEs, xmlns and bandwidth

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Fri, 28 Oct 2005 15:57:51 +0100
Message-ID: <F54B171D-EB58-4EEE-826C-9A96702315FB@s15.mail.x-port.net>
To: "'Misha Wolf'" <Misha.Wolf@reuters.com>
Cc: <public-swbp-wg@w3.org>, <public-rdf-in-xhtml-tf@w3.org>

Hi Misha,

I haven't thought about how it might work, but there is also another avenue
worth exploring:

3. Devise some other inclusion mechanism, which can include attributes.

Regards,

Mark

 
Mark Birbeck
CEO
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/

Download our XForms processor from
http://www.formsPlayer.com/ 

-----Original Message-----
From: public-rdf-in-xhtml-tf-request@w3.org
[mailto:public-rdf-in-xhtml-tf-request@w3.org] On Behalf Of Misha Wolf
Sent: 28 October 2005 14:51
To: public-rdf-in-xhtml-tf@w3.org
Cc: public-swbp-wg@w3.org
Subject: RE: CURIEs, xmlns and bandwidth


Hi all,
 
We've had confirmation that xmlns declarations can't be XIncluded.
As a consequence, the IPTC does not plan to go the xmlns route for 
declaring CURIEs.  If XHTML does decide to use xmlns for CURIE 
declarations, that leaves us with two options:
 
1.  Different standards use different declaration mechanisms.
 
2.  The IPTC calls it's CURIEs by some other name.
 
Any comments?

Thanks,
 
Misha Wolf
News Standards Manager, Reuters, www.reuters.com
Vice-Chair, News Architecture Working Party, IPTC, www.iptc.org/dev


-----Original Message-----
From: public-rdf-in-xhtml-tf-request@w3.org
[mailto:public-rdf-in-xhtml-tf-request@w3.org] On Behalf Of Misha Wolf
Sent: 26 October 2005 06:36
To: public-rdf-in-xhtml-tf@w3.org
Subject: CURIEs, xmlns and bandwidth


Hi Mark and others,
 
We've been spending a lot of time discussing CURIEs at the IPTC 
meeting taking place this week in Milan and were very glad to see 
the CURIE Note and the updated RDF/A document.  We have one big 
problem, though, and that is this ...
 
We plan to use CURIEs for everything, including the principal 
taxonomies themselves, as well as all the related info, like @role, 
@creator, @type, etc.
 
If you go to:
  http://www.iptc.org/NewsCodes/
you will see that we currently have nearly 30 taxonomies for things 
like Colorspace, Genre, Of Interest To (ie Audience), Provider, 
Scene, Status, Subject, Topic Type, Videocoder, ...
 
So a news story with even a moderate number of codes will easily 
have 20 or more prefix declarations.  If we assume an average size 
of 50 bytes, that makes 1,000 bytes of prefix declarations.  And 
this is probably quite a conservative estimate.
 
As we are very concerned about bandwidth, we have been thinking of 
allowing the use of XInclude to place the prefix declarations 
outside of the news story.  Now we think (possibly wrongly) that 
XInclude may not permit the inclusion of arbitrary snippets of 
text, at any point in the XML document, eg the inclusion of the 
string:
 
  xmlns:nc="http://www.iptc.org/NewsCodes#"
 
at the point shown with "^" below:
 
  <news:item  >
             ^
Having skimmed the (quite dense) XInclude spec, we're still not 
quite sure.
 
Prior to seeing the CURIE Note, we had decided to borrow a prefix 
declaration syntax from Schematron, eg (these are made-up examples):
 
  <ns prefix="nc" uri="http://www.iptc.org/NewsCodes#"/>
  <ns prefix="lang" uri="http://www.isi.edu/in-notes/bcp/bcp47.txt#"/>
  <ns prefix="curr" uri="http://en.wikipedia.org/wiki/ISO_4217#"/>
 
We believe that XInclude would not get indigestion when presented 
with the above.
 
Any comments on the above would be very much appreciated.
 
Thanks,
Misha


-----------------------------------------------------------------
        Visit our Internet site at http://www.reuters.com

To find out more about Reuters Products and Services visit
http://www.reuters.com/productinfo 

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 Ltd.
Received on Friday, 28 October 2005 14:58:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:15:00 GMT