Closed jonnyschaefer closed 1 week ago
I will fix this bug to take into account all possible formats of number. However, the TTL you provided seems to be invalid. There is a '.' sign right after the ';' sign.
unit:BTU_IT-FT
a qudt:DerivedUnit ;
a qudt:Unit ;
dcterms:description "${\\bf BTU_{IT} \\, Foot}$ is an Imperial unit for $\\textit{Thermal Energy Length}$ expressed as $Btu-ft$."^^qudt:LatexString ;
qudt:applicableSystem sou:IMPERIAL ;
qudt:applicableSystem sou:USCS ;
qudt:conversionMultiplier 321.581024 ;
qudt:conversionMultiplierSN 3.21581024E2 ;
qudt:definedUnitOfSystem sou:IMPERIAL ;
qudt:definedUnitOfSystem sou:USCS ;
qudt:expression "$Btu-ft$"^^qudt:LatexString ;
qudt:hasDimensionVector qkdv:A0E0L3I0M1H0T-2D0 ;
qudt:hasQuantityKind quantitykind:ThermalEnergyLength ;
qudt:symbol "Btu{IT}·ft" ;
qudt:ucumCode "[Btu_IT].[ft_i]"^^qudt:UCUMcs ;
rdfs:isDefinedBy <http://qudt.org/vocab/unit> ;
rdfs:label "BTU Foot"@en ;
.
Hello.
Thank you for the last fixes. I have the feeling, that this go package evolves to be one of the only sane go turtle parsers that works on real world turtle files.
While trying https://qudt.org/vocab/unit/ I noticed that it does not handle floats correctly: https://www.w3.org/TR/turtle/#abbrev, as e. g.
42E3
,1e0
,-2.3E-12
,+.3e+2
are also valid float representations.Example:
returns triples like