- From: Victor Porton <porton@narod.ru>
- Date: Thu, 15 Feb 2018 18:45:54 +0200
- To: semantic-web <semantic-web@w3.org>
I have to build an ordered list of interpreters (Python, XSLTProc,
etc.)
The first variant to expose this in Turtle:
###############################################
@prefix : <http://portonvictor.org/ns/trans/internal/> .
@prefix lang: <http://portonvictor.org/ns/trans/scripts/#> .
:boiler :interpretersList
(
lang:xsltproc
#...
) .
lang:xsltproc
:langMinVersion "1.0" ;
:langMaxVersion "1.0" ;
:command ("xsltproc"
[ :params ("--param" :name :value) ]
:script) ;
:debianPackage "xsltproc" .
###############################################
This variant has the disadvantage that if the list grows long, there
will be a long distance between lang:xsltproc in the list and its
description (below). This makes inconvenient to read and write the
Turtle file.
This variant has the advantage that every element of the list has a
definite resource (such as lang:xsltproc) associated with it.
The second variant to expose this in Turtle:
###############################################
@prefix : <http://portonvictor.org/ns/trans/internal/> .
@prefix lang: <http://portonvictor.org/ns/trans/scripts/#> .
:boiler :interpretersList
(
[
:lang lang:xsltproc ;
:langMinVersion "1.0" ;
:langMaxVersion "1.0" ;
:command ("xsltproc"
[ :params ("--param" :name :value) ]
:script) ;
:debianPackage "xsltproc"
]
#...
) .
###############################################
The advantage of this variant is that all info about an interpreter is
presented in one place (between [ and ]). This makes it convenient to
read and edit.
The disadvantage is that there is no resource name associated with the
interpreter.
Which of the variants to choose? or maybe you know a third variant?
I may also propose to produce new version of Turtle format which would
allow to add "labeled" objects to a list? Let us discuss the exact
details of this possible new extension to Turtle syntax.
Received on Thursday, 15 February 2018 16:46:27 UTC