-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Label for the organization that has the logo #1639
Comments
What would the id and type be?
|
And just to open a can of worms should the id be: https://www.wikidata.org/wiki/Q23308 or https://viaf.org/viaf/121814978/ as then you could plot the owners on a map and get translations... |
I think we should require |
What are the risks if we are opinionated about the
I think we should at least say the |
Community call of 2018-08-01: Big change, but one that has value. If we want to do it, now is the time to do it. We've lost something with attribution and this re-establishes the connection to the organizations. Accessibility is a big use case as well. Important for discovery and aggregations of manifests across organizations. Rather solve it here than externally in discovery or completely outside of IIIF. +1s all round to the general idea. Need a concrete proposal with guidance. |
Regarding the name for this property is it similar to |
Seems like a useful proposal and allowing multiple occurrences of this element would be good for shared attribution scenarios such as an exhibition being planned by multiple institutions. |
Warning, Semantics Overload FollowsPredicate Re
The example shows that it's a project that collects data from institutions and then delivers it to Europeana. I think we want something more like
However It's close to
It doesn't say how it's made available. It could be digitally, or physically. It could be schema:provider:
(It has a domain of CreativeWork, which is sufficiently vague to be the Manifest or the object it represents) Or schema:publisher, with the exceedingly bland definition:
Of those ... I like Class We can either have a consistent The most common case will be Organization. Indeed the definition of Or we can trust that if a system knows it's a Person, that they'll be able to put that in to the data. Systems that don't know will normally not be wrong if they naively put Organization. My preference is to use the two schema classes, with a note that Organization is what will be used the vast majority of the time, and that clients likely don't even need to check the Example To fill out Tom's example from the comment above...
|
Eds call: Discuss on Discovery call, then air solution on next week's tech call. Should just use |
Sorry it took so much time to be available for this very interesting discussion. Now on the semantics overload... In fact I'd argue that My two cents on other proposals
|
Approval on technical community call of 2018-09-26. |
Closed by #1699 |
Approved by TRC, already merged into |
The Presentation API has a
logo
property, with the definition in 2.1:And almost identical in 3.0.
So there is the capability to associate a logo of an actor, but not even a label for the actor that has the logo. The label of the logo would be "Logo of X" not just "X". The attribution/requiredStatement might not be for the institution that has the logo, e.g. the requiredStatement could say "Purchased with the generous donation of J Smith." whereas the logo is for the museum. Further, the cardinality of logo is 1-many, from the discussion in #664. Even if there were multiple institutionLabels and multiple logos, you still couldn't link them together.
The logo is at the same level of presentation as
summary
andthumbnail
-- when the manifest is being summarized in a list, such as a Collection or a search results list. This is implemented in Mirador (for example) in the "loading window" via a method that's not based on the specifications. It is useful in any context when the resource is used outside of the responsible institution's context. This would include any search/discovery environment, of which the Mirador load window is a preconfigured microcosm.Given that the only use of
logo
can be for an institution, it seems a very small step to actually instantiate the identity of that institution in the data.This is the right time to discuss, as it would be a breaking change for both Presentation and Image. It does not add significant complexity, while solving several use cases from discovery and adding accessibility to the intended use of the existing
logo
property. The requirement came up in the Discovery TSG on 2018-07-11 with several use cases being described.Proposal (from Rob, not Discovery TSG):
Where ever we currently use
logo
, instead replace with a property that references a Person or Organization, which in turn hasid
,type
,label
, andlogo
. It would have the same semantics aslogo
does currently -- an individual or organization associated with the resource.The text was updated successfully, but these errors were encountered: