| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Fedora takes issue with CC0. Although it doesn't really matter for this
stuff (dual licensed anyway, questionably "software", certainly not patentable,
and so on), this is simpler and more consistent with the ISC license used for
the actual software anyway.
|
|
|
|
|
|
|
|
|
|
|
|
Since most applications pay to keep these ontologies in memory, it is best to
keep them small. This replaces the "canonical" dcs ontology with a minimal and
restricted version specifically written for the subset of the vocabulary that
LV2 uses (like the xsd ontology).
|
|
|
|
|
|
I am not sure if anonymous classes like this are "officially" invalid for OWL,
but they cause problems with some tools. So, just replace them with the class
we actually use. With this, tools have no problem loading dcs.ttl as an OWL
Full ontology.
|
|
This adds more specific property types to support validation, and removed
doap:anon-root since it is unused by LV2 (and frankly I don't even know what
it's supposed to mean).
|
|
This avoids the need to do any datatype conversion for handling bounds. In
particular, it avoids troublesome range issues, like the maximum
xsd:unsignedLong being too large to fit in an xsd:long, which is likely what an
implementation without bigint support uses to represent xsd:integer.
So, avoid all of that by simply using the exact datatype in bounds for that
datatype, which makes more sense anyway.
|
|
This data costs memory, and I think it is better to not present things that
aren't useful to LV2 implementations at all here.
The whitespace annotations could be useful for cleaning up literals, but this
isn't currently used (and tends to be baked in to implementations anyway), so
remove them as well. If necessary they can be added later easily enough.
|
|
|
|
This fixes the patterns to properly match the spec (several were too strict or
otherwise impresive), and also reduces the regex syntax used to a basic and
nearly universal subset (without the use of counted replication) that should be
supported and handled consistently by even a very basic implementation.
|
|
|
|
It's unfortunate to diverge from the canonical document, but most of these
third-party schemas already do anyway. This may be technically fine according
to rdfs (I'm not sure), but it's better for the LV2 universe as a whole to
consistently eliminate such things.
|
|
|
|
|
|
|
|
Equivalent content, this is just to minimize the diff for the following commit.
|
|
|
|
|
|
|
|
When these are shown in a UI, it was an awful mess. This strips a lot
of junk that is useless in an LV2 context, and cleans up the labels to
have a consistent style.
|
|
|
|
|
|
|
