As i Pointed out in my comment to https://issues.apache.org/jira/browse/STANBOL-914 the descriptin-template mechanism ties NavigationLink too closely to a specific implementation of the start page.
I think the most straight forward approach would be to have a method getHtmlDescription that returns a String with an html description. If we want to support localization such support should be added to the label as well. But this would clearly be out of scope for the current issue. Cheers, Reto On Thu, Feb 7, 2013 at 5:50 PM, Reto Bachmann-Gmür <[email protected]> wrote: > > > On Thu, Feb 7, 2013 at 3:27 PM, Reto Bachmann-Gmür <[email protected]>wrote: > >> >> On Wed, Feb 6, 2013 at 12:35 PM, Reto Bachmann-Gmür <[email protected]> >>> wrote: >>> > I've created STANBOL-911 for this. A remaining functionality in >>> WebFragment >>> > for which there's afaik currently no alternative is the NavigationLink. >>> > Trying to understand how this work I looked at the NavigationLink >>> > interface: label and path seem intuitively clear, but what' is the >>> > DescriptionTemplate? >>> >>> I am not completely sure, but I think this is used for the short >>> description on the Stanbol main page. >>> >>> As the feature is neither documented nor used I've created STANBOL-914 >> to remove it. >> > > Fell once again in the stanbol version mix trap: things compile even > without the respective constructor and methods but they do not run as the > dependencies depend on older versions (and that's probably also the reason > why eclipse doesn't find any references). > > Reto >
