I was looking into this again... I see that RDFParserRegistry already
has the required collections langTriples and langQuads.
I think simply adding accessors for them would solve my use case.
Something like this maybe?
public static Set registeredLangTriples()
{
return
PRs welcome.
On 23/05/2022 08:51, Martynas Jusevičius wrote:
Could RDFParserRegistry::getRegistered and
ResultSetReaderRegistry::getRegistered be added?
Consistent naming would be registered().
Andy
On Fri, May 20, 2022 at 9:01 PM Andy Seaborne wrote:
On 20/05/2022 14:05, Martynas
Could RDFParserRegistry::getRegistered and
ResultSetReaderRegistry::getRegistered be added?
On Fri, May 20, 2022 at 9:01 PM Andy Seaborne wrote:
>
>
>
> On 20/05/2022 14:05, Martynas Jusevičius wrote:
> > Andy, is that correct?
>
> Yes
>
> Andy
>
> >
> > On Tue, May 17, 2022 at 1:33 PM
On 20/05/2022 14:05, Martynas Jusevičius wrote:
Andy, is that correct?
Yes
Andy
On Tue, May 17, 2022 at 1:33 PM Martynas Jusevičius
wrote:
On Tue, May 17, 2022 at 1:19 PM Andy Seaborne wrote:
RDFLanguages is a general registry of names (Lang's) in the system.
It is not for
Andy, is that correct?
On Tue, May 17, 2022 at 1:33 PM Martynas Jusevičius
wrote:
>
> On Tue, May 17, 2022 at 1:19 PM Andy Seaborne wrote:
> >
> > RDFLanguages is a general registry of names (Lang's) in the system.
> >
> > It is not for functionality.
> >
> > RDFParserRegistry
> >
On Tue, May 17, 2022 at 1:19 PM Andy Seaborne wrote:
>
> RDFLanguages is a general registry of names (Lang's) in the system.
>
> It is not for functionality.
>
> RDFParserRegistry
> RDFWriterRegistry
> RowSetReaderRegistry, ResultSetReaderRegistry
> RowSetWriterRegistry, ResultSetWriterRegistry
>
RDFLanguages is a general registry of names (Lang's) in the system.
It is not for functionality.
RDFParserRegistry
RDFWriterRegistry
RowSetReaderRegistry, ResultSetReaderRegistry
RowSetWriterRegistry, ResultSetWriterRegistry
StreamRDFWriter
A Lang needs looking up in a registry to see if there
Hi,
After upgrading from 4.3.2 to 4.5.0, some of our RDF writing code
started failing.
It seems that this is due to RDFLanguages.isTriples(Lang.SHACLC)
returning true, which messes up our content negotiation as it attempts
to write Models as SHACLC. Can this be rectified?
The RDFLanguages
