You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nacer2 doesn't naturally parse to NACE r2 so I'd use a dash (in file name and URLs): nace-r2
define and use @base and prefixes to shorten all URLs. Almost no absolute URL should remain in the file. This is a great way to check consistency between URLs and make it more useful for consumers. With a bit of URL tweaking, we can get to the much nicer:
http://semstats.org/2016/challenge/semstats-2016-challenge-data-v2.7z
nacer2.ttl
nacer2
doesn't naturally parse toNACE r2
so I'd use a dash (in file name and URLs):nace-r2
@base
and prefixes to shorten all URLs. Almost no absolute URL should remain in the file. This is a great way to check consistency between URLs and make it more useful for consumers. With a bit of URL tweaking, we can get to the much nicer:xkos:notationPattern
maybe needs an anchored regexp^...$
to validate the complete value. This is unclear, see below<nacer2/concept/section>
is not definedskos:notation
use datatype^^xsd:token
^^nace-r2:
. This identifies the codes as belonging to NACE r2http://rdf-vocabulary.ddialliance.org/xkos
xkos:notationPattern
is implicitly anchored. This is unclear from its labelcode pattern
and the two pieces of info belowrdfs:comment
. Eg forxkos:notationPattern
:rdfs:comment "Structure (defined as a regular expression) of the item codes at a given level"
The text was updated successfully, but these errors were encountered: