I meant to post the resolution by forwarding an email but i didn't post. well, i contacted the voidstar.com person they actually responded and fixed the...
... I agree. This restriction limits the use of some modules considerably (DC in particular - in most other use cases duplicate elements are common) and bans ...
... I disagree. If, for example, one provided a *feed document* with more than one channel in it how would you know which items belong to which channel? Not...
I've split my replies to make it easier to respond to individual points. ... If the allowable RDF were not constrained by the spec it would be possible to...
... I'm a huge fan of the typed-node syntax and would strongly encourage any RDF specs to promote it. My point in the issue was that I think it is overly...
... NO! You don't have to create them in two different passes! Create them /in memory/ together and then write them to disk. Or create a placeholder in the ...
... This is a very good idea. Http is the only MUST as far as I'm concerned. I don't want to jump the gun and label JavaScript as MUST NOT though. It's...
... OK, either you do two passes or you have two copies in memory. Putting the items first doesn't change the process. Suppose I'm using SAX to convert from...
... Apart from the security and accessibility issues, it's a bugger to code for, unless you pass it all to a browser to deal with. I don't like the idea that ...
... Here's a contrived example: I write about a new website being launched at http://example.com. Two months later I write again that the site has been...
... The two items /are/ about the site, correct? This is the old is it a link or a perma-link argument. I still see the rdf:about URI being the perma-link to...
... My only argument is the old Jon Postel Robustness Principle [1] "...be conservative in what you send". Using rdf:resource is, and will be, unambiguous. I...
... I know we discussed this recently. Did anyone produce a summary of the issues and positions? If not, I'll see if I can knock one together. - Ian...
... I'm pretty sure the decision was in one of the published WG minutes. It could take a while to actually end up in the draft. Requiring that both must be...
... it a link or a ... perma-link to the ... a non-issue ... destination ... I can summarise, I think: The rdf:about attribute of <item> should be the URI of...
... The actual wording in the spec is: "The {resource} URL of the channel element's rdf:about attribute must be unique with respect to any other rdf:about...
... I doubt that's the real intention of the spec. Is it more that the rdf:about isn't supposed to be used on another rss:item? That way one would avoid more...
... I agree. ... I think that this is the intention of the spec. But it's an artifact of treating the RSS as simple XML. If it was being processed as RDF then...
... As long as you're not making the same item assertion is there a problem? It does lead to issues of properly handling multiple elements (more than one ...
Correct, and in RDF your example would end up being layered into a "flattened" item: <item rdf:about="http://example.com"> <title>Example title</title> ...
... It is in the current rdf/xml working draft. The Status section at the top pointed at it: [[some non-namespaced attributes were returned to the grammar...
... Are you using this to validate arbitrary RSS input, or RSS coming from your own applications? An XML Schema for RSS would be very difficult if not...
... A relaxNG schema can be found at: http://lists.w3.org/Archives/Public/www-archive/2002Sep/0164.html (The comments about trying to get something to work in...
... The RDF Core draft doc I edit RDF/XML Syntax Specification (Revised) http://www.w3.org/TR/rdf-syntax-grammar/ has contained a RELAXNG schema for the last 3...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
