> 3.3 RDF and parseType Literal
>
> > While modules are not required to take full advantage of RSS 1.0's RDF
framework,
> > effort should at least be made to construct modules in a way that doesn't
> > confuse RDF parsers. To this end, any element containing XML markup (i.e.
other
> > elements) that is not written as RDF should signal RDF parsers that this
> > markup should not be interpreted, instead maintained as a value using the
> > parseType="Literal" attribute.
>
> As previously discussed, I think we should be more general here and ask
> modules writers to define vocabularies that are RDF compliant
> (parseType="Literal" is only one of the criteria) and also to do their
> best to provide coherent data models for both pure XML and RDF.
Howdy Folks, Well, since our final open issue is currently under vote, I thought it high time to start preparing for the impending release of RSS 1.0. I've: *...
Rael Dornfest
rael@...
Nov 6, 2000 12:22 am
... Great work ! ... Some comments then... I) main spec [1]: 5. Core Syntax, chapter "Notation:" ... I would suggest to add a line about element order not...
Eric van der Vlist
vdv@...
Nov 6, 2000 8:16 am
... +1 ... For backwards compatibility with 0.9 (which required the use of the rdf prefix to be compatible with non-namespace-aware parsers) we must force this...
Aaron Swartz
aswartz@...
Nov 6, 2000 1:43 pm
Howdy, ... Done (though not yet online). Rael...
Rael Dornfest
rael@...
Nov 9, 2000 10:48 pm
Is anybody besides me concerned that the name of the standard was left up in the air? There was some discussion on the subject and even a poll (which had...
David King
david.king@...
Nov 6, 2000 12:38 pm
... I don't believe any WG member ever raised it as an issue. In the absence of objection, we will go ahead with the 1.0 name as we always have, because we ...
Aaron Swartz
aswartz@...
Nov 6, 2000 1:23 pm
... I completely disagree with this approach. Creating confusion and then dealing with it seems backwards to me, but if that's what the group wants to...
David King
david.king@...
Nov 6, 2000 1:45 pm
... Do really need to keep this one ? We've already given up the restriction to "the full ASCII character set, as well as all legal decimal and HTML entities"...
Eric van der Vlist
vdv@...
Nov 6, 2000 2:11 pm
... Is there a pressing reason why we shouldn't? I really can't see where it would be a serious problem.... Do you have a specific instance in mind? ... Yes,...
Aaron Swartz
aswartz@...
Nov 6, 2000 2:26 pm
Howdy, ... I'll say that its advised if you want to be 0.9 backward-compatible. Any objections? Rael ... Rael Dornfest rael@... ...
Rael Dornfest
rael@...
Nov 9, 2000 10:17 pm
... No. I have to admit it's mostly an aesthetically issue. But I think it sucks if we can have 2 documents that should be considered as equivalent according...
Eric van der Vlist
vdv@...
Nov 6, 2000 3:24 pm
... I assume you mean PCDATA, because if they are in a CDATA, they should be assumed as plain text. Even so, if this is true it is important to note this so...
Aaron Swartz
aswartz@...
Nov 6, 2000 9:47 pm
... Likely the release of 1.0 will include an announcement of some type which be a good place to clear up confusion about the two threads of evolution. What...
Ken MacLeod
ken@...
Nov 6, 2000 3:49 pm
... I share this concern. It's beginning to look like the WG members want just to sweep this issue under the table ... wish only that it should go away. Well...
Seth Russell
seth@...
Nov 6, 2000 4:02 pm
Hi, I strongly encourage "you guys" (the WG) to come up with a good name for this before you release it. Once the cat is out of the bag in the form of a final...
Jeff Barr
jeff@...
Nov 7, 2000 4:41 am
... It would be useful information to know where "you guys" (that would be the IG and larger RSS community) stand on the proposal for both specs keeping the...
Ken MacLeod
ken@...
Nov 7, 2000 5:44 am
(I am sending this to RSS-DEV and to Syndication in hope of resolving the naming issue once and for all). My stance is that what is now known as RSS 1.0 needs...
Jeff Barr
jeff@...
Nov 7, 2000 6:25 am
... People already do the same thing about 1.0. I see no reason to make _their_ statements ambiguous. People keep acting like RSS 1.0 is nothing like RSS 0.9x...
Aaron Swartz
aswartz@...
Nov 7, 2000 1:19 pm
I'm really suprised to be having this discussion over again. This message is rather long, and contains a number of excerpts from ancient RSS history that I was...
Dan Brickley
daniel.brickley@...
Nov 7, 2000 4:09 pm
... Well maybe that should tell you there is still a real problem. Look, this thing is past the point of justifications being important. Im sure your...
Seth Russell
seth@...
Nov 7, 2000 4:51 pm
... I'm opposed to this - it creates unneeded confusion. As well as that, what happens in X years time when Netscape/AOL realises what's happened and decides...
Nick Lothian
nl@...
Nov 7, 2000 6:03 am
Might as well de-lurk, because it's 3am. I've been following this since the middle of August, and it seems like the name issue comes up once every month. I...
Chase Tingley
tingley@...
Nov 7, 2000 8:13 am
... That's exactly my point. I think we should specify in the spec that elements and attributes from other namespaces can be added everywhere, even in modules...
Eric van der Vlist
vdv@...
Nov 7, 2000 7:43 am
... Thats fine by me - so long as its clear that this can take place then we should be OK. My initial quibble was that the models for the core elements are...
Leigh Dodds
ldodds@...
Nov 7, 2000 1:49 pm
Howdy, ... So what would you write, then? Suggestions welcome ;-) Rael ... Rael Dornfest rael@... Maven,...
Rael Dornfest
rael@...
Nov 9, 2000 10:41 pm
... I'm sorry, but I don't see how we can do this as Eric suggests, and still maintain RDF compatibility. The following example would be incompatible with RDF...
Aaron Swartz
aswartz@...
Nov 9, 2000 11:55 pm
... change that to ... Content Model: ANY Which is the current thinking I believe. IOW, you can't guarantee what you're going to get in any of those elements ...