RE: Potential TAG issue: N3 limited by the constraints of RDF/XML

Hi Norm,

As the IPTC has no plans to use RDF/XML, we're not concerned about 
the limitations of this syntax.

As N3 is not built on XML, it should be able to express triples 
without any of the limitations imposed by XML.

Misha Wolf
News Standards Manager, Reuters, www.reuters.com
Vice-Chair, News Architecture WP, IPTC, www.iptc.org/dev
Chair, News Metadata Framework WG, IPTC, www.iptc.org/dev


-----Original Message-----
From: www-tag-request@w3.org [mailto:www-tag-request@w3.org] On Behalf
Of Norman Walsh
Sent: 09 November 2005 13:57
To: www-tag@w3.org
Subject: Re: Potential TAG issue: N3 limited by the constraints of
RDF/XML

/ Misha Wolf <Misha.Wolf@reuters.com> was heard to say:
| Hi Mark (and Norm),
|
| Many thanks for clarifying the situation re N3 [1].  This poses a 
| serious problem for the IPTC.  We have hitherto intended to use 
| GRDDL to harvest triples from NewsML 2.  These triples would, 
| presumably, be expressed using N3.  In the light of the latest 
| information, our choices seem to be:
|
| -  Use N3 in a non-conforming way, eg by allowing local parts 
|    which are not NCNames.
|
| -  Use something other than N3.

I think the TAG issue, if there is one, has more to do with the
dangers of overloading the lexical form "prefix:local-part" for things
that aren't QNames than it does with the particular limitations of N3.

It appears that this limitation, by the way, is present in RDF/XML as
well.

I haven't been able to find an RDF/XML serialization for the triple:

  (<http://example.org/>, <http://127.0.0.1/1234>, "foo")

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.


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 Ltd.

Received on Wednesday, 9 November 2005 14:13:23 UTC