Comments (3)
Hi Thomas,
Thanks for your comments!
Double:
bsdd:ReplacedObjectCode a rdf:Property ;
skos:prefLabel "Replaced Object Code"@en ;
rdfs:range xsd:string .bsdd:replacingObjectCode a rdf:Property ;
skos:prefLabel "Replacing Object Code"@en ;
rdfs:range xsd:string .
They're not duplicates, these are ISO 12006-3 properties. It is about "being replaced by" and "replacing". If "A" replaces "B" then for "A" ReplacingObjectCode will be "B" and for "B" ReplacedObjectCode will be "A".
Vvisual
Pparent
Uunit
Typos will be fixed
Everything range string, I'd look for ways to enforce more consistency in the data, e.g prevent Netherlands/Holland/NL/nl/The Netherlands. I understand that there needs to be a reasonable sync between RDF <-> database, so it might not be possible, to normalize everything into classes (or maybe it is...).
Ranges are checked upon input in the bSDD. RDF is (at least for the moment) meant for output only.
Not sure if it is useful to have all range values listed in the ttl. Some of the ranges can still be extended (e.g. range of units).
XSD can be imported as an ontology:
Not sure what you mean by this, can you give an example?
skos:note/rdfs:comment?
I think you mean replace "bsdd:Description" by one of those?
The documentation of skos:note says "it could be a definition, information about the scope of a concept, editorial information, or any other type of information.". "Description" is more demarcated definition which I think can be useful.
rdfs:comment: "is used to provide a human-readable description of a resource"
Looks like can use this one. Or add a predicate saying that bsdd:Description is same as rdfs:comment.
Thanks again for your comment!
from bsdd.
They're not duplicates, these are ISO 12006-3 properties. It is about "being replaced by" and "replacing". If "A" replaces "B" then for "A" ReplacingObjectCode will be "B" and for "B" ReplacedObjectCode will be "A".
Ok, but I don't think it makes a lot of sense to define both in the data. E.g in a sparql query it's trivial to query in both directions:
SELECT ?x WHERE {
<bsdd:Wall> <bsdd:ReplacedObjectCode> ?x .
}
SELECT ?x WHERE {
?x <bsdd:ReplacedObjectCode> <bsdd:Wall> .
}
XSD can be imported as an ontology:
Not sure what you mean by this, can you give an example?
Instead of redeclaring bsdd:MinInclusive, you can use the existing xsd:minInclusive. I also don't know the mechanics by which this precisely works, but I see this in OWL examples all the time, e.g: http://drobilla.net/2012/09/08/how-to-define-a-datatype-in-rdf.html
<http://example.org/AnswerishInteger>
a rdfs:Datatype ;
rdfs:comment "An integer between 24 and 42 inclusive" ;
owl:onDatatype xsd:integer ;
owl:withRestrictions (
[
xsd:minInclusive 24
] [
xsd:maxInclusive 42
]
) .
Looks like can use this one. Or add a predicate saying that bsdd:Description is same as rdfs:comment.
I also wasn't 100% sure on this. But yes, i'd say just use rdfs:comment
when you serialize the data.
from bsdd.
Also see https://bsdd.ontotext.com/new/ in particular https://bsdd.ontotext.com/new/#suggested-improvements (Artur is working on a lot of these suggestions).
I wouldn't dare use xsd:minInclusive
etc because these are used on datatypes, whereas bsdd:Property
is a class.
I even wouldn't dare map bsdd:dataType
to XSD datatypes because
- it can map not only to literals, but also to objects (enumerated values:
PropertyValue
) bsdd:propertyValueKind
RANGE has no analog in XSD
from bsdd.
Related Issues (20)
- GET method to retriev all properties of a domain. HOT 7
- get API for the test domain HOT 3
- Classification DocumentReference HOT 1
- IFC attributes HOT 5
- Fraction HOT 3
- the system does not authorize my graphql query HOT 2
- Import model version HOT 2
- Link is not working HOT 1
- Materials vs Classifications HOT 1
- Provide JSON Schema for bsdd
- Wrong encoding in RDF/XML HOT 1
- [RDF/XML] Improve namespace declarations HOT 2
- Property status value change HOT 3
- "Old" domain URI leads to error 400 for endpoint api/Domain/v*/Classifications HOT 1
- Unexpected namespaceUri property on ClassificationPropertyContract.v4 HOT 4
- Material Properties HOT 2
- More documentation on "Property inheritance" (file bSDD JSON import model.md) HOT 1
- Dynamic properties HOT 1
- How to distinguish between psets and qtos? HOT 7
- Workaround for special characters HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bsdd.