Re: [RFR] templates://virtuoso-opensource/{virtuoso-opensource-6.1.templates,l ibvirtodbc0.templates}
On Mon, Mar 1, 2010 at 1:40 PM, Justin B Rye <jbr@edlug.org.uk> wrote:
> Christian PERRIER wrote:
>> PS: I didn't review debian/control
>
> Diffage of just the control file.
>
> Package: virtuoso-opensource
>
> (I have to say, if there's not going to be a virtuoso-closedsource
> package, couldn't you just have called this one "virtuoso"? That
> would make it the obvious one to read first...)
Actually, upstream also distributes a closed source version deb. That
was one of the reason for the differentiated name.
>
> -Description: OpenLink Virtuoso Open-Source Edition (OSE)
>
> That tells me its name (which is already there in the package name)
> and nothing else. Instead, here's a short description:
>
> +Description: high-performance database
>
> The rest of the description continues to shout the product name at
> every opportunity, which is one of those unhelpful things homepages
> for commercial software like to do. I'll make sure the first one in
> the boilerplate mentions OpenLink and then filter most of them out
> from then on.
>
> - Virtuoso is a high-performance object-relational SQL database. As a
> - database, it provides transactions, a smart SQL compiler, powerful
> - stored-procedure language with optional Java and .Net server-side
> - hosting, hot backup, SQL-99 support and more. It has all major
> - data-access interfaces, such as ODBC, JDBC, ADO .Net and OLE/DB.
>
> (As a database? What does it provide when it's not a database?)
Actually, it does a lot more things than just database :) See below.
>
> Reshuffle the things it provides so that the heavy one is at the
> bottom (and tweak that one slightly).
>
> It's canonically .NET (and all-one word ADO.NET), not .Net, and
> SQL:1999 (or SQL3), not SQL-99.
>
> So:
>
> + OpenLink Virtuoso is a high-performance object-relational SQL database.
> + It provides transactions, a smart SQL compiler, hot backup, SQL:1999
> + support, a powerful stored-procedure language supporting server-side
> + Java or .NET, and more. It supports all major data-access interfaces,
> + including ODBC, JDBC, ADO.NET, and OLE/DB.
>
> (That's the suite-wide boilerplate paragraph; the next is specific
> to virtuoso-opensource.)
>
> - OpenLink Virtuoso supports SPARQL embedded into SQL for querying RDF
> - data stored in Virtuoso's database. SPARQL benefits from low-level
> - support in the engine itself, such as SPARQL-aware type-casting rules
> - and a dedicated IRI data type.
> + Virtuoso supports SPARQL embedded into SQL for querying RDF data stored
> + in its database. SPARQL benefits from low-level support in the engine
> + itself, such as SPARQL-aware type-casting rules and a dedicated IRI data
> + type.
>
> (Just reducing the namecalling)
>
> - This is the Virtuoso's Open-Source Edition (Virtuoso OSE).
> + Install this metapackage for the full suite of packages that make up
> + Virtuoso OSE ("Open-Source Edition").
>
> I *imagine* that's what this package is all about... the only real
> hint is the dependencies. If I went by the description I would
> assume this package provided SPARQL.
>
> Package: virtuoso-server
>
> -Description: Virtuoso OSE Server (metapackage for latest version)
> +Description: high-performance database - server dependency package
>
> Use the suite-description plus a summary of the role of this
> component. The term "metapackage" is often associated with packages
> that pull in whole suites (as virtuoso-opensource does); call this a
> dependency package instead.
>
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This is an empty package that depends on the current "best" version
> - of virtuoso-server (currently virtuoso-opensource-6.1), as determined by the
> - Virtuoso maintainers. Install this package if in doubt about which
> - Virtuoso OSE version you need. That will install the version
> - recommended by the package maintainers.
>
> This isn't much help if you don't know what's in virtuoso-server*.
> (The init script etcetera but not the binaries, I gather.)
>
> + This is an empty package depending on the current "best" version of the
> + Virtuoso server framework, as recommended by the maintainers (currently
> + virtuoso-opensource-6.1). Install this package if in doubt about
> + which version you need.
>
> "Virtuoso server framework" is the best I could come up with; any
> other suggestions?
>
> Package: virtuoso-minimal
>
> -Description: Virtuoso minimal Server (metapackage for latest version)
> +Description: high-performance database - core dependency package
>
> Same logic as for virtuoso-server.
>
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This is an empty package that depends on the current "best" version
> - of virtuoso-minimal (currently virtuoso-opensource-6.1-bin), as determined
> - by the Virtuoso maintainers. This should usually be depended on by all
> - packages which use Virtuoso as an embedded database.
> + This is an empty package depending on the current "best" version of the
> + core Virtuoso binaries, as recommended by the maintainers (currently
> + virtuoso-opensource-6.1-bin). This should usually be depended on by
> + all packages which use Virtuoso as an embedded database.
>
> Again giving some idea of what it is that it pulls in.
>
> Package: virtuoso-opensource-6.1
>
> -Description: OpenLink Virtuoso Open-Source Edition - Server support files
> +Description: high-performance database - support files
>
> Continuing in the same style of SUITE - COMPONENT synopses.
>
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This package contains the core tools and support files.
> + This package provides the Virtuoso server framework.
>
> "Tools" is misleading given that /etc/init.d/virtuoso-opensource-6.1
> is the only executable in the package.
>
> Package: virtuoso-opensource-6.1-common
>
> -Description: OpenLink Virtuoso Open-Source Edition - Common Binaries
> +Description: high-performance database - common files
>
> "Common files" is the normal term; besides, I only count one binary.
>
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This package contains the common binaries.
> + This package contains files common to all versions of Virtuoso.
>
> "Common files" may be the normal term, but it's not completely
> self-explanatory. (I'm also balancing the brandname-snippage by
> using the name in each of these final paragraphs.)
>
> Package: virtuoso-opensource-6.1-bin
>
> -Description: OpenLink Virtuoso Open-Source Edition - Server Binaries
> +Description: high-performance database - binaries
>
> Yes, this is the one with the binaries.
>
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This package contains the core binary libraries.
> + This package contains the core Virtuoso binaries.
>
> "Libraries"? This package contains only /usr/bin executables, man
> pages and /usr/share/doc material.
>
> Package: virtuoso-vsp-startpage
>
> -Description: OpenLink Virtuoso Open-Source Edition - Start Page
> +Description: high-performance database - web interface files
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This package contains the default start page for the web root.
> + This package contains the files for Virtuoso's web interface.
>
> Because it provides a lot more than one index.html file.
>
> Package: virtuoso-vad-conductor
>
> -Description: OpenLink Virtuoso Open-Source Edition - Conductor
> +Description: high-performance database - conductor module
>
> This whole VAD thing is basically just a matter of *modules*, right?
> All bundled up for the convenience of those on operating systems not
> blessed with an aptitude for package management. Or would
> "plug-in" work better?
>
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This package contains the administration interface VAD (Virtuoso
> - Application Distribution) package.
> + This package contains the Virtuoso Application Distribution module
> + for the administration interface.
>
> Avoid "this package contains the foo package".
>
> Package: virtuoso-vad-doc
>
> -Description: OpenLink Virtuoso Open-Source Edition - Documentation
> +Description: high-performance database - documentation module
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This package contains the documentation VAD (Virtuoso Application
> - Distribution) package.
> + This package contains the Virtuoso Application Distribution module
> + for the documentation.
>
> Continuing with the assumption that "module" is the word.
>
> Package: virtuoso-vad-demo
>
> -Description: OpenLink Virtuoso Open-Source Edition - Demo
> +Description: high-performance database - demo module
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This package contains the demo application VAD (Virtuoso Application
> - Distribution) package.
> + This package contains the Virtuoso Application Distribution module
> + for the demonstration application.
>
> Ditto; expanding the word "demo" once, in case anyone thought it was
> short for "demonetarization" or "demonolatry" or something.
>
> Package: virtuoso-vad-tutorial
>
> -Description: OpenLink Virtuoso Open-Source Edition - Tutorial
> +Description: high-performance database - tutorial module
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This package contains the tutorial application VAD (Virtuoso
> - Application Distribution) package.
> + This package contains the Virtuoso Application Distribution module
> + for the tutorial application.
>
> (These are applications in a web-app sort of sense, right?)
>
> Package: virtuoso-vad-rdfmappers
>
> -Description: OpenLink Virtuoso Open-Source Edition - RDF Mappers
> +Description: high-performance database - RDF mappers module
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This package contains the RDF Mappers application VAD (Virtuoso
> - Application Distribution) package.
> + This package contains the Virtuoso Application Distribution module
> + for the RDF mappers application.
>
> (Why plural?)
>
> Package: virtuoso-vad-sparqldemo
>
> -Description: OpenLink Virtuoso Open-Source Edition - SPARQL Demo
> +Description: high-performance database - SPARQL demo module
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This package contains the SPARQL Demo application VAD (Virtuoso
> - Application Distribution) package.
> + This package contains the Virtuoso Application Distribution module
> + for the SPARQL demo application.
>
> Is this a demo of SPARQL or a demo that happens to use SPARQL? I
> would expand SPARQL, but that doesn't make it much clearer.
>
> Package: virtuoso-vad-syncml
>
> -Description: OpenLink Virtuoso Open-Source Edition - SyncML
> +Description: high-performance database - SyncML module
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This package contains the SyncML application VAD (Virtuoso
> - Application Distribution) package.
> + This package contains the Virtuoso Application Distribution module
> + for Synchronization Markup Language support.
>
> Expanding it because the expansion is informative. Is "support"
> accurate?
>
> Package: virtuoso-vad-bpel
>
> -Description: OpenLink Virtuoso Open-Source Edition - BPEL
> +Description: high-performance database - BPEL module
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This package contains the BPEL application VAD (Virtuoso Application
> - Distribution) package.
> + This package contains the Virtuoso Application Distribution module
> + for Business Process Execution Language support.
>
> Ditto.
>
> Package: virtuoso-vad-isparql
>
> -Description: OpenLink Virtuoso Open-Source Edition - iSPARQL
> +Description: high-performance database - iSPARQL module
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This package contains the iSPARQL application VAD (Virtuoso
> - Application Distribution) package.
> + This package contains the Virtuoso Application Distribution module
> + for iSPARQL support.
>
> (Incidentally, is this the iSPARQL where the I stands for
> "imprecise" or the one where it means "interactive"? Neither of
> which sound very appealing, once I stop and think about it.)
>
> Package: virtuoso-vad-ods
>
> -Description: OpenLink Virtuoso Open-Source Edition - Open Data Spaces
> +Description: high-performance database - Open Data Spaces module
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> - This package contains Open Data Spaces (ODS) VAD (Virtuoso
> - Application Distribution) packages.
> + This package contains the Virtuoso Application Distribution module
> + for Open Data Spaces support.
>
> (Maybe it should specifically call it "OpenLink Open Data Spaces";
> apparently some sort of own-brand wiki/CMS.)
>
> Package: libvirtodbc0
>
> -Description: OpenLink Virtuoso Open-Source Edition - ODBC libraries
> +Description: high-performance database - ODBC libraries
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> This package contains the Virtuoso ODBC client libraries.
>
> Yes, I've actually left a line unaltered.
>
> Package: libvirtuoso5.5-cil
>
> -Description: OpenLink Virtuoso Open-Source Edition - Mono assemblies
> +Description: high-performance database - Mono assemblies
> - $OLDBOILERPLATE
> + $NEWBOILERPLATE
> .
> This package contains Virtuoso's ADO.NET data provider for Mono.
>
> Another, mainly because I have no idea what Mono assemblies are.
> --
> JBR with qualifications in linguistics, experience as a Debian
> sysadmin, and probably no clue about this particular package
>
So, about the description of Virtuoso: "high-performance database".
It's a bit restrictive.
Upstream calls Virtuoso an Universal Server or Universal Integration
Middleware. While kind of buzz wordy, they are not that far off.
See this: http://virtuoso.openlinksw.com/architect/vtechnical.htm
Virtuoso integrates heterogenous datasources pulling features, code
hosting environment for php, perl, python, external databases
rewriting (translating on the fly a relational database into a
semantic database for example)...
See what I mean?
Otherwise, all your suggestions look great to me.
Cheers
Arthur (new to all this translation stuff)
Reply to: