W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > December 2012

Preserving markup when distilling @property values in xhtml

From: Sebastian Heath <sebastian.heath@gmail.com>
Date: Thu, 20 Dec 2012 17:39:35 -0500
Message-ID: <CACsb_1pSv0z_3p9FGKy2v17zUqVTWv26p=6E2=y=1Pf2AuLiqw@mail.gmail.com>
To: RDFa WG <public-rdfa-wg@w3.org>
Hi,

 I'm guessing this is a topic that has some history behind it...

I am editing an article for the online scholarly journal "ISAW
Papers". The current text is available through my SugarSync account
[1].

It includes markup along the lines of:

<p class="reference" rel="dcterms:references"
typeof="dcterms:bibliographicResource"><span
property="dcterms:bibliographicCitation">Wright, M. T., A. G. Bromley,
and E Magkou. 1995. "Simple X-Ray Tomography and the Antikythera
Mechanism." <i>PACT Journal of the European Study Group on Physical,
Chemical and Mathematical Techniques Applied to Archaeology</i> 45,
531-543.</span></p>

When I pass that through the w3 distiller [2], I get

[ a dc:bibliographicResource;
            dc:bibliographicCitation "Wright, M. T., A. G. Bromley,
and E Magkou. 1995. \"Simple X-Ray Tomography and the Antikythera
Mechanism.\" PACT Journal of the European Study Group on Physical,
Chemical and Mathematical Techniques Applied to Archaeology 45,
531-543."@en ],


My issue is that the '<i>' element has been dropped out. I guess this
is because the original XMLLitteral is being co-erced into a plain
string. If that's the explanation, I think that is the incorrect
default behavior. I understand that I can add an @datatype, but that
will make my markup very messy. Particularly as I've chosen a simple
case. There are lots of places where I want to preserve the markup in
@property as that markup communicates important aspects of the data.
Again, the underlying data is an XML literal and I suggest that the
default behavior should be to preserve that when distilling RDFa in
XHTML contexts.

 It is possible that such preservation of markup should only be
defined for RDFa in (X)HTML(5). Again, why destroy good structured
information in a host-language context?

 Thanks for any reactions,

 Sebastian.

p.s You can see a published preprint of the article at [3]. That has
less complete markup in it so very little RDFa.




[1] https://www.sugarsync.com/pf/D7102992_62549779_91998

[2] http://www.w3.org/2012/pyRdfa/extract?uri=https%3A%2F%2Fwww.sugarsync.com%2Fpf%2FD7102992_62549779_91998%3FdirectDownload%3Dtrue&format=turtle&rdfagraph=output&vocab_expansion=false&rdfa_lite=false&embedded_rdf=true&space_preserve=true&vocab_cache=true&vocab_cache_report=false&vocab_cache_refresh=false

[3] http://dlib.nyu.edu/awdl/isaw/isaw-papers/4/preprint/


----------
Sebastian Heath, Ph.D.,
Research Assistant Professor of Ancient Studies,
Institute for the Study of the Ancient World,
New York University.

http://isaw.nyu.edu/people/faculty/sebastian-heath
Received on Thursday, 20 December 2012 22:40:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:19:57 UTC