the
kind of treatment that non-XML formats get.
Atom is quite reasonable here. An XML vocabulary that doesn't have a
MIME type that follows the convention *and* doesn't have a namespace
is itself a badly-behaved XML vocabulary.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
On Jan 2, 2007, at 12:40, A. Pagaltzis wrote:
* Henri Sivonen [EMAIL PROTECTED] [2007-01-02 01:35]:
I hadn't thought that Atom was supposed to use innerHTML
parsing. I'd have said that you prepend
!DOCTYPE htmltitle/titlediv to what travels in the
feed and append /div to it, parse
parsing. I'd have said that you prepend !DOCTYPE htmltitle/
titlediv to what travels in the feed and append /div to it,
parse the resulting string and grab the first div in the document order.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
when they
ignore unknown media type parameters.
Given the options of a new type or a new parameter, I am +1 on the
new type. (Although in general, I don't like the proliferation of
application/*+xml types, because apps need to do root sniffing for
application/xml anyway.)
--
Henri
On Nov 28, 2006, at 22:11, Edward O'Connor wrote:
WHAT WG seems like a neutral ground, syndication-format wise, so
perhaps they're best positioned to spec feed autodiscovery in a way
that makes everybody happy.
+1 for leaving speccing this to the WHATWG.
--
Henri Sivonen
[EMAIL PROTECTED
editing links. It is too late to apply elegance
retroactively.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
resource at a well-known URI with one rel value per LF-separated line.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
is here:
http://whatwg.org/specs/web-apps/current-work/
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
that the library is not fully doing its job when the logical value is
an XML document fragment.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
inserted copy gets an explicit xml:lang.)
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
library has undergone *very* little testing.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
/syndication/atom-format-
spec.php#element.summary
Actually, there is nothing deprecated in Atom 1.0. There are only
things that are in the spec and things that are not in the spec.
There is no Atom 0.3. :-) These are not the droids you are looking
for. :-)
--
Henri Sivonen
[EMAIL
? Has anyone implemented a
strictly correct IRI datatype in a Java datatype library (for Jing
and MSV)?
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
. The parser will never know how long the document
would have been. From the parsers point of view it looks like a broken
stream while reading a finite doc. There's nothing in the XML spec
requiring the app to throw away the data structures it has already
built when the parser reports the error.
--
Henri
the Atom schema from the presets of
http://hsivonen.iki.fi/validator/ .
I would vote for leaving the text as is and having the validator give
errors on whitespace.
ITYM, the Feed Validator and not a RELAX NG validator.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
On Jul 12, 2005, at 19:16, Norman Walsh wrote:
I use Kohsuke's MSV. (msv.dev.java.net)
Cool. Thanks.
I had allowed relaxng.org tell me that MSV Supports XML syntax only.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
/validator/ )
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
On May 28, 2005, at 05:28, James Cerra wrote:
Henri Sivonen,
Yes, but MSIE^H^H^H^Hsome xml processors (cough cough) still
inappropriately
use comments for that purpose.
I am not familiar with that. What purpose exactly? Why should Atom
support it?
MSIE conditional comments. See other
On May 28, 2005, at 04:54, James Cerra wrote:
Aristotle, Henri Sivonen,
Yes, but any Atom document MUST be processable from just an XML
processor, an
?xml-stylesheet? processor,
A conforming xml-stylesheet processor will only act on the PI if it
appears in the prolog. For this reason
will precisely ignore
the embedded Schematron.
A hand-crafted checker can potentially be more useful than a validator
that is limited to what is checkable using a given schema language.
Case point: DTDs and attribute data types.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
the level
of thoroughness using an outside metric makes sense to me. Whether the
WG wants to act on the assessment is another matter.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
string:
atom:content type=application/xml
xml version=1.0?
tag //atom:content
No. It becomes a tree:
Element atom:content having attribute type=application/xml
|
\ Text: xml version=1.0? tag /
(Newlines omitted.)
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
for the receiving app, you've got bigger
problems than Atom. Hardwiring IDness based on namespaces is more
practical than relying on DTD-based data typing.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
On May 23, 2005, at 12:31, Julian Reschke wrote:
For the record: I am +1 on
http://www.intertwingly.net/wiki/pie/PaceOptionalXhtmlDiv.
+1 from me too.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
declarations.
In my opinion, alteration of a namespace by anyone other than the
entity that created it, or someone authorized by its creator, would
completely violate the nature of namespaces.
Sure. But it happens for practical reasons.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
On May 17, 2005, at 01:35, Robert Sayre wrote:
Markup from other vocabularies (foreign markup) can be used in an
Atom document,
but MUST be namespace-qualified and in a namespace other than Atom's.
Surely attributes on extension elements don't need to be ns-qualified?
--
Henri Sivonen
[EMAIL
Marketing: Atom
I'm looking forward to an article by Mark Pilgrim about the
incompatible versions of Atom deceitfully marketed as one thing. :-)
(Which is why I said +1 to Atom 1.0.)
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
On May 10, 2005, at 05:29, Tim Bray wrote:
Atom 1.0
+1 for Atom 1.0 in order to distinguish from 0.3.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
like you have to get rid
of form feeds?
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
where the moral rights can be vested in an entity
other than the author who is a natural person?
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
. If this feature is important to you, why would you
switch to a transfer protocol that doesn't have the feature? (I am not
claiming anything about the actual Gnutella features.) To me, the what
if the feed is not over HTTP argumentation seems theoretical
over-generalization.
--
Henri Sivonen
[EMAIL
On May 4, 2005, at 02:56, David Nesting wrote:
Plus, feed is kind of application-specific. What about related?
It's a spec for discovering *feeds*. It is proper to have an
app-specific rel value to avoid feed-specific apps downloading non-feed
related documents.
--
Henri Sivonen
[EMAIL
in
XML source. Why? As far as I can tell, it should be permissible to
produce Atom documents that contain no LF or CR characters.
Can't languages without spaces use long source lines and apply soft
wrapping in a source view if necessary? Why is this a wire format
problem?
--
Henri Sivonen
[EMAIL
-level specs.
Are you suggesting Mozilla is wrong in supporting xml:base in a generic
way (including in XHTML)?
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
On Apr 20, 2005, at 01:29, Robert Sayre wrote:
Henri Sivonen wrote:
Is the Relax NG schema from the appendix hosted as a standalone HTTP
resource somewhere on atompub.org ?
Now it is.
http://atompub.org/2005/04/18/atom.rnc
Thanks.
Could you also set the MIME type to application/vnd.relax-ng.rnc
rendering mechanism requires a single root but not
atom:content, shouldn't it be your responsibility to add it?
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
On Apr 20, 2005, at 11:53, Bill de hÓra wrote:
Henri Sivonen wrote:
On Apr 20, 2005, at 05:21, Graham wrote:
iii) Require that xhtml and *xml content elements have only a single
child node. That is, all xml must be wrapped in an enclosing element
(eg contenttext bbold/b more text/content would
On Apr 20, 2005, at 17:52, Robert Sayre wrote:
Henri Sivonen wrote:
Could you also set the MIME type to application/vnd.relax-ng.rnc
instead of text/plain?
Hmm. That's not a registered type, is it?
It doesn't appear in the registry. I thought that type had consensus on
the OASIS Relax NG mailing
Is the Relax NG schema from the appendix hosted as a standalone HTTP
resource somewhere on atompub.org ?
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
that the XHTML
Modularization DTDs have stuff that can be parametrized.)
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
On Apr 14, 2005, at 10:07, Thomas Broyer wrote:
[1] http://www.w3.org/TR/xhtml1-schema/
For the record, James Clark has made Relax NG schemas for some flavors
of XHTML 1.x. Surely James Clark is at least as good an authority as
the W3C. :-)
http://www.thaiopensource.com/relaxng/xhtml/
--
Henri
be clearer to say XHTML 1.x or
defining it in terms of the XHTML 1.x namespace URI.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
On Apr 13, 2005, at 03:18, Asbjørn Ulsberg wrote:
namely to use a Strict DOCTYPE.
type='xhtml' takes a fragment and Atom is DTDless. Better to stay away
from the word DOCTYPE.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
On Apr 13, 2005, at 15:37, A. Pagaltzis wrote:
* Henri Sivonen [EMAIL PROTECTED] [2005-04-13 08:25]:
On Apr 13, 2005, at 01:02, Robert Sayre wrote:
[XHTML transitional reference]
Instead of saying XHTML it would be clearer to say XHTML
1.x or defining it in terms of the XHTML 1.x namespace URI
to be added would have to
have reached similar popularity to either plain text or HTML.
That pretty much rules out XHTML 2.0, doesn't it? Good ideas from the
XHTML 2.0 namespace are being backported to the XHTML 1.x namespace, so
it is unlikely for XHTML 2.0 to reach large-scale popularity.
--
Henri
, why not
DocBook NG fragments? One might argue that DocBook NG has a better
chance of getting browser support than XHTML 2.0. ;-)
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
service still needs
all lawyer who can convincingly argue against the permission culture.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
is really intended as an
anti-anti-circumvention clause and should be rephrased as such. See
http://lists.debian.org/debian-legal/2005/03/msg00423.html
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
of the wrapper div.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
On Feb 17, 2005, at 15:09, Bill de hÓra wrote:
1. About Rob's example from MT; the point is twofold a) that what the
tool provides ootb
Wasn't that what type='HTML' was for?
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
everything in the Atom namespace is
part of the envelope and everything in the XHTML namespace is part of
the payload.)
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
if you had
Markdown content (or similar non-(X)HTML) in MySQL?
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
proper tools.
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
out of an aesthetic dislike of entity-encoded HTML?
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
/WebCore/Presto
* Less repulsive for people who really don't like entity-encoded HTML
* Easier to produce with some tools (even if you have HTML in the
first place)
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
work.
When I did a string concatenation implementation, using colonified
names was not a big deal.
5) For some combinations of clients and servers, entries produced
via an HTTP POST will end up with multiple divs.
I can anticipate that happening either way.
--
Henri Sivonen
[EMAIL PROTECTED
On Feb 8, 2005, at 07:03, Henri Sivonen wrote:
On Feb 8, 2005, at 01:55, Sam Ruby wrote:
Can I get one of you three to mock up what Tim's feed should look
like?
a:feed xmlns:a='http://purl.org/atom/ns#draft-ietf-atompub-format-04'
version='draft-ietf-atompub-format-04 : do not deploy'
xmlns
in a div.
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
of the intended audience.
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
/PaceXhtmlNamespaceDiv)
The abstract no longer matches the proposal. This seems to cause
confusion.
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
inside a Text
construct.
(Noting that the Pace was retracted by the original author.)
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
in XML.
OR
contentThis is xhtml:b xmlns:xhtml=... bold/xhtml:b/content
IMO, this on should be allowed on the same grounds.
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
On Feb 7, 2005, at 20:04, Robert Sayre wrote:
Paul Hoffman wrote:
-1. Not core. The current text has a simple way of creating archives,
and extensions can be used to create more specialized archive
formats.
-1 to the Pace. Agree in full.
-1 to the Pace. Me three.
--
Henri Sivonen
[EMAIL
(templateXhtmlDocument.importNode(n,
true));
}
Is that too much to ask from clients?
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
='XHTML'I was in the drugstore picking up a
prescription and wandered into the computer section, where I found
myself impulse-buying h:a
href='http://dvforge.com/themousebt.shtml'The Mouse BT/h:a from some
outfit
...
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
to read, you could put MathML or
even SVG there, which is fine, IMO, because I don't think it makes
sense to exclude well-known vocabularies that you could legitimately
serve embedded in application/xhtml+xml.
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
breaks for
display at places that do not have adjacent XML white-space.
(All this would be so much easier if XML used linefeeds and tabs for
pretty-printing and those could always be dropped and spaces were
always meaningful content. Too late to change it though.)
--
Henri Sivonen
[EMAIL
On Jan 31, 2005, at 03:11, Asbjørn Ulsberg wrote:
On Sun, 30 Jan 2005 22:06:23 +0200, Henri Sivonen [EMAIL PROTECTED]
wrote:
So how many European sites besides the EU have the resources to
provide translations of the *same* content in multiple languages at
the same time?
The company I work
be considered
spaces--not disregarded. Thus: Software displaying this text SHOULD
remove white-space at the beginning and end; and treat sequences of one
or more XML white-space characters as a single space.
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
, but not _identical_ to your
example, given the current spec.
You could also have
atom:title type=XHTML xmlns=http://www.w3.org/1999/xhtml;
Less: em lt; /em
/atom:title
(assuming the atom prefix to be bound higher up)
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
it is better if they cope in the
same way normatively.
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
translations of the *same* content in multiple languages at the same
time? How many of those can't provide multiple feed links and really
want to stuff everything in a single feed?
Aren't language alternatives within a feed over-engineering.
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
could let WebCore see the Atom Text construct element without
harm. So if a single container is needed, the Text construct itself is
the obvious container.
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
On Jan 29, 2005, at 00:39, Sam Ruby wrote:
Henri Sivonen wrote:
On Jan 28, 2005, at 20:21, Sam Ruby wrote:
I also don't like the restriction on where namespace declarations
must
be placed, but overall, I believe that the pace is a good idea.
I, for one, use gnu.xml.pipeline.NSFilter for ensuring
to warn you that the process by which we got to consensus on
the current setup was long, arduous, and involved a huge volume of
email, and you may get -1's based on people just not wanting to
revisit this space.
Sure, the current version is better than the mode/type stuff.
--
Henri Sivonen
[EMAIL
.
The easiest way to solve this, I think, is with examples.
Avoiding the word markup would also help avoiding any associations
with unparsed source.
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
or with a namespace prefix
-1 Atom should not micro-manage how and on which elements namespace
declarations appear.
Feed in the wild that declares the namespaces on root:
http://macsanomat.fi/atom
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
the legitimate use of serializers that
take care of namespace declarations.
-1 for the pace, still.
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
On Jan 28, 2005, at 01:38, Eric Scheid wrote:
On 28/1/05 7:39 AM, Henri Sivonen [EMAIL PROTECTED] wrote:
If the value of type is XHTML, the content of the Text construct
MUST be a single xhtml:div element
-1 gratuitous element cruft. The text construct element itself serves
as a container
support XHTML content in a Gecko-based aggregator in a
non-bogotic way (XML DOM to XML DOM copy with platupus filtering), you
get MathML for free.
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
allowing %flow.
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
On Jan 26, 2005, at 23:18, Tim Bray wrote:
On Jan 26, 2005, at 12:44 PM, Henri Sivonen wrote:
What's the difference between:
atom:title type='TEXT'I do not like
![CDATA[]]marqueegt;/atom:title
and
atom:title type='XHTML'I do not like
![CDATA[]]marqueegt;/atom:title
?
Shouldn't both render
text node does not make possible to write?
--
Henri Sivonen
[EMAIL PROTECTED]
http://iki.fi/hsivonen/
86 matches
Mail list logo
