incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür (JIRA) <>
Subject [jira] [Commented] (JENA-31) Add possibility to connect serializers to prefix service
Date Mon, 08 Aug 2011 09:46:27 GMT


Reto Bachmann-Gmür commented on JENA-31:

Stumbled once again over an RDF/XML with lot of generated J.<NUM> prefixes. Even if
a jena-model is a graph and a prefix mapping and some user may want to have their unused prefixes
in the RDF/XML I would like to be able to have more friendly prefixes than this J.<NUM>
prefix without requiring massive additional computational costs like analysing the predicates
of all properties in advance. As even a comprehensive pre-written list of prefix binding is
not guaranteed to contain all needed prefix I see no performance or scalability advantage
not to allow connecting such a service (for RDF/XML).

For the exchangeability of writers/serializers you might want to have a look at the service
approach used in clerezza. In fact the jena-based serializer is just one of several exchageable
serializers (but currently the only one for RDF/XML, that's why I'd like to get rid of those
ugly prefixes)

> Add possibility to connect serializers to prefix service
> --------------------------------------------------------
>                 Key: JENA-31
>                 URL:
>             Project: Jena
>          Issue Type: Improvement
>          Components: Jena
>            Reporter: Reto Bachmann-Gmür
> Currently the serializers want to access the whole set of available prefimappings, instead
they shold only ask for a prefix suggestion for uris actually in the model, that way it is
possible to connect services which can suggest prefixes for a huge number of uris which is
not reasonably feasible now.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message