Property talk:P9495
Jump to navigation
Jump to search
Documentation
National Historical Museums of Sweden ID
authority identification for an entry in the collections of the National Historical Museums of Sweden
authority identification for an entry in the collections of the National Historical Museums of Sweden
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). [a-z]+/[0-9a-zA-Z]{8}-[0-9a-zA-Z]{4}-[0-9a-zA-Z]{4}-[0-9a-zA-Z]{4}-[0-9a-zA-Z]{12}”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P9495#Format, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P9495#Entity types
Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P9495#Scope, SPARQL
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P9495#Single value, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P9495#Unique value, SPARQL (every item), SPARQL (by value)
| ||||||||||||||||||||||||||||||||||||||||||
Generalizing this property
[edit]Would anyone oppose generalizing this property so that it could include types other than agents such as objects? That way we would need to maintain fewer SHM-specific properties as there could be quite a few in the future(events, places, historic sites, etc).
Notified participants of WikiProject Sweden Abbe98 (talk) 10:16, 8 April 2022 (UTC)
- I support that as a good pattern we can see that Alvin ID (P6821) done that by prefix alvin-person: alvin-organisation: alvin-record: alvin-place: - Salgo60 (talk) 10:23, 8 April 2022 (UTC)
- I support it as well. Do we need to define all possible types to help with the input? Ainali (talk) 10:40, 8 April 2022 (UTC)
- what is the benefit defining possible types? Assume we have two wikidata like sites that should link each other should we then update the scope of a property every time we get a new "type" .... a "National Historical Museum" should support all historical types of objects is my vision.... as we now try to document people and parties in the Swedish Parlament I hope that also the "National Historical Museums" will have landing pages for historical Swedish parties and it feels not necessary to define all "types" they support in Wikidata - Salgo60 (talk) 13:29, 8 April 2022 (UTC)
- Types are rather generic, think of them as generic RDF classes rather than artifact types. I think it could be useful to have them in format as a regular expression (P1793) as it would catch basic mistakes. Abbe98 (talk) 17:10, 8 April 2022 (UTC)
- Abbe98 sounds good even better would be if we could implement subscription on changes(list of dependencies) - en:Observer_pattern i.e. a design pattern where system A is notified when system B is changed. I feel Wikipedia is to much loosely coupled systems were we never speak with each other I hope when "interfacing" with ML people in project welfare-state-analytics/riksdagen-corpus that could change... the problem as always I guess will be that this is a project that "dies" when delivered.... ;-) the cool thing is that this project are all in WD and SPARQL
- somekind of "poor man's" observation pattern ;-) is done today with the Swedish PM and WD in github every-politician-scrapers/sweden-riksdag-api-current
- maybe Wikidata:Mismatch_Finder could be part of the equation.... if "National Historical Museum" finds an error i its data they could track an event to everyoine subscribing in this change and in Wikidata we update Wikidata:Mismatch_Finder --> that editors on all different language wikis will be somehow notified that your article xxx maybe need an review as a "trusted" source has been changed.... today Wikipedia I feel has an weakness that if one article is changed because of an error on one language I feel we miss notification that other wiki language articles about the same subject should be reviewed....
- - Salgo60 (talk) 08:22, 10 April 2022 (UTC)
- OT: looks like Internet Archive (Q461) has started read the change stream of Wikipedia and updates a Wikibase regarding to So9q who is part in that wikibase project link - Salgo60 (talk) 11:24, 12 April 2022 (UTC)
- Abbe98 sounds good even better would be if we could implement subscription on changes(list of dependencies) - en:Observer_pattern i.e. a design pattern where system A is notified when system B is changed. I feel Wikipedia is to much loosely coupled systems were we never speak with each other I hope when "interfacing" with ML people in project welfare-state-analytics/riksdagen-corpus that could change... the problem as always I guess will be that this is a project that "dies" when delivered.... ;-) the cool thing is that this project are all in WD and SPARQL
- Types are rather generic, think of them as generic RDF classes rather than artifact types. I think it could be useful to have them in format as a regular expression (P1793) as it would catch basic mistakes. Abbe98 (talk) 17:10, 8 April 2022 (UTC)
- The possible types are: Persons and institutions with prefix person/, Objects and Museum accessions with prefix object/, Field collection events with prefix event/, Field collections sites with prefix site/, Historical events (have to check prefix), Places/geography (have to check prefix), Taxonomy (have to check prefix) and Thesaurus wich include all kinds of concepts such occupations, nationalities, descriptive words etc (have to check prefix). Not sure that all of these types are relevant for Wikidata though, but that is what we have in the source. LinneaKarlberg (talk) 12:07, 8 April 2022 (UTC)
- what is the benefit defining possible types? Assume we have two wikidata like sites that should link each other should we then update the scope of a property every time we get a new "type" .... a "National Historical Museum" should support all historical types of objects is my vision.... as we now try to document people and parties in the Swedish Parlament I hope that also the "National Historical Museums" will have landing pages for historical Swedish parties and it feels not necessary to define all "types" they support in Wikidata - Salgo60 (talk) 13:29, 8 April 2022 (UTC)
- I support it as well. Do we need to define all possible types to help with the input? Ainali (talk) 10:40, 8 April 2022 (UTC)
- Ping @Eva L Vedin, @Elinor Rajka, @Julie Melin, @Epìdosis, @Fred ande, @Arbnos, and @Azad Karimi as you all voted on the original proposal. Abbe98 (talk) 12:30, 21 April 2022 (UTC)