Re: Thing properties

Good morning Dan,

I think some diagrams would definitely help.

The Zen of Python.

/Explicit is better than implicit./

https://www.python.org/dev/peps/pep-0020/ 
<https://www.python.org/dev/peps/pep-0020/>


Yours sincerely,
Hans Polak

On 5/11/21 10:54, Dan Brickley wrote:
>
> Yes! In fact this piece of knowledge is the key to being able to read 
> Schema.org markup in json-ld, rdf, microdata, ... Or even in other W3C 
> RDF settings like RDF/XML, SPARQL (for querying),  Turtle, N-Triples, 
> N-Quads, SHACL, ShEx etc etc.
>
> In any of these when you see an initial lowercase letter beginning a 
> term, it will be a property term.
>
> If it begins uppercase, the majority of cases it will be a type (aka 
> class). However it might also be an enumerated value, i.e. an instance 
> of the Enumeration type.
>
> This convention is also followed in most other RDF schemas too.
>
> As for our breadcrumbs punctuation, "::" is a poor choice of mine. It 
> looks too much like something from the C++ programming language (
> https://www.geeksforgeeks.org/scope-resolution-operator-in-c/ 
> <https://www.geeksforgeeks.org/scope-resolution-operator-in-c/> ).
>
> Essentially what we want to communicate in the site navigation 
> structure is the kind of term (property, type or value), alongside a 
> summary of where it fits in the corresponding hierarchies (supertypes, 
> superproperties).
>
> I wonder whether introducing a few diagrams in our docs like used in 
> https://www.w3.org/TR/NOTE-MCF-XML/MCF-tutorial.html 
> <https://www.w3.org/TR/NOTE-MCF-XML/MCF-tutorial.html> would help 
> communicate the underlying approach to data modeling?
>
> Dan
> On Fri, 24 Sept 2021, 23:04 Micah McG, <mcglabs@gmail.com 
> <mailto:mcglabs@gmail.com>> wrote:
>
>     All properties start with lowercase letters, and all properties
>     will resolve to the Property class. I reason the breadcrumb with
>     the :: operator indicates scope, not class lineage.
>
>
>
>     On Fri, Sep 24, 2021 at 2:39 AM Omar Holzknecht
>     <omar.holzknecht@onlim.com <mailto:omar.holzknecht@onlim.com>> wrote:
>
>         Hallo Bob,
>
>
>         Used on these types
>         |Permit <https://schema.org/Permit>|
>
>         "validUntil" is a property of "Permit", not of "Thing".
>
>         Thing <https://schema.org/Thing>>Property
>         <https://schema.org/Property>::validUntil
>         <https://schema.org/validUntil>
>
>         The breadcrumb under the title tells that "validUntil" is an
>         instance of "Property" which is a Sub-class of "Thing".
>
>
>         Sinc. Omar
>
>
>         On 23.09.21 11:43, Bob Coret wrote:
>>         Hi,
>>
>>         I see on https://schema.org/validUntil
>>         <https://schema.org/validUntil> that validUntil is property
>>         of Thing (this is the case for more properties). But on
>>         https://schema.org/Thing <https://schema.org/Thing> I don't
>>         see this property listed?
>>
>>         Is this a deliberate choice to not list all Thing properties?
>>         And, is it valid to use such a property on any subclass of Thing?
>>
>>         Bob Coret
>