On 21.6.2012 22:07, Sebastian Hellmann wrote: >> Maybe you can use something different then NIF then. For example XPath >> location of element that has its-* attached to it? > Well, your chainsaw picture still seems quite appropriate. For RDFa to > work *at all* , you will need to create URIs. XPath is a candidate for > that and it is straightforward to append after a '#', which is very > similar to the way NIF uses URIs. What features would you like that > XPath location to have? Felix mentioned that evaluating XPath can be > quite expensive. I think that XPath is not expensive compared to RDF processing and further translation machinery applied to ITS decorated sources. > Could you give us a figure what would be feasible? > Something like "#xpath_html/1/body/1/h2/1" would allow to use SAX > instead of DOM, You mean probably #xpath(/html[1]/body[1]/h2[1]) Yes, this would be quite feasible. > but xpath would also not 100% proof against changes, > right? Of course, but it will at least survive changes to whitespace made by many tools. > My personal opinion on this is that RDFa inline is possible, but might > not be worth the trouble. Having RDF would be feasible, however. We shouldn't overengineer. So if event SemWeb optimist (if I can call you that way :-) have doubts about RDFa we might give it up. But it's always good to have mapping to RDF. -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka@kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member ------------------------------------------------------------------Received on Friday, 22 June 2012 08:19:54 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:45 UTC