Hey Thad,
interesting question. Maybe P400 (platform) might work? This is mostly
used for things like 'Playstation 4' or 'iOS', but i think processor
architecture could be valid there as well.

Kind regards,
-- Hay

On Sat, Apr 25, 2020 at 12:11 AM Thad Guidry <[email protected]> wrote:
>
> With application Q166142
>
> I ran into a mapping problem again with Schema.org where we have a nice 
> Property already called https://schema.org/processorRequirements that allows 
> listing the ISA (instruction set architecture) that some applications are 
> designed for and require in order to run. (This happened a lot historically 
> when the world wasn't limited to a handful of ISA's beyond Intel-based and 
> ARM-based :-) )
>
> Anyways...
>
> As you can see on  application Q166142 where I tried to overload through 
> properties for this type P1963 the use of the existing instruction set P1068 
> which doesn't quite work, since an application is not a class of electronic 
> circuit or instruction set architecture.
>
> I could not find an appropriate Property already existing in a predicate form.
> Such as "requires ISA" or "requires instruction set" or even better and more 
> generally "depends on hardware" since we seem to already have a depends on 
> software Property and this could be the reverse to state that some Thing has 
> a hardware dependency or requires some kind of hardware ?
>
> I'd love some help in searching if something like this already exists, or if 
> that kind of Property was proposed before. (I sincerely tried and dug around 
> for over 2 hours)
>
> I could thus properly map and connect a few more dots to Schema.org's 
> property and other Linked Open Vocabularies.
>
> Thad
> https://www.linkedin.com/in/thadguidry/
> _______________________________________________
> Wikidata mailing list
> [email protected]
> https://lists.wikimedia.org/mailman/listinfo/wikidata

_______________________________________________
Wikidata mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata

Reply via email to