Property talk:P3761
Jump to navigation
Jump to search
Documentation
IPv4 routing prefix
range of IPv4 addresses
range of IPv4 addresses
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “
List of violations of this constraint: Database reports/Constraint violations/P3761#Format, hourly updated report, SPARQL(([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]?|25[0-5])\.){3}([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]?|25[0-5])\/([0-9]|[12][0-9]|3[0-2])
”: value must be formatted using this pattern (PCRE syntax). (Help)Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P3761#Unique value, SPARQL (every item), SPARQL (by value)
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P3761#Scope, hourly updated report, SPARQL
This property is being used by: Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Merging IP ranges
[edit]In my first additions of IP ranges to institutions I have added the ranges as they are represented by RIPE, but in fact some of these ranges can be merged. For instance on University of Orléans (Q13334), the IP ranges '193.49.80.0/24','193.49.81.0/24','193.49.82.0/24','193.49.83.0/24' can be merged into '193.49.80.0/22'. I plan to merge automatically these ranges in the coming days. − Pintoch (talk) 20:57, 4 April 2017 (UTC)