[DDI-SRG] DDI Profile for applications

[Wendy Thomas]

put it in as a documentation bug. Keeping in mind that this is the 
official documentation and that there are separate best practices. 
However, it could probably do with a bit of expansion.

wlt


On Wed, 7 Jan 2009, Pascal Heus wrote:

> Wendy:
> looked at the doc and we could probably provide more details/example. We
> could also distinguish between agency/institutional profiles (like DDI
> Core which describe element collection for ingestion or publication) and
> application profiles (not agency specific, work on subset/superset)
> (like my concept editor requires a ConceptScheme and nothing else). A
> few examples would be helpful.
> *P
>
> Wendy Thomas wrote:
>> I'd like to capture as a documentation bug if it really is one. See
>> the content in DDI 3.0 Part II User Guide section 2.9 lines 766-793 to
>> see if this is captured sufficiently before filing a bug.
>>
>> wendy
>>
>>
>> On Wed, 7 Jan 2009, arofan.gregory wrote:
>>
>>> Pascal:
>>>
>>> This was the original intent of profiles, at least in part - I don't
>>> think
>>> we need to file a bug on this. I don't think this drives any changes
>>> to the
>>> schemas at all (unless we find that we missed something when we did the
>>> original design).
>>>
>>> Cheers,
>>>
>>> Arofan
>>>
>>> -----Original Message-----
>>> From: ddi-srg-bounces at icpsr.umich.edu
>>> [mailto:ddi-srg-bounces at icpsr.umich.edu] On Behalf Of Pascal Heus
>>> Sent: Wednesday, January 07, 2009 8:15 AM
>>> To: DDI Structural Reform Working Group.
>>> Subject: [DDI-SRG] DDI Profile for applications
>>>
>>> All:
>>> This is just an idea regarding DDI Profile but I'm thinking that
>>> profiles could also be used by application to describe the set of DDI 3
>>> elements they can consume/process or to accompany instances they
>>> produce. This could be useful when you need for example submit DDI to a
>>> service or a tools and need to prepare your metadata ((this becomes a
>>> bit the equivalent oa WSDL for DDI), to know what is the potential
>>> content to the tool output as you may want to further process it, or
>>> possibly for application to application metadata exchange. I don't think
>>> this has a direct impact on the schema (though we may come up with
>>> additional elements/attributes for machine processing), this idea could
>>> simply be integrated in the documentation. Will also file this in
>>> Mantis.
>>> best
>>> *P
>>>
>>> _______________________________________________
>>> DDI-SRG mailing list
>>> DDI-SRG at icpsr.umich.edu
>>> http://www.icpsr.umich.edu/mailman/listinfo/ddi-srg
>>>
>>> _______________________________________________
>>> DDI-SRG mailing list
>>> DDI-SRG at icpsr.umich.edu
>>> http://www.icpsr.umich.edu/mailman/listinfo/ddi-srg
>>>
>>
>> Wendy L. Thomas                          Phone: +1 612.624.4389
>> Data Access Core Director         Fax:   +1 612.626.8375
>> Minnesota Population Center              Email: wlt at pop.umn.edu
>> University of Minnesota
>> 50 Willey Hall
>> 225 19th Avenue South
>> Minneapolis, MN 55455
>>
>

Wendy L. Thomas                          Phone: +1 612.624.4389
Data Access Core Director		 Fax:   +1 612.626.8375
Minnesota Population Center              Email: wlt at pop.umn.edu
University of Minnesota
50 Willey Hall
225 19th Avenue South
Minneapolis, MN 55455