Print

Print


Hi all,

the comment of Rodolphe give me the opportunity of arising a question
I'm thinking about since long time now:

Why we have a type "video" and not a type  "multimedia"?

if we have only video then we should allow a max number of occurrences
larger than 1 as we can have a video with sound (movie), or sound with
a video composed by only an image or just a text or video without
sound (if we just select VIDEO).

Inserting a multimedia type will solve this problem as "multimedia" is
by definition composed by multiple media (a movie is composed by video
+ sound )

Best regards,
Denis

On 6 April 2011 17:01, Rodolphe Bailly <[log in to unmask]> wrote:
> Hi all,
>
> I'm having a hard time with:
> ____________________________________________________________
>
> ens:type | literal (TEXT-VIDEO-SOUND-IMAGE) | min 1, max 1
> ____________________________________________________________
>
> which is now a property of ens:ProvidedCHO
>
> How to proceed with physical objects coming with more than one "digital
> representation", and more than one type of resource ( images, audio and
> video ) ?
>
> I know this element just moved from ens:Aggregation, following comments by
> Go, but I would expect to see it as a property of ens:WebResource ?
>
> Best,
>
> Rodolphe
>
>
>
> -----Message d'origine-----
> De : Discussion list for Europeana WP3 participants
> [mailto:[log in to unmask]] De la part de
> Antoine Isaac
> Envoyé : mercredi 6 avril 2011 11:26
> À : [log in to unmask]
> Objet : Re: Separating between provider's focus and Europeana focus for EDM
> ingestion
>
> PS: note that in attempt for making stuff more practical for providers, and
> also to prepare for XML schema and object models where types have to be
> given to all resources, we've assigned a new "ens:ProvidedObject" type to
> the "central node" in the EDM "triangle".
> As mentioned last week, we can't be sure that ens:PhysicalThing can apply to
> every case (especially for the cases where the physical nature of the object
> would be debatable). So we have to come with something that just captures
> the *function*.
> It does not change much to the graph structure--it's just a matter of adding
> an additional type. But it should be added to the next EDM version, if
> that's alright.
>
> Antoine
>
>
>
>> Dear all,
>>
>> A follow-up on the discussions we had last week, in the work we're doing
> at the Office trying to populate EDM templates.
>> The basic idea is to make the work easier for providers who don't have to
> manage the data provenance requirements that Europeana has to meet. For such
> providers, all descriptive metadata on objects comes from their space, and
> hence they don't need proxies.
>>
>> http://europeanalabs.eu/wiki/EDMXMLSchema thus now gives access to two
> pages:
>> - http://europeanalabs.eu/wiki/EDMObjectTemplatesProviders
>> - http://europeanalabs.eu/wiki/EDMObjectTemplatesEuropeana
>>
>> Feedback welcome!
>> In the same line, in the next week we would work on making the Primer
> reflect that, as Herbert suggested. Mostly, streamlining most of the
> examples and making proxies disappear from the beginning of the document...
>>
>> Best,
>>
>> Antoine
>>
>>
>>> Hi everyone,
>>>
>>> I will mention it at the meeting in Vienna next week, but in case some of
> you are interested in more details, here are links to recent progresses made
> at the Office for the Danube programme (beyond the ESE-EDM stuff for linked
> data that I've circulated last week):
>>>
>> [...]
>>> - identification by the Operations team of properties that apply to the
> different main EDM classes, so as to prepare programming work by our
> technical team (and which can be used for XML schema creation). This is
> based on the EDM specs you know already--notably formal and informal domain
> and ranges assignments.
>>> It also tries to fill some gaps re. the contextual entity classes for
> which little "profiling information" came out of our work in WP3. The aim is
> clearly not to be exhaustive. Rather, we cherry-picked elements from
> available ontologies, so that Europeana can later ingest (and exploit) a
> "core" for each of these types.
>>> See http://europeanalabs.eu/wiki/EDMXMLSchema
>>>
>>> Best,
>>>
>>> Antoine
>>>
>
>



-- 
----------------------
VAST 2011 - http://www.vast-conference.eu

Denis Pitzalis - http://www.pitzalis.org
Researcher in Digital Heritage and Archaeological Sciences

The Cyprus Institute, STARC - http://www.cyi.ac.cy
Guy Ourisson Bld, Nicosia, Cyprus - Tel: +35722208653

Centre de Recherche et de Restauration des Musées de France (C2RMF) -
http://www.c2rmf.fr
Palais du Louvre, Paris, France - Tel: +33140202414

3DCoForm - Tools and Expertise for 3D Collection Formation -
http://www.3dcoform.eu
Business Strand Coordinator