Please add further namspaces to namespaces.tsv

[larsgsvensson]

Can you please add two more namespaces to namespaces.tsv:

1. gndo as http://d-nb.info/standards/elementset/gnd#
2. sf as http://www.opengis.net/ont/sf#
   Thanks in advance

[cgutteridge]

Have you registered those on prefix.cc?

I just use the list from there as a community generated set.

On 09/01/2014 10:10, larsgsvensson wrote:

Can you please add two more namespaces to namespaces.tsv:

1. gndo as http://d-nb.info/standards/elementset/gnd#
2. sf as http://www.opengis.net/ont/sf#
   Thanks in advance

—
Reply to this email directly or view it on GitHub
#1 Bug from
https://github.com/notifications/beacon/510699__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNDc5NTAyNSwiZGF0YSI6eyJpZCI6MjMxOTc1MTd9fQ==--8ce8e3e6fafcb012a41428ee060065e2103f3e39.gif

Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg

University of Southampton Open Data Service: http://data.southampton.ac.uk/
You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/

[larsgsvensson]

Yes, they are registered:

http://prefix.cc/gndo (some months ago)
http://prefix.cc/sf (recently)

[cgutteridge]

Great that's really easy then I've just updated the site and github repo
from prefix.cc. It's great to hear people are using the service. I
mostly built it for myself over xmas 2012 after I spent 4 hours
debugging what turned out to be a missing "#" from the end of a namespace.
On 09/01/2014 11:18, larsgsvensson wrote:

Yes, they are registered:

http://prefix.cc/gndo (some months ago)
http://prefix.cc/sf (recently)

—
Reply to this email directly or view it on GitHub
#1 (comment)
Bug from
https://github.com/notifications/beacon/510699__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNDc5OTA5MiwiZGF0YSI6eyJpZCI6MjMxOTc1MTd9fQ==--d321d54e1600bdc0927d45cbd1a83b648b7005d3.gif

Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg

University of Southampton Open Data Service: http://data.southampton.ac.uk/
You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/

[larsgsvensson]

Well I found it by chance and it's really helpful. I might deploy a local instance so that it can access our internal systems. My goal would be to have it as part of an automated test process.

Thanks for making it available,

Lars

Christopher Gutteridge notifications@github.com schrieb:

Great that's really easy then I've just updated the site and github repo
from prefix.cc. It's great to hear people are using the service. I
mostly built it for myself over xmas 2012 after I spent 4 hours
debugging what turned out to be a missing "#" from the end of a namespace.
On 09/01/2014 11:18, larsgsvensson wrote:

Yes, they are registered:

http://prefix.cc/gndo (some months ago)
http://prefix.cc/sf (recently)

—
Reply to this email directly or view it on GitHub
#1 (comment)
Bug from
https://github.com/notifications/beacon/510699__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNDc5OTA5MiwiZGF0YSI6eyJpZCI6MjMxOTc1MTd9fQ==--d321d54e1600bdc0927d45cbd1a83b648b7005d3.gif

Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg

University of Southampton Open Data Service: http://data.southampton.ac.uk/
You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/

---

Reply to this email directly or view it on GitHub:
#1 (comment)

[cgutteridge]

What I'd like to add if I have time (or if you feel keen...) is
something that detects literal datatypes like xsd:date xsd:boolean and
xsd:float and validates the value.

eg. will detect "2002-02-02"^^xsd:date as OK and "2nd Feb '02"^^xsd:date
as an error.

I've never found a good list of regular expressions to match xsd
datatypes... The code would be easy given that, without it it's an utter
pain.

On 09/01/2014 20:00, larsgsvensson wrote:

Well I found it by chance and it's really helpful. I might deploy a
local instance so that it can access our internal systems. My goal
would be to have it as part of an automated test process.

Thanks for making it available,

Lars

Christopher Gutteridge notifications@github.com schrieb:

Great that's really easy then I've just updated the site and github repo
from prefix.cc. It's great to hear people are using the service. I
mostly built it for myself over xmas 2012 after I spent 4 hours
debugging what turned out to be a missing "#" from the end of a
namespace.
On 09/01/2014 11:18, larsgsvensson wrote:

Yes, they are registered:

http://prefix.cc/gndo (some months ago)
http://prefix.cc/sf (recently)

—
Reply to this email directly or view it on GitHub

#1 (comment)

Bug from

https://github.com/notifications/beacon/510699__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNDc5OTA5MiwiZGF0YSI6eyJpZCI6MjMxOTc1MTd9fQ==--d321d54e1600bdc0927d45cbd1a83b648b7005d3.gif

Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg

University of Southampton Open Data Service:
http://data.southampton.ac.uk/
You should read the ECS Web Team blog:
http://blogs.ecs.soton.ac.uk/webteam/

---

Reply to this email directly or view it on GitHub:
#1 (comment)

—
Reply to this email directly or view it on GitHub
#1 (comment)
Bug from
https://github.com/notifications/beacon/510699__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNDgzMDQxNCwiZGF0YSI6eyJpZCI6MjMxOTc1MTd9fQ==--04db109184a0e228db48db46a24b98e6bda45dc3.gif

Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg

University of Southampton Open Data Service: http://data.southampton.ac.uk/
You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/

[larsgsvensson]

OK, I came up with this as a first try:

{
xsd:base64Binary=([a-z]|[A-Z]|[0-9]|\+|/|=|\s)*,
xsd:gYearMonth=-?\d{4,}-(0[1-9]|1[0-2])((\+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?,
xsd:time=\d\d:\d\d:\d\d(\.\d+)?((\+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?,
xsd:date=-?\d{4,}-(0[1-9]|1[0-2])-(0[1-9]|(1|2)[0-9]|3[01])((\+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?,
xsd:boolean=(true|false|0|1),
xsd:gYear=-?\d{4,}((\+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?,
xsd:duration=-?P([0-9]+Y)?([0-9]+M)?([0-9]+D)?(T([0-9]+H)?([0-9]+M)?([0-9]+(.[0-9]+)?+S)?)?,
xsd:gDay=---(0[1-9]|(1|2)[0-9]|3[01])((\+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?,
xsd:double=-?INF|NaN|(\+|-)?\d+(\.\d+)?([Ee](\+|-)?\d+)?,
xsd:float=-?INF|NaN|(\+|-)?\d+(\.\d+)?([Ee](\+|-)?\d+)?,
xsd:hexBinary=([\dABCDEF]{2})+,
xsd:gMonthDay=--(0[1-9]|1[0-2])-(0[1-9]|(1|2)[0-9]|3[01])((\+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?,
xsd:decimal=(\+|-)?\d+(\.\d+)?,
xsd:dateTime=-?\d{4,}-(0[1-9]|1[0-2])-(0[1-9]|(1|2)[0-9]|3[01])T\d\d:\d\d:\d\d(\.\d+)?((\+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?,
xsd:integer=(\+|-)?\d+
}

What I didn't do were all the derived types (except for xsd:integer), i. e. the following are missing:

 * anyURI
 * QName
 * NOTATION
 * string
 * normalizedString
 * token
 * language
 * NMToken
 * NMTokens
 * Name
 * NCName
 * ID
 * IDREF
 * IDREFS
 * ENTITY
 * ENTITIES
 * nonPositiveInteger
 * negativeInteger
 * long
 * int
 * short
 * byte
 * nonNegativeInteger
 * unsignedLong
 * unsignedInt
 * unsignedShort
 * unsignedByte
 * positiveInteger

Also, float and double are considered to have the same form (technically they differ in how large the numbers can be....)

Can you try to add it to the checker? My PHP is a bit rusty...

[cgutteridge]

dude. That's brilliant.

Have you got a reference for where you've got the patterns from?

On 13/01/14 11:12, larsgsvensson wrote:

OK, I came up with this as a first try:

{
xsd:base64Binary=([a-z]|[A-Z]|[0-9]|+|/|=|\s)*,
xsd:gYearMonth=-?\d{4,}-(0[1-9]|1[0-2])((+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?,
xsd:time=\d\d:\d\d:\d\d(.\d+)?((+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?,
xsd:date=-?\d{4,}-(0[1-9]|1[0-2])-(0[1-9]|(1|2)[0-9]|3[01])((+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?,
xsd:boolean=(true|false|0|1),
xsd:gYear=-?\d{4,}((+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?,
xsd:duration=-?P([0-9]+Y)?([0-9]+M)?([0-9]+D)?(T([0-9]+H)?([0-9]+M)?([0-9]+(.[0-9]+)?+S)?)?,
xsd:gDay=---(0[1-9]|(1|2)[0-9]|3[01])((+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?,
xsd:double=-?INF|NaN|(+|-)?\d+(.\d+)?(Ee <+%7C->?\d+)?,
xsd:float=-?INF|NaN|(+|-)?\d+(.\d+)?(Ee <+%7C->?\d+)?,
xsd:hexBinary=([\dABCDEF]{2})+,
xsd:gMonthDay=--(0[1-9]|1[0-2])-(0[1-9]|(1|2)[0-9]|3[01])((+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?,
xsd:decimal=(+|-)?\d+(.\d+)?,
xsd:dateTime=-?\d{4,}-(0[1-9]|1[0-2])-(0[1-9]|(1|2)[0-9]|3[01])T\d\d:\d\d:\d\d(.\d+)?((+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?,
xsd:integer=(+|-)?\d+
}

What I didn't do were all the derived types (except for xsd:integer),
i. e. the following are missing:

| * anyURI

• QName
• NOTATION
• string
• normalizedString
• tokeng
• language
• NMToken
• NMTokens
• Name
• NCName
• ID
• IDREF
• IDREFS
• ENTITY
• ENTITIES
• nonPositiveInteger
• negativeInteger
• long
• int
• short
• byte
• nonNegativeInteger
• unsignedLong
• unsignedInt
• unsignedShort
• unsignedByte
• positiveInteger
  |

Also, float and double are considered to have the same form
(technically they differ in how large the numbers can be....)

Can you try to add it to the checker? My PHP is a bit rusty...

—
Reply to this email directly or view it on GitHub
#1 (comment)
Bug from
https://github.com/notifications/beacon/510699__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNTE0NDM0OSwiZGF0YSI6eyJpZCI6MjMxOTc1MTd9fQ==--45a589aa20195cf102c190c3757397e2f1757a72.gif

Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg

University of Southampton Open Data Service: http://data.southampton.ac.uk/
You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/

Would you recommend the software you use to another institution?
http://uni-software.ideascale.com/

[larsgsvensson]

I wrote them myself using the information at http://www.w3.org/TR/xmlschema-2/

If I can find another hour of spare time, I shall try to get at least byte, int etc. ready. It is a bit awkward to restrict the value space using only syntactical restrictions...

[cgutteridge]

It's going to end up as code, so feel free to write something with
regexp () patterns and a note to say what their numeric constraint
should be. Actually, that might be smart for things like date... we can
give a more meaningful warning. eg. "Month must be a 2 digit value from
01 to 12" rather than just a "fail".

I don't mind having 2 rounds of checks.

On 13/01/14 15:51, larsgsvensson wrote:

I wrote them myself using the information at
http://www.w3.org/TR/xmlschema-2/

If I can find another hour of spare time, I shall try to get at least
byte, int etc. ready. It is a bit awkward to restrict the value space
using only syntactical restrictions...

—
Reply to this email directly or view it on GitHub
#1 (comment)
Bug from
https://github.com/notifications/beacon/510699__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNTE2MTA4MiwiZGF0YSI6eyJpZCI6MjMxOTc1MTd9fQ==--e7b96c3fc0f8c7f6228cf6e06dce3e502c3bfdf8.gif

Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg

University of Southampton Open Data Service: http://data.southampton.ac.uk/
You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/

Would you recommend the software you use to another institution?
http://uni-software.ideascale.com/

[larsgsvensson]

OK, then we make it simple:

datatype	syntax restriction	value restriction
xsd:nonPositiveInteger	xsd:integer	n <= 0
xsd:negativeInteger	xsd:integer	n < 0
xsd:long	xsd:integer	-9223372036854775808 <= n <= 9223372036854775807
xsd:int	xsd:integer	-2147483648 <= n <= 2147483647
xsd:short	xsd:integer	-32768 <= n <= 32767
xsd:byte	xsd:integer	-128 <= n <= 127
xsd:nonNegativeInteger	xsd:integer	n >= 0
xsd:unsignedLong	xsd:integer	0 <= n <= 18446744073709551615
xsd:unsignedInt	xsd:integer	0 <= n <= 4294967295
xsd:unsignedShort	xsd:integer	0 <= n <= 65535
xsd:unsignedByte	xsd:integer	0 <= n <= 255
xsd:positiveInteger	xsd:integer	n > 0
xsd:float	xsd:float	m = first capture group (mantissa), e = third capture group (exponent): m < 2^2 AND -149 <= e <= 104
xsd:double	xsd.float	m and e as in xsd:float: m < 2^53 AND -1075 <= e < 970

To do what you suggest with date ("Month must be a 2 digit value from 01 to 12") is nice but much more work since you have to parse the data, pick out the different parts and validate them individually.

[larsgsvensson]

Sorry, forgot to add the latest version of the regexes...

{
xsd:base64Binary=([a-z]|[A-Z]|[0-9]|\+|/|=|\s)*,
xsd:unsignedShort=\d{1,4}|[0-5]\d{4}|6[0-4]\d{3}|65[0-4]\d\d|655[0-2]\d|6553[0-5], 
xsd:gYearMonth=-?\d{4,}-(0[1-9]|1[0-2])((\+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?, 
xsd:time=\d\d:\d\d:\d\d(\.\d+)?((\+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?, 
xsd:unsignedLong=\d{1,10}, 
xsd:date=-?\d{4,}-(0[1-9]|1[0-2])-(0[1-9]|(1|2)[0-9]|3[01])((\+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?, 
xsd:boolean=(true|false|0|1), xsd:gYear=-?\d{4,}((\+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?, 
xsd:duration=-?P([0-9]+Y)?([0-9]+M)?([0-9]+D)?(T([0-9]+H)?([0-9]+M)?([0-9]+(.[0-9]+)?+S)?)?, 
xsd:gDay=---(0[1-9]|(1|2)[0-9]|3[01])((\+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?, 
xsd:double=-?INF|NaN|(\+|-)?\d+(\.\d+)?([Ee](\+|-)?\d+)?, 
xsd:float=-?INF|NaN|(\+|-)?\d+(\.\d+)?([Ee](\+|-)?\d+)?, 
xsd:hexBinary=([\dABCDEF]{2})+, 
xsd:gMonthDay=--(0[1-9]|1[0-2])-(0[1-9]|(1|2)[0-9]|3[01])((\+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?, 
xsd:decimal=(\+|-)?\d+(\.\d+)?, 
xsd:dateTime=-?\d{4,}-(0[1-9]|1[0-2])-(0[1-9]|(1|2)[0-9]|3[01])T\d\d:\d\d:\d\d(\.\d+)?((\+|-)(0[0-9]|1[0-4]):([0-5][0-9])|Z)?, 
xsd:unsignedByte=[01]\d\d|2[0-4]\d|25[0-5], 
xsd:nonNegativeInteger=\d+, 
xsd:integer=(\+|-)?\d+
}

[cgutteridge]

hmm. Is it xsd:int or xsd:integer?

On 13/01/14 17:26, larsgsvensson wrote:

OK, then we make it simple:

datatype syntax restriction value restriction
xsd:nonPositiveInteger xsd:integer n <= 0
xsd:negativeInteger xsd:integer n < 0
xsd:long xsd:integer -9223372036854775808 <= n <= 9223372036854775807
xsd:int xsd:integer -2147483648 <= n <= 2147483647
xsd:short xsd:integer -32768 <= n <= 32767
xsd:byte xsd:integer -128 <= n <= 127
xsd:nonNegativeInteger xsd:integer n >= 0
xsd:unsignedLong xsd:integer 0 <= n <= 18446744073709551615
xsd:unsignedInt xsd:integer 0 <= n <= 4294967295
xsd:unsignedShort xsd:integer 0 <= n <= 65535
xsd:unsignedByte xsd:integer 0 <= n <= 255
xsd:positiveInteger xsd:integer n > 0
xsd:float xsd:float m = first capture group (mantissa), e = third
capture group (exponent):
m < 2^2 AND -149 <= e <= 104
xsd:double xsd.float m and e as in xsd:float:
m < 2^53 AND -1075 <= e < 970

To do what you suggest with date ("Month must be a 2 digit value from
01 to 12") is nice but much more work since you have to parse the
data, pick out the different parts and validate them individually.

—
Reply to this email directly or view it on GitHub
#1 (comment)
Bug from
https://github.com/notifications/beacon/510699__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNTE2Njc5MSwiZGF0YSI6eyJpZCI6MjMxOTc1MTd9fQ==--b6cdc87d58aad9581a8cee06123725b03dca9cfa.gif

Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg

University of Southampton Open Data Service: http://data.southampton.ac.uk/
You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/

Would you recommend the software you use to another institution?
http://uni-software.ideascale.com/

[cgutteridge]

OK.
I've applied most of this if you want to give it a go.
http://graphite.ecs.soton.ac.uk/checker-dev/?uri=data.ttl&output=html

If you'd like to be credited by name, let me know, I've just added your
username to the README.txt for now.

On 13/01/14 17:26, larsgsvensson wrote:

OK, then we make it simple:

datatype syntax restriction value restriction
xsd:nonPositiveInteger xsd:integer n <= 0
xsd:negativeInteger xsd:integer n < 0
xsd:long xsd:integer -9223372036854775808 <= n <= 9223372036854775807
xsd:int xsd:integer -2147483648 <= n <= 2147483647
xsd:short xsd:integer -32768 <= n <= 32767
xsd:byte xsd:integer -128 <= n <= 127
xsd:nonNegativeInteger xsd:integer n >= 0
xsd:unsignedLong xsd:integer 0 <= n <= 18446744073709551615
xsd:unsignedInt xsd:integer 0 <= n <= 4294967295
xsd:unsignedShort xsd:integer 0 <= n <= 65535
xsd:unsignedByte xsd:integer 0 <= n <= 255
xsd:positiveInteger xsd:integer n > 0
xsd:float xsd:float m = first capture group (mantissa), e = third
capture group (exponent):
m < 2^2 AND -149 <= e <= 104
xsd:double xsd.float m and e as in xsd:float:
m < 2^53 AND -1075 <= e < 970

To do what you suggest with date ("Month must be a 2 digit value from
01 to 12") is nice but much more work since you have to parse the
data, pick out the different parts and validate them individually.

—
Reply to this email directly or view it on GitHub
#1 (comment)
Bug from
https://github.com/notifications/beacon/510699__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNTE2Njc5MSwiZGF0YSI6eyJpZCI6MjMxOTc1MTd9fQ==--b6cdc87d58aad9581a8cee06123725b03dca9cfa.gif

Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg

University of Southampton Open Data Service: http://data.southampton.ac.uk/
You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/

Would you recommend the software you use to another institution?
http://uni-software.ideascale.com/

[larsgsvensson]

hmm. Is it xsd:int or xsd:integer?

They both exist. xsd:integer is any integer number (optional sign followed by any number of digits), xsd:int is a java/C/… int, i. e. like a xsd:integer with a value range going from -2147483648 <= n <= 2147483647. Thus 2147483648 is an xsd:integer but not an xsd:int since the value is too large

[larsgsvensson]

OK.
I've applied most of this if you want to give it a go.
http://graphite.ecs.soton.ac.uk/checker-dev/?uri=data.ttl&output=html

If you'd like to be credited by name, let me know, I've just added your
username to the README.txt for now.

Pretty cool! Do I understand correctly that it shows the results of the datatype tests only if they fail?

Yes, please add name credits. Lars G. Svensson is the preferred form.