[ 
https://issues.apache.org/jira/browse/JENA-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500650#comment-17500650
 ] 

Andy Seaborne commented on JENA-2297:
-------------------------------------

Turtle has comments.

The configuration file can be in any RDF syntax - including JSON-LD (which 
technically is YAML). An {{@context}} would be nice to have _if_ someone wishes 
to propose and contribute one.

There are some RDF-in-YAML systems so you can write in YAML and translate to 
another RDF syntax. Try one of those.

There is a lot of RDF-based code behind configuration - 1000's of lines of code.

You can even have the server write configuration files for you so you are never 
starting from scratch (see your stackoverflow answer.)

A YAML overlay that translated to RDF for interpretation would be practical and 
it could be a subset of of the expressivity if someone wishes to make a 
concrete proposal and contribute.

It will have to address the needs of Fuseki configuration - multiple 
independent subsystems like jena-text, inference, data access control. They use 
the ability of RDF to have data from different places without clashes.

YAML has its own peculiarities.

 

> Change configuration files to YAML or other similarly simple syntax
> -------------------------------------------------------------------
>
>                 Key: JENA-2297
>                 URL: https://issues.apache.org/jira/browse/JENA-2297
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Fuseki
>            Reporter: Wolfgang Fahl
>            Priority: Minor
>
> As outlined in 
> [https://stackoverflow.com/questions/63874908/fuseki-configuration] i never 
> understood the turtle configuration files. RDF syntax is just to outwordly to 
> beginners. 
> I suggest to not go with ttl files as the only option for the configuration 
> since these files are not self explaining. In YAML e.g. you can have proper 
> comments. Converting the YAML Files to ttl for internal use is IMHO fine. 
> It's just for better readability.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to