Monday, January 17, 2005, 5:06:47 AM, you wrote:
I think this proposal throws out the baby with the bathwater.
I don't see any reason to introduce an atom:language element;
xml:lang can serve exactly the same purpose. If you want to
reduce the effect on performance/DBs, there are the
* Henry Story [EMAIL PROTECTED] [2005-01-17 16:12+0100]
I have put up two pages (Paces) on the wiki.
One AtomOWL [1] just is a place to work on the latest RDF model of
Atom, and fulfill
the requirement that Atom have a model.
The Other AtomIsRDF [2] is a place to track the way for
On 17 Jan 2005, at 18:16, Dan Brickley wrote:
[snip]
I fear [2] is unfortunately named. Atom is RDF-like in some ways,
but until the Atom spec says Atom is RDF, Atom isn't RDF. A surface
similarity to RDF's XML encoding, or even to RDF's graph data model,
isn't by itself enough to declare that
--On Monday, January 17, 2005 12:16:36 PM -0500 Dan Brickley [EMAIL PROTECTED] wrote:
I fear [2] is unfortunately named. Atom is RDF-like in some ways,
but until the Atom spec says Atom is RDF, Atom isn't RDF.
Call it AtomAsRDF.
wunder
--
Walter Underwood
Principal Architect
Verity Ultraseek
Tim Bray wrote:
On Jan 17, 2005, at 12:47 AM, David Powell wrote:
I think that if we allow xml:lang then it should definitely be
restricted. The current xml:lang everywhere situation is only simple
to implement if you assume that your implementation stores all of it's
data in an XML DOM.
This
Tim Bray wrote:
Draft format-04 says Requirements regarding the content and
interpretation of xml:lang are specified in XML 1.0
[W3C.REC-xml-20040204] Section 2.12. If the element or attribute so
labeled contains free text, xml:lang is relevant. If not, not. If you
don't know (i.e. on some
On Mon, Jan 17, 2005 at 04:32:49PM -0500, Robert Sayre wrote:
entry xml:lang=en xmlns=... xmlns:ext=...
...
!-- a comment --
updated xml:lang=de ext:att=neintime/updated
/entry
I think it should be acceptable to return the following:
entry xml:lang=en
What I'm wondering here is whether or not a retracted / or retracts
/ element could be used for this purpose. The retracted / element
would be used within an entry to indicate that the entry has been
retracted. The retracts / element would be used within a second
entry to identify it as a
On Jan 15, 2005, at 10:47 AM, David Powell wrote:
I've just updated this proposal thanks to some of the feedback that I
received. There is a change history at the end of the document.
I'm OK with this. Also OK without it, but I gather that it would
improve some people's comfort levels. Anyone
On Mon, 17 Jan 2005 23:38:50 +0100, Henry Story [EMAIL PROTECTED] wrote:
Take for example the following extension proposed recently
entry
idtag://sometag/id
geo:x10.1/geo:x
geo:y57.3/geo:y
...
/entry
this implies the following rdf graph
_e
James Snell wrote:
The retracted / element would be used within an entry to indicate that
the entry has been retracted.
I must admit that I find myself going around in circles concerning
this issue of retractions. I may be overly analyzing this. In any case, the
following is my current
Henry Story wrote:
this implies the following rdf graph
_e -entry- _E
|-id--tag://sometag
|-geo:x-10.1
|-geo:y-57.3
[On a technical point, I would disagree the graph is implied. As I said
earlier, this kind of assumption concerns me.]
If you look at the AtomOWL
At 17:47 05/01/17, David Powell wrote:
Reading the XML spec, I'm not clear that we're allowed to restrict the
inheritance of xml:lang?
From the spec:
The intent declared with xml:lang is considered to apply to all
attributes and content of the element where it is specified, unless
overridden
At 05:15 05/01/18, David Powell wrote:
Monday, January 17, 2005, 6:11:22 PM, you wrote:
Suppose Joi Ito wants to list his name in
Japanese but still write in English; or the the reverse.
Let's hope he doesn't want to provide a name in more than one language.
Well, I can definitely imagine
At 04:54 05/01/18, Danny Ayers wrote:
It's been a long time since I looked at XML schemas, but would be
possible to express the content type attribute at all neatly using a
complex type? I imagine the TEXT | HTML | XHTML part would be
straightforward, but doesn't the | pretty/much;anything option
At 05:16 05/01/18, David Powell wrote:
Monday, January 17, 2005, 7:32:48 PM, you wrote:
There are some fields in Atom which are language-independent or
neutral and thus it might be useful to explicitly prevent the use of
xml:lang tags for these elements or simply state that they have
16 matches
Mail list logo
