Additional 'namespace' attribute on content element?
Hi, on the NewsML list, an issue came up that due to they lack of a MIME type for NewsML using NewsML as Atom content is somewhat problematic[1]; I think this is the case with most of the more interesting XML applications out there. Is there any chance to extend/revise Atom to allow an attribute on the content element that allows to specify the namespace of XML content given the MIME type is declared as application/xml or text/xml? Actually, there is no posibility to do this as an Atom extension, is there? What is the opinion of the compund document formats experts on this? Note: I recall Mark Baker using something similar in his former RDF Forms draft: rf:Container xmlns:rf=http://www.markbaker.ca/2003/rdfforms/; xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns#; rdf:about=http://shoes.example.com/order-processor/; rf:acceptedMediaTypeapplication/xml/rf:acceptedMediaType rf:acceptedNamespace rdf:resource=http://shoe-standards.example.org/orders/shoes// rf:intent rdf:resource=http://shoe-standards.example.org/order-shoes// /rf:Container Jan [1] http://tech.groups.yahoo.com/group/newsml/message/2424 [2] http://www.markbaker.ca/2003/05/RDF-Forms/rdf-forms-old1.html
Re: Additional 'namespace' attribute on content element?
Jan Algermissen wrote: Hi, on the NewsML list, an issue came up that due to they lack of a MIME type for NewsML using NewsML as Atom content is somewhat problematic[1]; I think this is the case with most of the more interesting XML applications out there. Is there any chance to extend/revise Atom to allow an attribute on the content element that allows to specify the namespace of XML content given the MIME type is declared as application/xml or text/xml? Actually, there is no posibility to do this as an Atom extension, is there? Of course this can be done as an extension. The bigger problem is that NewsML doesn't have an XML Namespace to declare. At least, I don't see one in version 1.2 - James
Re: Additional 'namespace' attribute on content element?
Jan Algermissen wrote: on the NewsML list, an issue came up that due to they lack of a MIME type for NewsML using NewsML as Atom content is somewhat problematic[1]; From my brief reading of the thread, I got the impression that NewsML did have a media type (text/vnd.IPTC.NewsML) - it just isn't recognised as an XML media type. If that's correct, then surely you can just escape the content as you would with html or any other text/ media type. Obviously it's not ideal, but it is workable. If you think it's vitally important that the content be embedded as unescaped XML, then I would think a more practical solution would be to get a +xml media type rather than trying to extend Atom. Regards James
Re: Additional 'namespace' attribute on content element?
On Thu, Jan 04, 2007 at 08:00:29AM -0800, Jan Algermissen wrote: Is there any chance to extend/revise Atom to allow an attribute on the content element that allows to specify the namespace of XML content given the MIME type is declared as application/xml or text/xml? What is the opinion of the compund document formats experts on this? I wouldn't class myself as an expert, but why do we need an attribute? How about something like (please not text/xml, by the way :-): -- atom:content type=application/xml newsml:whatever xmlns:newsml=newsml namespace URI ... /newsml:whatever /atom:content -- I don't see a big difference between dispatch-on-namespace-of-child-of-content (which is, I believe, legal in Atom 1.0) and dispatch-on-namespace-attribute-on-content (which is what I think you're proposing). James -- /--\ James Aylett xapian.org [EMAIL PROTECTED] uncertaintydivision.org
Please add draft-ietf-atompub-typeparam to the charter [eom] -- Rob Sayre
-- cheers, Robert Sayre I would have written a shorter letter, but I did not have the time. http://franklinmint.fm/ http://feedautodiscovery.org/
Re: I-D ACTION:draft-ietf-atompub-typeparam-00.txt
Hey Bob, I have no problem with the rewording. Just waiting to see what others may have to say about it. - James Bob Wyman wrote: This document looks good on an initial quick read -- with one possible exception. It says: Atom processors that do recognize the parameter SHOULD detect and report inconsistencies between the parameter's value and the actual type of the document's root element. This would seem to be creating a directive concerning behavior which is not directly related to interoperation between systems. (I'm assuming that the destination of the reports is the user of the application, a log file, or something like that.) Thus, it seems to me that it might be inappropriate to use the SHOULD word since IETF apps are supposed to be focused on interoperation and are supposed to avoid constraining application behavior unnecessarily. May I suggest that you rewrite this sentence in a manner similar to that below: It is strongly recommended that Atom processors that do recognize the parameter detect and report bob wyman
Fwd: Atom format interpretation question
Begin forwarded message: From: John Cowan [EMAIL PROTECTED] Date: January 4, 2007 8:08:06 AM PST (CA) To: [EMAIL PROTECTED] Subject: Atom format interpretation question Am I right in thinking that content which is in fact in XML but is labeled with a media type that is neither generic XML nor ends in +xml cannot be included inline in an Atom entry? The NewsML community (which uses the registered media-type text/vnd.IPTC.NewsML) is concerned about this. -- John Cowan [EMAIL PROTECTED] http://ccil.org/~cowan Any sufficiently-complicated C or Fortran program contains an ad-hoc, informally-specified bug-ridden slow implementation of half of Common Lisp. --Greenspun's Tenth Rule of Programming (rules 1-9 are unknown)
Re: Fwd: Atom format interpretation question
If it's well-formed XML then I'd think dropping it into atom:content using type=application/xml would be acceptable. You'd just end up losing that bit of semantic metadata that tells you exactly what kind of XML it is. If you want to use the text/vnd.IPTC.NewsML media type to identify the type of XML, then you'd have to escape the markup and treat it like text. If the NewsML folks want to be able to use a proper media type to identify their stuff AND treat it as XML, they should come up with an appropriate media type registration (e.g. application/newsml+xml, etc). - James Tim Bray wrote: Begin forwarded message: From: John Cowan [EMAIL PROTECTED] Date: January 4, 2007 8:08:06 AM PST (CA) To: [EMAIL PROTECTED] Subject: Atom format interpretation question Am I right in thinking that content which is in fact in XML but is labeled with a media type that is neither generic XML nor ends in +xml cannot be included inline in an Atom entry? The NewsML community (which uses the registered media-type text/vnd.IPTC.NewsML) is concerned about this. -- John Cowan [EMAIL PROTECTED] http://ccil.org/~cowan Any sufficiently-complicated C or Fortran program contains an ad-hoc, informally-specified bug-ridden slow implementation of half of Common Lisp. --Greenspun's Tenth Rule of Programming (rules 1-9 are unknown)
Re: Additional 'namespace' attribute on content element?
On Thu, 04 Jan 2007 17:00:29 +0100, Jan Algermissen [EMAIL PROTECTED] wrote: on the NewsML list, an issue came up that due to they lack of a MIME type for NewsML using NewsML as Atom content is somewhat problematic[1]; I think this is the case with most of the more interesting XML applications out there. The more interesting XML applications out there should get a proper MIME type, that's all. Nothing wrong with Atom in this case, imo. -- Asbjørn Ulsberg -=|=-http://virtuelvis.com/quark/ «He's a loathsome offensive brute, yet I can't look away»
