- From: Ivan Herman <ivan@w3.org>
- Date: Mon, 29 Oct 2007 16:59:21 +0100
- To: Mark Birbeck <mark.birbeck@formsPlayer.com>
- Cc: Bent Rasmussen <incredibleshrinkingsphere@gmail.com>, Karl Dubost <karl@w3.org>, public-rdf-in-xhtml-tf@w3.org
- Message-ID: <47260359.2040809@w3.org>
Mark Birbeck wrote: > Hi Bent, Karl...the list. :) > > This is very interesting discussion, but it actually pertains more to > RDF than to RDFa. Is there somewhere better that anyone can suggest > that we could move the discussion to? > SWIG (semantic-web@w3.org)? Ivan > I'm keen to continue it, since this is actually one of the use-cases I > was hoping to work on when I first got involved with the XHTML 2 work, > but I'm also wary of frightening the life out of anyone who has come > to this list looking for chat about RDFa. :) > > Mark > > On 29/10/2007, Bent Rasmussen <incredibleshrinkingsphere@gmail.com> wrote: >> >> Hello Karl >> >> That was the old (malformed) example, based on a misunderstanding of Turtle >> semantics. The newer example was structured so that rdf:value attaches >> element content to an element (doesn't have to be rdf:value of course), >> rdf:List maintains element content ordering; hopefully I "got" Turtle now. >> Attributes are unordered and just attached to the element node directly via >> regular properties. >> >> The idea I have is to capture the entire portal as RDF, including form >> posts. That requires, at first, an HTML <=> RDF bi-directional >> transformation. I'll make a taxonomy akin to the DOM one to make querying a >> bit more interesing. Then the deam would be to have an editor directly work >> on top of the RDF datamodel so only RDF => HTML will be necessary past that >> point. This editor will enable different kinds of annotations to the text >> which can be exposed to the user in the rendered HTML ("D", or "Ajax"). >> >> Of course RDFa could also be used to capture some information, but I'd like >> to maintain a full RDF model all the time. Not sure all the opportunities it >> opens, but I'm pondering... >> >> I'm not sure I get the parser ordering issue. Whilst RDF graphs are not >> intrinsically ordered, it would be very disappointing to me if it was >> somehow not useful to semantically capture ordering. That's the reason for >> rdf:List, right? I get the open world assumption, but >> >> Regards >> >> Bent >> >> >> 2007/10/29, Karl Dubost <karl@w3.org>: >>> >>> Bent Rasmussen (27 oct. 2007 - 03:37) : >>>> h:p rdf:value ( >>>> h:text rdf:value "It has to be possible!" >>>> ) >>>> h:p rdf:value ( >>> … >>> >>>> Ordering is preserved where necessary. >>> I'm worried because specifically a graph is not done to preserve >>> ordering. So that will break going from parsers to parsers. >>> >>> What is the benefit to express everything in RDF? >>> What is the specific use case you have in mind? >>> >>> >>> -- >>> Karl Dubost - http://www.w3.org/People/karl/ >>> W3C Conformance Manager, QA Activity Lead >>> QA Weblog - http://www.w3.org/QA/ >>> *** Be Strict To Be Cool *** >>> >>> >>> >>> >> > > -- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ PGP Key: http://www.ivan-herman.net/pgpkey.html FOAF: http://www.ivan-herman.net/foaf.rdf
Received on Monday, 29 October 2007 15:59:28 UTC