- From: Anthony Moretti <anthony.moretti@gmail.com>
- Date: Mon, 18 Jun 2018 22:07:54 -0700
- To: Thad Guidry <thadguidry@gmail.com>
- Cc: Michael Andrews <nextcontent01@gmail.com>, public-schemaorg@w3.org
- Message-ID: <CACusdfSz8NjfJ4oSUnBteu2Vwet2mE0-45sepfCkStY5rHwvBQ@mail.gmail.com>
Webfeet, yeah you have the first parts pretty much right, but maybe the inheritance part not as much though. It's tricky stuff, I'll give you an example. *Individual iPhones* and *iPhone types*: *Thing* * MobilePhone* * Smartphone* * iPhone* * iPhone7* * iPhone8* * iPhoneX* iPhoneX (serial number 00000001) iPhoneX (serial number 00000002) iPhoneX (serial number 00000003) * ThingType* * MobilePhoneType* * SmartphoneType* * iPhoneType* iPhone 7 iPhone 8 iPhone X Example description of an *individual iPhone*: iPhoneX (serial number 00000001) serialNumber: 00000001 height: 5.651 inches width: 2.789 inches depth: 0.299 inches weight: 6.139 ounces purchaseDate: Jun 18, 2018 owner: Anthony Moretti Example description of an *iPhone type*: iPhoneX heightOfTypicalInstances: 5.65 inches widthOfTypicalInstances: 2.79 inches depthOfTypicalInstances: 0.3 inches weightOfTypicalInstances: 6.14 ounces Having types always exist in pairs, like iPhone existing with iPhoneType, creates a pattern, and patterns can potentially help understanding. I took the following definitions from Apple, maybe they help explain what's going on too: - *Instance properties*: Properties belonging to an instance of a particular type. - *Type properties*: Properties that define values universal to all instances of a particular type. >From https://docs.swift.org/swift-book/LanguageGuide/Properties.html#ID264 Anthony On Mon, Jun 18, 2018 at 8:45 PM Thad Guidry <thadguidry@gmail.com> wrote: > Sounds Great Michael ! And thanks for sticking with us and helping > improve users understanding...its a long term effort, I know, but we are > all in this together and just having these notes from you helps understand > areas we need to improve. > > Looking forward to our Slack conversations with you and the community ! > (it'll probably blow up on the first day! lololol) > -Thad > > On Mon, Jun 18, 2018 at 10:23 PM Michael Andrews <nextcontent01@gmail.com> > wrote: > >> I’ve jotted down a number of questions I have about schema.org, based on >> reading existing documentation. They involve too much detail to discuss >> in an email thread, so I will save them for the Slack channel when it is >> operational. >> >> >> However, I will preview some of the themes in my questions. >> >> >> * Which to use (when two entities or properties seem similar) >> >> * When to use (especially for intangible entities) >> >> * How to use (especially for intangible entities) >> >> * Clarifying the intention of an entity (when the definition is not >> completely aligned with properties) >> >> * Cases of terminology that can be misunderstood >> >> * Cases of unclear definitions >> >> * Inheritance in entities, and in properties, and clarifying whether >> different statements are equivalent or not >> >> * Cases of low adoption of seemingly widely applicable terms >> >> * Scope disambiguation of conceptually related terms >> >> * Clarifying intended use of Action entities >> >> * Guidance on preferred course of action when schema.org does not cover >> specific entity or property needed >> >> >>
Received on Tuesday, 19 June 2018 05:08:31 UTC