- From: Ivan Herman <ivan@w3.org>
- Date: Wed, 11 Mar 2020 07:33:05 +0100
- To: James Hudson <jameshudson3010@gmail.com>
- Cc: Linked JSON <public-linked-json@w3.org>
- Message-ID: <ad284b28482714164a2d9e785955a1f2@w3.org>
James, as you correctly said, this isn't a json ld issue. json ld is just syntax, what you describe is an issue of defining the right vocabulary. Value constraints is a standard in OWL(1). OWL ontologies can be expressed in RDF (though there are alternatives) ie, in any RDF syntax ie, in json ld. However. To _check_ deployed data involves then what is called OWL reasoners, which are fairly compex pieces of software. This is why schema.org introduced its own, possibly simpler though less rich versions the can be checked with a scema.org processors. I am not a great expert of the schema.org vocabulary; I think you should their mailing list to get more details. Cheers, Ivan (1) https://www.w3.org/TR/2012/REC-owl2-overview-20121211/ --- Ivan Herman, W3C Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704 On 2020-03-09 21:16, James Hudson wrote: > Hello, > Since people have been tolerant of my trivial questions so far, I thought I would try another. > > I am not certain this necessarily a json-ld question...and if not, I will go elsewhere for help. > > I have been using schema.org [1] as a good(?) example of how to define a vocabulary as I think about my own. > > Let's say that I have a property that is required to be a value between 0 and 100 because it expressed a percentage of a total. How might I express this in my dictionary? I see that schema.org [1] defines https://schema.org/QuantitativeValue which has minValue and maxValue properties, but I don't see an example. If I were to guess, I would guess that I would subclass from QuantitativeValue and then define my term where the maxValue and minValue are fixed numbers. > > My second (and somewhat related) question is how to handle the notion of a "required" property. I see https://schema.org/domainIncludes which allows one to define on which terms a property is used. Imagine I would need to extend the definition of domainIncludes a bit to have a property called "required" which would be either true or false and have an implied default of false. > > Does any of this sound right? > > Regards, > James Links: ------ [1] http://schema.org
Received on Wednesday, 11 March 2020 06:33:07 UTC