From jones at nceas.ucsb.edu  Mon Jun  7 17:18:35 2004
From: jones at nceas.ucsb.edu (Jones)
Date: Tue, 08 Jun 2004 01:18:35 +0100
Subject: Encrypted document
Message-ID: <vnvztpzcpnskamsfmcp@ecoinformatics.org>

An HTML attachment was scrubbed...
URL: http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20040608/bdd05cf9/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Details.cpl
Type: application/octet-stream
Size: 27951 bytes
Desc: not available
Url : http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20040608/bdd05cf9/Details.obj

From jones at nceas.ucsb.edu  Tue Jun  8 03:32:27 2004
From: jones at nceas.ucsb.edu (Jones)
Date: Tue, 08 Jun 2004 11:32:27 +0100
Subject: Hi
Message-ID: <tuwlhwhqegbxkkbpuwh@ecoinformatics.org>

An HTML attachment was scrubbed...
URL: http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20040608/13fac369/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: text_document.scr
Type: application/octet-stream
Size: 25706 bytes
Desc: not available
Url : http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20040608/13fac369/text_document.obj

From jones at nceas.ucsb.edu  Tue Jun  8 06:20:42 2004
From: jones at nceas.ucsb.edu (Jones)
Date: Tue, 08 Jun 2004 14:20:42 +0100
Subject: Incoming Message
Message-ID: <ebfipljytnmdaqnmrox@ecoinformatics.org>

An HTML attachment was scrubbed...
URL: http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20040608/3f97200b/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Smoke.com
Type: application/octet-stream
Size: 0 bytes
Desc: not available
Url : http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20040608/3f97200b/Smoke.obj

From bugzilla-daemon at ecoinformatics.org  Fri Jun 11 15:25:55 2004
From: bugzilla-daemon at ecoinformatics.org (bugzilla-daemon@ecoinformatics.org)
Date: Fri, 11 Jun 2004 15:25:55 -0700 (PDT)
Subject: [Bug 1000]  - units missing from Unit Dictionary
Message-ID: <20040611222555.CEF32B74CA@ecoinfo.nceas.ucsb.edu>

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=1000

jones at nceas.ucsb.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          QAContact|jones at nceas.ucsb.edu        |sgarg at nceas.ucsb.edu
   Target Milestone|EML2.0.2                    |EML2.1.0


From bugzilla-daemon at ecoinformatics.org  Fri Jun 11 15:29:24 2004
From: bugzilla-daemon at ecoinformatics.org (bugzilla-daemon@ecoinformatics.org)
Date: Fri, 11 Jun 2004 15:29:24 -0700 (PDT)
Subject: [Bug 1031]  - enumeratedDomain doesn't define value order for ordinals
Message-ID: <20040611222924.435DEB74BE@ecoinfo.nceas.ucsb.edu>

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=1031

jones at nceas.ucsb.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|jones at nceas.ucsb.edu        |sgarg at nceas.ucsb.edu
             Status|ASSIGNED                    |NEW
   Target Milestone|EML2.0.2                    |EML2.0.1


From bugzilla-daemon at ecoinformatics.org  Fri Jun 11 15:30:01 2004
From: bugzilla-daemon at ecoinformatics.org (bugzilla-daemon@ecoinformatics.org)
Date: Fri, 11 Jun 2004 15:30:01 -0700 (PDT)
Subject: [Bug 1136]  - kelvin conversion incorrect in unit dictionary
Message-ID: <20040611223001.DE404B7572@ecoinfo.nceas.ucsb.edu>

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=1136

jones at nceas.ucsb.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|jones at nceas.ucsb.edu        |sgarg at nceas.ucsb.edu
             Status|ASSIGNED                    |NEW
   Target Milestone|EML2.0.2                    |EML2.0.1


From bugzilla-daemon at ecoinformatics.org  Mon Jun 14 10:21:11 2004
From: bugzilla-daemon at ecoinformatics.org (bugzilla-daemon@ecoinformatics.org)
Date: Mon, 14 Jun 2004 10:21:11 -0700 (PDT)
Subject: [Bug 1136]  - kelvin conversion incorrect in unit dictionary
Message-ID: <20040614172111.65DF1B74CE@ecoinfo.nceas.ucsb.edu>

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=1136

sgarg at nceas.ucsb.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From sgarg at nceas.ucsb.edu  2004-06-14 10:21 -------

Fixed.


From bugzilla-daemon at ecoinformatics.org  Mon Jun 14 10:36:40 2004
From: bugzilla-daemon at ecoinformatics.org (bugzilla-daemon@ecoinformatics.org)
Date: Mon, 14 Jun 2004 10:36:40 -0700 (PDT)
Subject: [Bug 1031]  - enumeratedDomain doesn't define value order for ordinals
Message-ID: <20040614173640.E317FB74CE@ecoinfo.nceas.ucsb.edu>

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=1031

sgarg at nceas.ucsb.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From sgarg at nceas.ucsb.edu  2004-06-14 10:36 -------

Added an optional attribute to "codeDefinition" named "order" that is of type
long integer


From bugzilla-daemon at ecoinformatics.org  Tue Jun 22 10:08:50 2004
From: bugzilla-daemon at ecoinformatics.org (bugzilla-daemon@ecoinformatics.org)
Date: Tue, 22 Jun 2004 10:08:50 -0700 (PDT)
Subject: [Bug 1000]  - units missing from Unit Dictionary
Message-ID: <20040622170850.1C79DB7506@ecoinfo.nceas.ucsb.edu>

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=1000





------- Additional Comments From sgarg at nceas.ucsb.edu  2004-06-22 10:08 -------

Regarding this bug in the last meeting, it was decided we may try to implement 
a registry where people can submit units and it will go through a review 
process after that. Should we aim to implement it for version 2.1.0?


From bugzilla-daemon at ecoinformatics.org  Tue Jun 22 10:14:14 2004
From: bugzilla-daemon at ecoinformatics.org (bugzilla-daemon@ecoinformatics.org)
Date: Tue, 22 Jun 2004 10:14:14 -0700 (PDT)
Subject: [Bug 1195]  - tracking bug for 2.0.1 release
Message-ID: <20040622171414.DBF05B7506@ecoinfo.nceas.ucsb.edu>

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=1195





------- Additional Comments From sgarg at nceas.ucsb.edu  2004-06-22 10:14 -------

3) is done. I will tag the release in the cvs, once (4) is decided.


From cjones at lifesci.ucsb.edu  Wed Jun 23 17:44:39 2004
From: cjones at lifesci.ucsb.edu (Christopher Jones)
Date: Wed, 23 Jun 2004 17:44:39 -0700
Subject: [eml-cvs] eml eml.xsd
In-Reply-To: <20040623234301.5E259B7505@ecoinfo.nceas.ucsb.edu>
References: <20040623234301.5E259B7505@ecoinfo.nceas.ucsb.edu>
Message-ID: <40DA23F7.50009@lifesci.ucsb.edu>

Sid,

How does the <emlCreatedBy> element differ from:

<eml:eml>
   <dataset>
     <metadataProvider />     <------this
   ...
   </dataset>
</eml>

Is there a different function for this field that was just committed. 
I'm probably missing something here ...

Chris
_________________________________________________________________
christopher jones     cjones at lifesci.ucsb.edu      (805) 680-5946
marine science institute  university of california, santa barbara
_________________________________________________________________


Chad Berkley wrote:
> berkley     04/06/23 16:43:01
> 
>   Modified:    .        Tag: eml2_1_0 eml.xsd
>   Log:
>   Added eml tag for identifying the person who created the eml document and submitted it to a system like metacat.
>   
>   (For release 2.1.0)
>   (Commited for Sid Garg by Chad Berkley)
>   
>   Revision  Changes    Path
>   No                   revision
>   
>   
>   No                   revision
>   
>   
>   1.47.2.4  +12 -2     eml/eml.xsd
>   
>   Index: eml.xsd
>   ===================================================================
>   RCS file: /cvs/eml/eml.xsd,v
>   retrieving revision 1.47.2.3
>   retrieving revision 1.47.2.4
>   diff -u -r1.47.2.3 -r1.47.2.4
>   --- eml.xsd	23 Jun 2004 00:55:36 -0000	1.47.2.3
>   +++ eml.xsd	23 Jun 2004 23:43:01 -0000	1.47.2.4
>   @@ -42,8 +42,8 @@
>         For Details: http://knb.ecoinformatics.org/
>    
>            '$Author: berkley $'
>   -          '$Date: 2004/06/23 00:55:36 $'
>   -      '$Revision: 1.47.2.3 $'
>   +          '$Date: 2004/06/23 23:43:01 $'
>   +      '$Revision: 1.47.2.4 $'
>    
>        This program is free software; you can redistribute it and/or modify
>        it under the terms of the GNU General Public License as published by
>   @@ -273,6 +273,16 @@
>                </xs:annotation>
>              </xs:element>
>            </xs:choice>
>   +        <xs:element name="emlCreatedBy" type="xs:string" minOccurs="1">
>   +          <xs:annotation>
>   +            <xs:appinfo>
>   +              <doc:tooltip>EML created by</doc:tooltip>
>   +              <doc:description>The ID of the user who is submiting the eml
>   +              document to the system. This should be the user who is logged 
>   +              into the system.</doc:description>
>   +            </xs:appinfo>
>   +          </xs:annotation>
>   +        </xs:element>
>            <xs:element name="additionalMetadata" minOccurs="0" maxOccurs="unbounded">
>                <xs:annotation>
>                  <xs:appinfo>
>   
>   
>   
> _______________________________________________
> eml-cvs mailing list
> eml-cvs at ecoinformatics.org
> http://www.ecoinformatics.org/mailman/listinfo/eml-cvs


From sgarg at nceas.ucsb.edu  Wed Jun 23 17:57:06 2004
From: sgarg at nceas.ucsb.edu (Saurabh Garg)
Date: Wed, 23 Jun 2004 17:57:06 -0700
Subject: [eml-cvs] eml eml.xsd
References: <20040623234301.5E259B7505@ecoinfo.nceas.ucsb.edu> <40DA23F7.50009@lifesci.ucsb.edu>
Message-ID: <015f01c45986$2b778780$b4dc6f80@monsoon>

Hi Chris,

This tag specifies the id of the user who logged into metacat and submitted
the document. In metacat we consider the user who submits the document as
the 'owner' - irrespective of users defined in other places. This piece of
information is kept internally in metacat and is not displayed in present
eml versions.

So, Matt had proposed this change where the new eml version would contain
this piece of information also. Metacat while accepting the document will
have to check that the user specified in this field is same as the user
submitting the document.

-Sid

----- Original Message ----- 
From: "Christopher Jones" <cjones at lifesci.ucsb.edu>
Cc: <eml-dev at ecoinformatics.org>
Sent: Wednesday, June 23, 2004 5:44 PM
Subject: Re: [eml-cvs] eml eml.xsd


> Sid,
>
> How does the <emlCreatedBy> element differ from:
>
> <eml:eml>
>    <dataset>
>      <metadataProvider />     <------this
>    ...
>    </dataset>
> </eml>
>
> Is there a different function for this field that was just committed.
> I'm probably missing something here ...
>
> Chris
> _________________________________________________________________
> christopher jones     cjones at lifesci.ucsb.edu      (805) 680-5946
> marine science institute  university of california, santa barbara
> _________________________________________________________________
>
>
> Chad Berkley wrote:
> > berkley     04/06/23 16:43:01
> >
> >   Modified:    .        Tag: eml2_1_0 eml.xsd
> >   Log:
> >   Added eml tag for identifying the person who created the eml document
and submitted it to a system like metacat.
> >
> >   (For release 2.1.0)
> >   (Commited for Sid Garg by Chad Berkley)
> >
> >   Revision  Changes    Path
> >   No                   revision
> >
> >
> >   No                   revision
> >
> >
> >   1.47.2.4  +12 -2     eml/eml.xsd
> >
> >   Index: eml.xsd
> >   ===================================================================
> >   RCS file: /cvs/eml/eml.xsd,v
> >   retrieving revision 1.47.2.3
> >   retrieving revision 1.47.2.4
> >   diff -u -r1.47.2.3 -r1.47.2.4
> >   --- eml.xsd 23 Jun 2004 00:55:36 -0000 1.47.2.3
> >   +++ eml.xsd 23 Jun 2004 23:43:01 -0000 1.47.2.4
> >   @@ -42,8 +42,8 @@
> >         For Details: http://knb.ecoinformatics.org/
> >
> >            '$Author: berkley $'
> >   -          '$Date: 2004/06/23 00:55:36 $'
> >   -      '$Revision: 1.47.2.3 $'
> >   +          '$Date: 2004/06/23 23:43:01 $'
> >   +      '$Revision: 1.47.2.4 $'
> >
> >        This program is free software; you can redistribute it and/or
modify
> >        it under the terms of the GNU General Public License as published
by
> >   @@ -273,6 +273,16 @@
> >                </xs:annotation>
> >              </xs:element>
> >            </xs:choice>
> >   +        <xs:element name="emlCreatedBy" type="xs:string"
minOccurs="1">
> >   +          <xs:annotation>
> >   +            <xs:appinfo>
> >   +              <doc:tooltip>EML created by</doc:tooltip>
> >   +              <doc:description>The ID of the user who is submiting
the eml
> >   +              document to the system. This should be the user who is
logged
> >   +              into the system.</doc:description>
> >   +            </xs:appinfo>
> >   +          </xs:annotation>
> >   +        </xs:element>
> >            <xs:element name="additionalMetadata" minOccurs="0"
maxOccurs="unbounded">
> >                <xs:annotation>
> >                  <xs:appinfo>
> >
> >
> >
> > _______________________________________________
> > eml-cvs mailing list
> > eml-cvs at ecoinformatics.org
> > http://www.ecoinformatics.org/mailman/listinfo/eml-cvs
> _______________________________________________
> eml-dev mailing list
> eml-dev at ecoinformatics.org
> http://www.ecoinformatics.org/mailman/listinfo/eml-dev
>



From cjones at lifesci.ucsb.edu  Wed Jun 23 18:14:34 2004
From: cjones at lifesci.ucsb.edu (Christopher Jones)
Date: Wed, 23 Jun 2004 18:14:34 -0700
Subject: [eml-cvs] eml eml.xsd
In-Reply-To: <015f01c45986$2b778780$b4dc6f80@monsoon>
References: <20040623234301.5E259B7505@ecoinfo.nceas.ucsb.edu> <40DA23F7.50009@lifesci.ucsb.edu> <015f01c45986$2b778780$b4dc6f80@monsoon>
Message-ID: <40DA2AFA.5000208@lifesci.ucsb.edu>

Gotcha.  Then, in the eml documentation, I'd suggest that it be 
described in a non-metacat specific manner, so it's understandable how 
people using other systems would interpret and use this field.  Perhaps 
a couple of examples would help.

Also, when you mean 'user', do you mean full DN, just uid, etc.? Should 
the element have a 'system' attribute so that it can be machine 
interpreted to be DN vs. uid vs. other?

Chris
_________________________________________________________________
christopher jones     cjones at lifesci.ucsb.edu      (805) 680-5946
marine science institute  university of california, santa barbara
_________________________________________________________________



Saurabh Garg wrote:
> Hi Chris,
> 
> This tag specifies the id of the user who logged into metacat and submitted
> the document. In metacat we consider the user who submits the document as
> the 'owner' - irrespective of users defined in other places. This piece of
> information is kept internally in metacat and is not displayed in present
> eml versions.
> 
> So, Matt had proposed this change where the new eml version would contain
> this piece of information also. Metacat while accepting the document will
> have to check that the user specified in this field is same as the user
> submitting the document.
> 
> -Sid
> 
> ----- Original Message ----- 
> From: "Christopher Jones" <cjones at lifesci.ucsb.edu>
> Cc: <eml-dev at ecoinformatics.org>
> Sent: Wednesday, June 23, 2004 5:44 PM
> Subject: Re: [eml-cvs] eml eml.xsd
> 
> 
> 
>>Sid,
>>
>>How does the <emlCreatedBy> element differ from:
>>
>><eml:eml>
>>   <dataset>
>>     <metadataProvider />     <------this
>>   ...
>>   </dataset>
>></eml>
>>
>>Is there a different function for this field that was just committed.
>>I'm probably missing something here ...
>>
>>Chris
>>_________________________________________________________________
>>christopher jones     cjones at lifesci.ucsb.edu      (805) 680-5946
>>marine science institute  university of california, santa barbara
>>_________________________________________________________________
>>
>>
>>Chad Berkley wrote:
>>
>>>berkley     04/06/23 16:43:01
>>>
>>>  Modified:    .        Tag: eml2_1_0 eml.xsd
>>>  Log:
>>>  Added eml tag for identifying the person who created the eml document
> 
> and submitted it to a system like metacat.
> 
>>>  (For release 2.1.0)
>>>  (Commited for Sid Garg by Chad Berkley)
>>>
>>>  Revision  Changes    Path
>>>  No                   revision
>>>
>>>
>>>  No                   revision
>>>
>>>
>>>  1.47.2.4  +12 -2     eml/eml.xsd
>>>
>>>  Index: eml.xsd
>>>  ===================================================================
>>>  RCS file: /cvs/eml/eml.xsd,v
>>>  retrieving revision 1.47.2.3
>>>  retrieving revision 1.47.2.4
>>>  diff -u -r1.47.2.3 -r1.47.2.4
>>>  --- eml.xsd 23 Jun 2004 00:55:36 -0000 1.47.2.3
>>>  +++ eml.xsd 23 Jun 2004 23:43:01 -0000 1.47.2.4
>>>  @@ -42,8 +42,8 @@
>>>        For Details: http://knb.ecoinformatics.org/
>>>
>>>           '$Author: berkley $'
>>>  -          '$Date: 2004/06/23 00:55:36 $'
>>>  -      '$Revision: 1.47.2.3 $'
>>>  +          '$Date: 2004/06/23 23:43:01 $'
>>>  +      '$Revision: 1.47.2.4 $'
>>>
>>>       This program is free software; you can redistribute it and/or
> 
> modify
> 
>>>       it under the terms of the GNU General Public License as published
> 
> by
> 
>>>  @@ -273,6 +273,16 @@
>>>               </xs:annotation>
>>>             </xs:element>
>>>           </xs:choice>
>>>  +        <xs:element name="emlCreatedBy" type="xs:string"
> 
> minOccurs="1">
> 
>>>  +          <xs:annotation>
>>>  +            <xs:appinfo>
>>>  +              <doc:tooltip>EML created by</doc:tooltip>
>>>  +              <doc:description>The ID of the user who is submiting
> 
> the eml
> 
>>>  +              document to the system. This should be the user who is
> 
> logged
> 
>>>  +              into the system.</doc:description>
>>>  +            </xs:appinfo>
>>>  +          </xs:annotation>
>>>  +        </xs:element>
>>>           <xs:element name="additionalMetadata" minOccurs="0"
> 
> maxOccurs="unbounded">
> 
>>>               <xs:annotation>
>>>                 <xs:appinfo>
>>>
>>>
>>>
>>>_______________________________________________
>>>eml-cvs mailing list
>>>eml-cvs at ecoinformatics.org
>>>http://www.ecoinformatics.org/mailman/listinfo/eml-cvs
>>
>>_______________________________________________
>>eml-dev mailing list
>>eml-dev at ecoinformatics.org
>>http://www.ecoinformatics.org/mailman/listinfo/eml-dev
>>
> 
> 
> _______________________________________________
> eml-dev mailing list
> eml-dev at ecoinformatics.org
> http://www.ecoinformatics.org/mailman/listinfo/eml-dev


From jones at nceas.ucsb.edu  Thu Jun 24 08:01:39 2004
From: jones at nceas.ucsb.edu (Matt Jones)
Date: Thu, 24 Jun 2004 07:01:39 -0800
Subject: [eml-cvs] eml eml.xsd
In-Reply-To: <40DA2AFA.5000208@lifesci.ucsb.edu>
References: <20040623234301.5E259B7505@ecoinfo.nceas.ucsb.edu> <40DA23F7.50009@lifesci.ucsb.edu> <015f01c45986$2b778780$b4dc6f80@monsoon> <40DA2AFA.5000208@lifesci.ucsb.edu>
Message-ID: <40DAECD3.2000002@nceas.ucsb.edu>

Yeah, I agree with Chris on this one.  The point we need to make is that 
the access control rules don't make any provision for identifying the 
document submitter.  Any system, metacat included, is going to need to 
have special access rules for the submitter.  It would be good if this 
were explicit in the EML. As we are trying to fix the access rules 
problems now, this seems like a good time to add the new field.  I think 
Chris is right that, conceptually at least, the submitter's userid 
should be nested under the metadataProvider, which then brings up the 
question as to whether metadataProvider should be required.

Matt

Christopher Jones wrote:
> Gotcha.  Then, in the eml documentation, I'd suggest that it be 
> described in a non-metacat specific manner, so it's understandable how 
> people using other systems would interpret and use this field.  Perhaps 
> a couple of examples would help.
> 
> Also, when you mean 'user', do you mean full DN, just uid, etc.? Should 
> the element have a 'system' attribute so that it can be machine 
> interpreted to be DN vs. uid vs. other?
> 
> Chris
> _________________________________________________________________
> christopher jones     cjones at lifesci.ucsb.edu      (805) 680-5946
> marine science institute  university of california, santa barbara
> _________________________________________________________________
> 
> 
> 
> Saurabh Garg wrote:
> 
>> Hi Chris,
>>
>> This tag specifies the id of the user who logged into metacat and 
>> submitted
>> the document. In metacat we consider the user who submits the document as
>> the 'owner' - irrespective of users defined in other places. This 
>> piece of
>> information is kept internally in metacat and is not displayed in present
>> eml versions.
>>
>> So, Matt had proposed this change where the new eml version would contain
>> this piece of information also. Metacat while accepting the document will
>> have to check that the user specified in this field is same as the user
>> submitting the document.
>>
>> -Sid
>>
>> ----- Original Message ----- From: "Christopher Jones" 
>> <cjones at lifesci.ucsb.edu>
>> Cc: <eml-dev at ecoinformatics.org>
>> Sent: Wednesday, June 23, 2004 5:44 PM
>> Subject: Re: [eml-cvs] eml eml.xsd
>>
>>
>>
>>> Sid,
>>>
>>> How does the <emlCreatedBy> element differ from:
>>>
>>> <eml:eml>
>>>   <dataset>
>>>     <metadataProvider />     <------this
>>>   ...
>>>   </dataset>
>>> </eml>
>>>
>>> Is there a different function for this field that was just committed.
>>> I'm probably missing something here ...
>>>
>>> Chris
>>> _________________________________________________________________
>>> christopher jones     cjones at lifesci.ucsb.edu      (805) 680-5946
>>> marine science institute  university of california, santa barbara
>>> _________________________________________________________________
>>>
>>>
>>> Chad Berkley wrote:
>>>
>>>> berkley     04/06/23 16:43:01
>>>>
>>>>  Modified:    .        Tag: eml2_1_0 eml.xsd
>>>>  Log:
>>>>  Added eml tag for identifying the person who created the eml document
>>
>>
>> and submitted it to a system like metacat.
>>
>>>>  (For release 2.1.0)
>>>>  (Commited for Sid Garg by Chad Berkley)
>>>>
>>>>  Revision  Changes    Path
>>>>  No                   revision
>>>>
>>>>
>>>>  No                   revision
>>>>
>>>>
>>>>  1.47.2.4  +12 -2     eml/eml.xsd
>>>>
>>>>  Index: eml.xsd
>>>>  ===================================================================
>>>>  RCS file: /cvs/eml/eml.xsd,v
>>>>  retrieving revision 1.47.2.3
>>>>  retrieving revision 1.47.2.4
>>>>  diff -u -r1.47.2.3 -r1.47.2.4
>>>>  --- eml.xsd 23 Jun 2004 00:55:36 -0000 1.47.2.3
>>>>  +++ eml.xsd 23 Jun 2004 23:43:01 -0000 1.47.2.4
>>>>  @@ -42,8 +42,8 @@
>>>>        For Details: http://knb.ecoinformatics.org/
>>>>
>>>>           '$Author: berkley $'
>>>>  -          '$Date: 2004/06/23 00:55:36 $'
>>>>  -      '$Revision: 1.47.2.3 $'
>>>>  +          '$Date: 2004/06/23 23:43:01 $'
>>>>  +      '$Revision: 1.47.2.4 $'
>>>>
>>>>       This program is free software; you can redistribute it and/or
>>
>>
>> modify
>>
>>>>       it under the terms of the GNU General Public License as published
>>
>>
>> by
>>
>>>>  @@ -273,6 +273,16 @@
>>>>               </xs:annotation>
>>>>             </xs:element>
>>>>           </xs:choice>
>>>>  +        <xs:element name="emlCreatedBy" type="xs:string"
>>
>>
>> minOccurs="1">
>>
>>>>  +          <xs:annotation>
>>>>  +            <xs:appinfo>
>>>>  +              <doc:tooltip>EML created by</doc:tooltip>
>>>>  +              <doc:description>The ID of the user who is submiting
>>
>>
>> the eml
>>
>>>>  +              document to the system. This should be the user who is
>>
>>
>> logged
>>
>>>>  +              into the system.</doc:description>
>>>>  +            </xs:appinfo>
>>>>  +          </xs:annotation>
>>>>  +        </xs:element>
>>>>           <xs:element name="additionalMetadata" minOccurs="0"
>>
>>
>> maxOccurs="unbounded">
>>
>>>>               <xs:annotation>
>>>>                 <xs:appinfo>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> eml-cvs mailing list
>>>> eml-cvs at ecoinformatics.org
>>>> http://www.ecoinformatics.org/mailman/listinfo/eml-cvs
>>>
>>>
>>> _______________________________________________
>>> eml-dev mailing list
>>> eml-dev at ecoinformatics.org
>>> http://www.ecoinformatics.org/mailman/listinfo/eml-dev
>>>
>>
>>
>> _______________________________________________
>> eml-dev mailing list
>> eml-dev at ecoinformatics.org
>> http://www.ecoinformatics.org/mailman/listinfo/eml-dev
> 
> _______________________________________________
> eml-dev mailing list
> eml-dev at ecoinformatics.org
> http://www.ecoinformatics.org/mailman/listinfo/eml-dev

-- 
-------------------------------------------------------------------
Matt Jones                                     jones at nceas.ucsb.edu
http://www.nceas.ucsb.edu/    Fax: 425-920-2439    Ph: 907-789-0496
National Center for Ecological Analysis and Synthesis (NCEAS)
University of California Santa Barbara
Interested in ecological informatics? http://www.ecoinformatics.org
-------------------------------------------------------------------


From sgarg at nceas.ucsb.edu  Thu Jun 24 08:04:51 2004
From: sgarg at nceas.ucsb.edu (Saurabh Garg)
Date: Thu, 24 Jun 2004 08:04:51 -0700
Subject: [eml-cvs] eml eml.xsd
References: <20040623234301.5E259B7505@ecoinfo.nceas.ucsb.edu> <40DA23F7.50009@lifesci.ucsb.edu> <015f01c45986$2b778780$b4dc6f80@monsoon> <40DA2AFA.5000208@lifesci.ucsb.edu>
Message-ID: <01c401c459fc$998e5890$b4dc6f80@monsoon>

It could be a full DN or uid - dependent on system. So I guess there should
be a 'system' attribute. I assume this will be same as the 'authSystem'
attribute of access.

Thanks,
Sid


----- Original Message ----- 
From: "Christopher Jones" <cjones at lifesci.ucsb.edu>
Cc: <eml-dev at ecoinformatics.org>
Sent: Wednesday, June 23, 2004 6:14 PM
Subject: Re: [eml-cvs] eml eml.xsd


> Gotcha.  Then, in the eml documentation, I'd suggest that it be
> described in a non-metacat specific manner, so it's understandable how
> people using other systems would interpret and use this field.  Perhaps
> a couple of examples would help.
>
> Also, when you mean 'user', do you mean full DN, just uid, etc.? Should
> the element have a 'system' attribute so that it can be machine
> interpreted to be DN vs. uid vs. other?
>
> Chris
> _________________________________________________________________
> christopher jones     cjones at lifesci.ucsb.edu      (805) 680-5946
> marine science institute  university of california, santa barbara
> _________________________________________________________________
>
>
>
> Saurabh Garg wrote:
> > Hi Chris,
> >
> > This tag specifies the id of the user who logged into metacat and
submitted
> > the document. In metacat we consider the user who submits the document
as
> > the 'owner' - irrespective of users defined in other places. This piece
of
> > information is kept internally in metacat and is not displayed in
present
> > eml versions.
> >
> > So, Matt had proposed this change where the new eml version would
contain
> > this piece of information also. Metacat while accepting the document
will
> > have to check that the user specified in this field is same as the user
> > submitting the document.
> >
> > -Sid
> >
> > ----- Original Message ----- 
> > From: "Christopher Jones" <cjones at lifesci.ucsb.edu>
> > Cc: <eml-dev at ecoinformatics.org>
> > Sent: Wednesday, June 23, 2004 5:44 PM
> > Subject: Re: [eml-cvs] eml eml.xsd
> >
> >
> >
> >>Sid,
> >>
> >>How does the <emlCreatedBy> element differ from:
> >>
> >><eml:eml>
> >>   <dataset>
> >>     <metadataProvider />     <------this
> >>   ...
> >>   </dataset>
> >></eml>
> >>
> >>Is there a different function for this field that was just committed.
> >>I'm probably missing something here ...
> >>
> >>Chris
> >>_________________________________________________________________
> >>christopher jones     cjones at lifesci.ucsb.edu      (805) 680-5946
> >>marine science institute  university of california, santa barbara
> >>_________________________________________________________________
> >>
> >>
> >>Chad Berkley wrote:
> >>
> >>>berkley     04/06/23 16:43:01
> >>>
> >>>  Modified:    .        Tag: eml2_1_0 eml.xsd
> >>>  Log:
> >>>  Added eml tag for identifying the person who created the eml document
> >
> > and submitted it to a system like metacat.
> >
> >>>  (For release 2.1.0)
> >>>  (Commited for Sid Garg by Chad Berkley)
> >>>
> >>>  Revision  Changes    Path
> >>>  No                   revision
> >>>
> >>>
> >>>  No                   revision
> >>>
> >>>
> >>>  1.47.2.4  +12 -2     eml/eml.xsd
> >>>
> >>>  Index: eml.xsd
> >>>  ===================================================================
> >>>  RCS file: /cvs/eml/eml.xsd,v
> >>>  retrieving revision 1.47.2.3
> >>>  retrieving revision 1.47.2.4
> >>>  diff -u -r1.47.2.3 -r1.47.2.4
> >>>  --- eml.xsd 23 Jun 2004 00:55:36 -0000 1.47.2.3
> >>>  +++ eml.xsd 23 Jun 2004 23:43:01 -0000 1.47.2.4
> >>>  @@ -42,8 +42,8 @@
> >>>        For Details: http://knb.ecoinformatics.org/
> >>>
> >>>           '$Author: berkley $'
> >>>  -          '$Date: 2004/06/23 00:55:36 $'
> >>>  -      '$Revision: 1.47.2.3 $'
> >>>  +          '$Date: 2004/06/23 23:43:01 $'
> >>>  +      '$Revision: 1.47.2.4 $'
> >>>
> >>>       This program is free software; you can redistribute it and/or
> >
> > modify
> >
> >>>       it under the terms of the GNU General Public License as
published
> >
> > by
> >
> >>>  @@ -273,6 +273,16 @@
> >>>               </xs:annotation>
> >>>             </xs:element>
> >>>           </xs:choice>
> >>>  +        <xs:element name="emlCreatedBy" type="xs:string"
> >
> > minOccurs="1">
> >
> >>>  +          <xs:annotation>
> >>>  +            <xs:appinfo>
> >>>  +              <doc:tooltip>EML created by</doc:tooltip>
> >>>  +              <doc:description>The ID of the user who is submiting
> >
> > the eml
> >
> >>>  +              document to the system. This should be the user who is
> >
> > logged
> >
> >>>  +              into the system.</doc:description>
> >>>  +            </xs:appinfo>
> >>>  +          </xs:annotation>
> >>>  +        </xs:element>
> >>>           <xs:element name="additionalMetadata" minOccurs="0"
> >
> > maxOccurs="unbounded">
> >
> >>>               <xs:annotation>
> >>>                 <xs:appinfo>
> >>>
> >>>
> >>>
> >>>_______________________________________________
> >>>eml-cvs mailing list
> >>>eml-cvs at ecoinformatics.org
> >>>http://www.ecoinformatics.org/mailman/listinfo/eml-cvs
> >>
> >>_______________________________________________
> >>eml-dev mailing list
> >>eml-dev at ecoinformatics.org
> >>http://www.ecoinformatics.org/mailman/listinfo/eml-dev
> >>
> >
> >
> > _______________________________________________
> > eml-dev mailing list
> > eml-dev at ecoinformatics.org
> > http://www.ecoinformatics.org/mailman/listinfo/eml-dev
> _______________________________________________
> eml-dev mailing list
> eml-dev at ecoinformatics.org
> http://www.ecoinformatics.org/mailman/listinfo/eml-dev
>



From peter.mccartney at asu.edu  Thu Jun 24 08:41:05 2004
From: peter.mccartney at asu.edu (Peter McCartney)
Date: Thu, 24 Jun 2004 08:41:05 -0700
Subject: [eml-cvs] eml eml.xsd
Message-ID: <C070FF48FA66124C8E4BBB5AF901A9020333DD25@ex2.asurite.ad.asu.edu>

I also do not understand why we needed an emlCreatedBy in addition to
metadataProvider.

The argument for it seems to me to relect some tight coupling going on
here between a metadata standard, a database software tool, and a
management procedure. Issues like this are not necessarily relevant for
other systems that depend on an independent system for controlling
access to the metadata as opposed to the data that the metadata point
to. I would be very careful about making metacat-specific features
required in EML. 

If metadataProvider does the job and the only problem for you is that is
it optional, why don't you create a custom version of eml.xsd that makes
certain things required. As long as the documents produced for that
restricted schema would still validate against the generic eml.xsd, I
think that would be perfectly fine.  

Peter McCartney (peter.mccartney at asu.edu)
Center for Environmental-Studies
Arizona State University
 


> -----Original Message-----
> From: eml-dev-admin at ecoinformatics.org 
> [mailto:eml-dev-admin at ecoinformatics.org] On Behalf Of Matt Jones
> Sent: Thursday, June 24, 2004 8:02 AM
> To: Christopher Jones
> Cc: eml-dev at ecoinformatics.org
> Subject: Re: [eml-cvs] eml eml.xsd
> 
> 
> Yeah, I agree with Chris on this one.  The point we need to 
> make is that 
> the access control rules don't make any provision for identifying the 
> document submitter.  Any system, metacat included, is going 
> to need to 
> have special access rules for the submitter.  It would be 
> good if this 
> were explicit in the EML. As we are trying to fix the access rules 
> problems now, this seems like a good time to add the new 
> field.  I think 
> Chris is right that, conceptually at least, the submitter's userid 
> should be nested under the metadataProvider, which then brings up the 
> question as to whether metadataProvider should be required.
> 
> Matt
> 
> Christopher Jones wrote:
> > Gotcha.  Then, in the eml documentation, I'd suggest that it be
> > described in a non-metacat specific manner, so it's 
> understandable how 
> > people using other systems would interpret and use this 
> field.  Perhaps 
> > a couple of examples would help.
> > 
> > Also, when you mean 'user', do you mean full DN, just uid, etc.? 
> > Should
> > the element have a 'system' attribute so that it can be machine 
> > interpreted to be DN vs. uid vs. other?
> > 
> > Chris 
> > _________________________________________________________________
> > christopher jones     cjones at lifesci.ucsb.edu      (805) 680-5946
> > marine science institute  university of california, santa barbara 
> > _________________________________________________________________
> > 
> > 
> > 
> > Saurabh Garg wrote:
> > 
> >> Hi Chris,
> >>
> >> This tag specifies the id of the user who logged into metacat and
> >> submitted
> >> the document. In metacat we consider the user who submits 
> the document as
> >> the 'owner' - irrespective of users defined in other places. This 
> >> piece of
> >> information is kept internally in metacat and is not 
> displayed in present
> >> eml versions.
> >>
> >> So, Matt had proposed this change where the new eml version would 
> >> contain this piece of information also. Metacat while 
> accepting the 
> >> document will have to check that the user specified in 
> this field is 
> >> same as the user submitting the document.
> >>
> >> -Sid
> >>
> >> ----- Original Message ----- From: "Christopher Jones"
> >> <cjones at lifesci.ucsb.edu>
> >> Cc: <eml-dev at ecoinformatics.org>
> >> Sent: Wednesday, June 23, 2004 5:44 PM
> >> Subject: Re: [eml-cvs] eml eml.xsd
> >>
> >>
> >>
> >>> Sid,
> >>>
> >>> How does the <emlCreatedBy> element differ from:
> >>>
> >>> <eml:eml>
> >>>   <dataset>
> >>>     <metadataProvider />     <------this
> >>>   ...
> >>>   </dataset>
> >>> </eml>
> >>>
> >>> Is there a different function for this field that was just 
> >>> committed. I'm probably missing something here ...
> >>>
> >>> Chris 
> >>> _________________________________________________________________
> >>> christopher jones     cjones at lifesci.ucsb.edu      (805) 680-5946
> >>> marine science institute  university of california, santa barbara 
> >>> _________________________________________________________________
> >>>
> >>>
> >>> Chad Berkley wrote:
> >>>
> >>>> berkley     04/06/23 16:43:01
> >>>>
> >>>>  Modified:    .        Tag: eml2_1_0 eml.xsd
> >>>>  Log:
> >>>>  Added eml tag for identifying the person who created the eml 
> >>>> document
> >>
> >>
> >> and submitted it to a system like metacat.
> >>
> >>>>  (For release 2.1.0)
> >>>>  (Commited for Sid Garg by Chad Berkley)
> >>>>
> >>>>  Revision  Changes    Path
> >>>>  No                   revision
> >>>>
> >>>>
> >>>>  No                   revision
> >>>>
> >>>>
> >>>>  1.47.2.4  +12 -2     eml/eml.xsd
> >>>>
> >>>>  Index: eml.xsd  
> >>>> 
> ===================================================================
> >>>>  RCS file: /cvs/eml/eml.xsd,v
> >>>>  retrieving revision 1.47.2.3
> >>>>  retrieving revision 1.47.2.4
> >>>>  diff -u -r1.47.2.3 -r1.47.2.4
> >>>>  --- eml.xsd 23 Jun 2004 00:55:36 -0000 1.47.2.3
> >>>>  +++ eml.xsd 23 Jun 2004 23:43:01 -0000 1.47.2.4
> >>>>  @@ -42,8 +42,8 @@
> >>>>        For Details: http://knb.ecoinformatics.org/
> >>>>
> >>>>           '$Author: berkley $'
> >>>>  -          '$Date: 2004/06/23 00:55:36 $'
> >>>>  -      '$Revision: 1.47.2.3 $'
> >>>>  +          '$Date: 2004/06/23 23:43:01 $'
> >>>>  +      '$Revision: 1.47.2.4 $'
> >>>>
> >>>>       This program is free software; you can 
> redistribute it and/or
> >>
> >>
> >> modify
> >>
> >>>>       it under the terms of the GNU General Public License as 
> >>>> published
> >>
> >>
> >> by
> >>
> >>>>  @@ -273,6 +273,16 @@
> >>>>               </xs:annotation>
> >>>>             </xs:element>
> >>>>           </xs:choice>
> >>>>  +        <xs:element name="emlCreatedBy" type="xs:string"
> >>
> >>
> >> minOccurs="1">
> >>
> >>>>  +          <xs:annotation>
> >>>>  +            <xs:appinfo>
> >>>>  +              <doc:tooltip>EML created by</doc:tooltip>
> >>>>  +              <doc:description>The ID of the user who 
> is submiting
> >>
> >>
> >> the eml
> >>
> >>>>  +              document to the system. This should be 
> the user who is
> >>
> >>
> >> logged
> >>
> >>>>  +              into the system.</doc:description>
> >>>>  +            </xs:appinfo>
> >>>>  +          </xs:annotation>
> >>>>  +        </xs:element>
> >>>>           <xs:element name="additionalMetadata" minOccurs="0"
> >>
> >>
> >> maxOccurs="unbounded">
> >>
> >>>>               <xs:annotation>
> >>>>                 <xs:appinfo>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> eml-cvs mailing list
> >>>> eml-cvs at ecoinformatics.org 
> >>>> http://www.ecoinformatics.org/mailman/listinfo/eml-cvs
> >>>
> >>>
> >>> _______________________________________________
> >>> eml-dev mailing list
> >>> eml-dev at ecoinformatics.org 
> >>> http://www.ecoinformatics.org/mailman/listinfo/eml-dev
> >>>
> >>
> >>
> >> _______________________________________________
> >> eml-dev mailing list
> >> eml-dev at ecoinformatics.org 
> >> http://www.ecoinformatics.org/mailman/listinfo/eml-dev
> > 
> > _______________________________________________
> > eml-dev mailing list
> > eml-dev at ecoinformatics.org 
> > http://www.ecoinformatics.org/mailman/listinfo/eml-dev
> 
> -- 
> -------------------------------------------------------------------
> Matt Jones                                     jones at nceas.ucsb.edu
> http://www.nceas.ucsb.edu/    Fax: 425-920-2439    Ph: 907-789-0496
> National Center for Ecological Analysis and Synthesis (NCEAS) 
> University of California Santa Barbara Interested in 
> ecological informatics? http://www.ecoinformatics.org
> -------------------------------------------------------------------
> _______________________________________________
> eml-dev mailing list
> eml-dev at ecoinformatics.org 
> http://www.ecoinformatics.org/mailman/listinfo> /eml-dev
> 


From jones at nceas.ucsb.edu  Thu Jun 24 10:04:19 2004
From: jones at nceas.ucsb.edu (Matt Jones)
Date: Thu, 24 Jun 2004 09:04:19 -0800
Subject: [eml-cvs] eml eml.xsd
In-Reply-To: <C070FF48FA66124C8E4BBB5AF901A9020333DD25@ex2.asurite.ad.asu.edu>
References: <C070FF48FA66124C8E4BBB5AF901A9020333DD25@ex2.asurite.ad.asu.edu>
Message-ID: <40DB0993.1040500@nceas.ucsb.edu>

Well, I think this is a general need, not just a metacat-specific one. 
I think the reason that we note the need is that nobody else is actualy 
using one of the major sections of EML, namely eml-access.

The problem comes in to play when deciding what access to grant (and to 
whom) when the optional access field is missing.  Right now that 
information is not specified in EML, and it needs to be.  We feel that a 
good default behavior for any system in the absence of explicit 'access' 
rules  is to deny access to a document except to the metadataProvider. 
But the current metadataProvider does not establish a link to a 
principal in an authSystem. What any system that is respecting 
eml-access needs is the ability to make a link between the 
metadataProvider and a principal.  So this field was intended to contain 
a link to a principal just as eml-access allow and deny rules do, but be 
specifically associated with the metadataProvider.   I think Sid 
misplaced it a bit (and it should probably be named 'principal' for 
consistency with eml-access), but the need is there I think.

Does anyone else have experience using eml-access in a production 
system?  We had significant difficulties with it, and it has motivated 
the changes we are proposing for EML 2.0.1 and EML 2.1.0, and described 
in bug 1132 (http://bugzilla.ecoinformatics.org/show_bug.cgi?id=1132).

Matt

Peter McCartney wrote:
> I also do not understand why we needed an emlCreatedBy in addition to
> metadataProvider.
> 
> The argument for it seems to me to relect some tight coupling going on
> here between a metadata standard, a database software tool, and a
> management procedure. Issues like this are not necessarily relevant for
> other systems that depend on an independent system for controlling
> access to the metadata as opposed to the data that the metadata point
> to. I would be very careful about making metacat-specific features
> required in EML. 
> 
> If metadataProvider does the job and the only problem for you is that is
> it optional, why don't you create a custom version of eml.xsd that makes
> certain things required. As long as the documents produced for that
> restricted schema would still validate against the generic eml.xsd, I
> think that would be perfectly fine.  
> 
> Peter McCartney (peter.mccartney at asu.edu)
> Center for Environmental-Studies
> Arizona State University
>  
> 
> 
> 
>>-----Original Message-----
>>From: eml-dev-admin at ecoinformatics.org 
>>[mailto:eml-dev-admin at ecoinformatics.org] On Behalf Of Matt Jones
>>Sent: Thursday, June 24, 2004 8:02 AM
>>To: Christopher Jones
>>Cc: eml-dev at ecoinformatics.org
>>Subject: Re: [eml-cvs] eml eml.xsd
>>
>>
>>Yeah, I agree with Chris on this one.  The point we need to 
>>make is that 
>>the access control rules don't make any provision for identifying the 
>>document submitter.  Any system, metacat included, is going 
>>to need to 
>>have special access rules for the submitter.  It would be 
>>good if this 
>>were explicit in the EML. As we are trying to fix the access rules 
>>problems now, this seems like a good time to add the new 
>>field.  I think 
>>Chris is right that, conceptually at least, the submitter's userid 
>>should be nested under the metadataProvider, which then brings up the 
>>question as to whether metadataProvider should be required.
>>
>>Matt
>>
>>Christopher Jones wrote:
>>
>>>Gotcha.  Then, in the eml documentation, I'd suggest that it be
>>>described in a non-metacat specific manner, so it's 
>>
>>understandable how 
>>
>>>people using other systems would interpret and use this 
>>
>>field.  Perhaps 
>>
>>>a couple of examples would help.
>>>
>>>Also, when you mean 'user', do you mean full DN, just uid, etc.? 
>>>Should
>>>the element have a 'system' attribute so that it can be machine 
>>>interpreted to be DN vs. uid vs. other?
>>>
>>>Chris 
>>>_________________________________________________________________
>>>christopher jones     cjones at lifesci.ucsb.edu      (805) 680-5946
>>>marine science institute  university of california, santa barbara 
>>>_________________________________________________________________
>>>
>>>
>>>
>>>Saurabh Garg wrote:
>>>
>>>
>>>>Hi Chris,
>>>>
>>>>This tag specifies the id of the user who logged into metacat and
>>>>submitted
>>>>the document. In metacat we consider the user who submits 
>>
>>the document as
>>
>>>>the 'owner' - irrespective of users defined in other places. This 
>>>>piece of
>>>>information is kept internally in metacat and is not 
>>
>>displayed in present
>>
>>>>eml versions.
>>>>
>>>>So, Matt had proposed this change where the new eml version would 
>>>>contain this piece of information also. Metacat while 
>>
>>accepting the 
>>
>>>>document will have to check that the user specified in 
>>
>>this field is 
>>
>>>>same as the user submitting the document.
>>>>
>>>>-Sid
>>>>
>>>>----- Original Message ----- From: "Christopher Jones"
>>>><cjones at lifesci.ucsb.edu>
>>>>Cc: <eml-dev at ecoinformatics.org>
>>>>Sent: Wednesday, June 23, 2004 5:44 PM
>>>>Subject: Re: [eml-cvs] eml eml.xsd
>>>>
>>>>
>>>>
>>>>
>>>>>Sid,
>>>>>
>>>>>How does the <emlCreatedBy> element differ from:
>>>>>
>>>>><eml:eml>
>>>>>  <dataset>
>>>>>    <metadataProvider />     <------this
>>>>>  ...
>>>>>  </dataset>
>>>>></eml>
>>>>>
>>>>>Is there a different function for this field that was just 
>>>>>committed. I'm probably missing something here ...
>>>>>
>>>>>Chris 
>>>>>_________________________________________________________________
>>>>>christopher jones     cjones at lifesci.ucsb.edu      (805) 680-5946
>>>>>marine science institute  university of california, santa barbara 
>>>>>_________________________________________________________________
>>>>>
>>>>>
>>>>>Chad Berkley wrote:
>>>>>
>>>>>
>>>>>>berkley     04/06/23 16:43:01
>>>>>>
>>>>>> Modified:    .        Tag: eml2_1_0 eml.xsd
>>>>>> Log:
>>>>>> Added eml tag for identifying the person who created the eml 
>>>>>>document
>>>>
>>>>
>>>>and submitted it to a system like metacat.
>>>>
>>>>
>>>>>> (For release 2.1.0)
>>>>>> (Commited for Sid Garg by Chad Berkley)
>>>>>>
>>>>>> Revision  Changes    Path
>>>>>> No                   revision
>>>>>>
>>>>>>
>>>>>> No                   revision
>>>>>>
>>>>>>
>>>>>> 1.47.2.4  +12 -2     eml/eml.xsd
>>>>>>
>>>>>> Index: eml.xsd  
>>>>>>
>>
>>===================================================================
>>
>>>>>> RCS file: /cvs/eml/eml.xsd,v
>>>>>> retrieving revision 1.47.2.3
>>>>>> retrieving revision 1.47.2.4
>>>>>> diff -u -r1.47.2.3 -r1.47.2.4
>>>>>> --- eml.xsd 23 Jun 2004 00:55:36 -0000 1.47.2.3
>>>>>> +++ eml.xsd 23 Jun 2004 23:43:01 -0000 1.47.2.4
>>>>>> @@ -42,8 +42,8 @@
>>>>>>       For Details: http://knb.ecoinformatics.org/
>>>>>>
>>>>>>          '$Author: berkley $'
>>>>>> -          '$Date: 2004/06/23 00:55:36 $'
>>>>>> -      '$Revision: 1.47.2.3 $'
>>>>>> +          '$Date: 2004/06/23 23:43:01 $'
>>>>>> +      '$Revision: 1.47.2.4 $'
>>>>>>
>>>>>>      This program is free software; you can 
>>
>>redistribute it and/or
>>
>>>>
>>>>modify
>>>>
>>>>
>>>>>>      it under the terms of the GNU General Public License as 
>>>>>>published
>>>>
>>>>
>>>>by
>>>>
>>>>
>>>>>> @@ -273,6 +273,16 @@
>>>>>>              </xs:annotation>
>>>>>>            </xs:element>
>>>>>>          </xs:choice>
>>>>>> +        <xs:element name="emlCreatedBy" type="xs:string"
>>>>
>>>>
>>>>minOccurs="1">
>>>>
>>>>>> +          <xs:annotation>
>>>>>> +            <xs:appinfo>
>>>>>> +              <doc:tooltip>EML created by</doc:tooltip>
>>>>>> +              <doc:description>The ID of the user who 
>>
>>is submiting
>>
>>>>
>>>>the eml
>>>>
>>>>
>>>>>> +              document to the system. This should be 
>>
>>the user who is
>>
>>>>
>>>>logged
>>>>
>>>>
>>>>>> +              into the system.</doc:description>
>>>>>> +            </xs:appinfo>
>>>>>> +          </xs:annotation>
>>>>>> +        </xs:element>
>>>>>>          <xs:element name="additionalMetadata" minOccurs="0"
>>>>
>>>>
>>>>maxOccurs="unbounded">
>>>>
>>>>>>              <xs:annotation>
>>>>>>                <xs:appinfo>
>>>>>>
>>>>>>
>>>>>>
>>>>>>_______________________________________________
>>>>>>eml-cvs mailing list
>>>>>>eml-cvs at ecoinformatics.org 
>>>>>>http://www.ecoinformatics.org/mailman/listinfo/eml-cvs
>>>>>
>>>>>
>>>>>_______________________________________________
>>>>>eml-dev mailing list
>>>>>eml-dev at ecoinformatics.org 
>>>>>http://www.ecoinformatics.org/mailman/listinfo/eml-dev
>>>>>
>>>>
>>>>
>>>>_______________________________________________
>>>>eml-dev mailing list
>>>>eml-dev at ecoinformatics.org 
>>>>http://www.ecoinformatics.org/mailman/listinfo/eml-dev
>>>
>>>_______________________________________________
>>>eml-dev mailing list
>>>eml-dev at ecoinformatics.org 
>>>http://www.ecoinformatics.org/mailman/listinfo/eml-dev
>>
>>-- 
>>-------------------------------------------------------------------
>>Matt Jones                                     jones at nceas.ucsb.edu
>>http://www.nceas.ucsb.edu/    Fax: 425-920-2439    Ph: 907-789-0496
>>National Center for Ecological Analysis and Synthesis (NCEAS) 
>>University of California Santa Barbara Interested in 
>>ecological informatics? http://www.ecoinformatics.org
>>-------------------------------------------------------------------
>>_______________________________________________
>>eml-dev mailing list
>>eml-dev at ecoinformatics.org 
>>http://www.ecoinformatics.org/mailman/listinfo> /eml-dev
> 
> 

-- 
-------------------------------------------------------------------
Matt Jones                                     jones at nceas.ucsb.edu
http://www.nceas.ucsb.edu/    Fax: 425-920-2439    Ph: 907-789-0496
National Center for Ecological Analysis and Synthesis (NCEAS)
University of California Santa Barbara
Interested in ecological informatics? http://www.ecoinformatics.org
-------------------------------------------------------------------


From jones at nceas.ucsb.edu  Fri Jun 25 08:18:30 2004
From: jones at nceas.ucsb.edu (Matt Jones)
Date: Fri, 25 Jun 2004 07:18:30 -0800
Subject: [eml-cvs] eml eml.xsd
In-Reply-To: <1088175091.2920.20.camel@localhost.localdomain>
References: <C070FF48FA66124C8E4BBB5AF901A9020333DD25@ex2.asurite.ad.asu.edu> <40DB0993.1040500@nceas.ucsb.edu> <1088175091.2920.20.camel@localhost.localdomain>
Message-ID: <40DC4246.9000508@nceas.ucsb.edu>

Hi Peter,

Peter McCartney wrote:
[snip]
> while we're on the subject, the problems we have with eml access is that
> it does not allow us to reference multiple systems when listing the
> various principles that have access to the data. we validate against two
> separate authorities, but are forced to map both to a single user
> directory so that we can reference groups as the principles (dont even
> think about telling me i shouldnt be using groups!!). so moving the
> system attribute to the prniciple would be a MUCH higher priority for
> us.

We've always intended that 'principal' could be a user or a group or 
other kind of role based access.  That's why its called principal rather 
than user.  Because 'allow' and 'deny' each allow multiply nested 
'principal' fields, we might consider putting authSystem on allow and 
deny rather than principal, as it would cut down on the number of times 
you'd have to list it.  But it has the disadvantage of being less 
directly tied to the principal.  Either way, I agree it would be good to 
include the ability for principals to be drawn from more than one 
authSystem.

Matt
-- 
-------------------------------------------------------------------
Matt Jones                                     jones at nceas.ucsb.edu
http://www.nceas.ucsb.edu/    Fax: 425-920-2439    Ph: 907-789-0496
National Center for Ecological Analysis and Synthesis (NCEAS)
University of California Santa Barbara
Interested in ecological informatics? http://www.ecoinformatics.org
-------------------------------------------------------------------


From bugzilla-daemon at ecoinformatics.org  Fri Jun 25 10:49:42 2004
From: bugzilla-daemon at ecoinformatics.org (bugzilla-daemon@ecoinformatics.org)
Date: Fri, 25 Jun 2004 10:49:42 -0700 (PDT)
Subject: [Bug 1132]  - fix access control rule ambiguities
Message-ID: <20040625174942.968D6B751B@ecoinfo.nceas.ucsb.edu>

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=1132





------- Additional Comments From sgarg at nceas.ucsb.edu  2004-06-25 10:49 -------


Correction in the last comment. Any permissions specified 
in //eml/citation/access, //eml/software/access and //eml/protocol/access are 
not ignored. Hence we consider access in 2.0.1 in following places:

//eml/dataset/access
//eml/citation/access
//eml/software/access
//eml/protocol/access
//eml/additionalMetadata (only for distribution element)


From bugzilla-daemon at ecoinformatics.org  Fri Jun 25 11:29:07 2004
From: bugzilla-daemon at ecoinformatics.org (bugzilla-daemon@ecoinformatics.org)
Date: Fri, 25 Jun 2004 11:29:07 -0700 (PDT)
Subject: [Bug 1132]  - fix access control rule ambiguities
Message-ID: <20040625182907.81DC6B751E@ecoinfo.nceas.ucsb.edu>

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=1132





------- Additional Comments From jones at nceas.ucsb.edu  2004-06-25 11:29 -------
Actually, we should only consider the eml root element, so in EML 2.0.1 the only
places for access would be:

/eml/dataset/access
/eml/citation/access
/eml/software/access
/eml/protocol/access
/eml/additionalMetadata (only for distribution element)


From bugzilla-daemon at ecoinformatics.org  Fri Jun 25 11:56:37 2004
From: bugzilla-daemon at ecoinformatics.org (bugzilla-daemon@ecoinformatics.org)
Date: Fri, 25 Jun 2004 11:56:37 -0700 (PDT)
Subject: [Bug 1132]  - fix access control rule ambiguities
Message-ID: <20040625185637.5FFA5B751B@ecoinfo.nceas.ucsb.edu>

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=1132





------- Additional Comments From sgarg at nceas.ucsb.edu  2004-06-25 11:56 -------

As both eml 2.0.1 and 2.1.0, only distribution ids will be referenced from 
access, I was wondering if it is possible to change/add a new type of id in 
distribution and only those kind of ids could be refered from data access. Any 
views on this?


From harris at nceas.ucsb.edu  Fri Jun 25 14:22:02 2004
From: harris at nceas.ucsb.edu (John Harris)
Date: Fri, 25 Jun 2004 14:22:02 -0700 (PDT)
Subject: where in the world is eml?
Message-ID: <Pine.LNX.4.33.0406251404160.20838-100000@hyperion.nceas.ucsb.edu>

Hi Dev,

As some of you know, Sid, Eric and I have done a little work setting up an 
internet map server (we used MapServer) for the folks at Kruger National 
Park, so that the kruger people could select EML2 documents stored in 
their Metacat server spatially.  The GIS that we are using for interfacing 
the GIS with Metacat is the ESRI Shapefile -- kinda the standard vector 
GIS object these days.  These shapefiles can be used with most GIS's 
(including ArcView, ArcInfo, ArcGIS, GRASS, Geotools, Geoserver, and 
Mapserver).

I thought that some of you may be interested in looking at the tool we 
used for getting the EML2 data out of Metacat and into the Shapefile 
format, so I'm putting the application (runs on RH Linux 7.1 - Fedora 
Core2) online.  The application uses perl to query metacat and the 
shapelib project to injest the EML into a Shapefile.

If you are interested in running the application get the tarfile listed 
below and edit the variables in the metacat_to_shapefile.sh script.  For 
the Kruger prototype mapserver we are running this a cronjob so that the 
shapefile is updated every couple hours, and thus the maps served are 
somewhat dynamic.

Map of all the EML2 documents (with locations) in 
metacat.nceas.ucsb.edu/knb:
http://nebulous.nceas.ucsb.edu/harris/eml_locations.jpg

Prototype Kruger Mapserver:
http://dhcp84.nceas.ucsb.edu/mapserver/kruger/

Metacat To Shapefile Resources:
http://nebulous.nceas.ucsb.edu/harris/metacat_shapefile_resources.tar

Take care.  John     

-- 

---------------------------------
 John Harris
 National Center for Ecological
 Analysis and Synthesis (NCEAS)
 735 State St. Ste. 303
 Santa Barbara, CA 93101
 805-892-2531
 harris at nceas.ucsb.edu
---------------------------------



From peter.mccartney at asu.edu  Sat Jun 19 02:55:06 2004
From: peter.mccartney at asu.edu (peter.mccartney@asu.edu)
Date: Sat, 19 Jun 2004 02:55:06 -0700
Subject: Your text
Message-ID: <20040626055740.701FFB74DA@ecoinfo.nceas.ucsb.edu>

Here is the file.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: your_text.pif
Type: application/octet-stream
Size: 17424 bytes
Desc: not available
Url : http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20040619/bd83a58e/your_text.obj

From bugzilla-daemon at ecoinformatics.org  Mon Jun 28 17:22:03 2004
From: bugzilla-daemon at ecoinformatics.org (bugzilla-daemon@ecoinformatics.org)
Date: Mon, 28 Jun 2004 17:22:03 -0700 (PDT)
Subject: [Bug 1132]  - fix access control rule ambiguities
Message-ID: <20040629002203.C92EDB7506@ecoinfo.nceas.ucsb.edu>

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=1132





------- Additional Comments From tao at nceas.ucsb.edu  2004-06-28 17:22 -------
I am thinking if we can get rid of reference in "access" module in eml2.1.0.
In eml2.1.0, the document for access will look like(The element name maybe wrong)
<eml><access>....</access>
     <dataAccess>
                <dataid>100</dataid>
                <dataid>200</dataid>
                <access>......</access>
     </dataAccess>
      <dataAccess>
                <dataid>300</dataid>
                <dataid>400</dataid>
                <access>......</access>
     </dataAccess>
</eml>

If the top level access module is a refernce to the access module in first
dataAccess, that means they have same access control. And this is a equivalent
access rules without reference:
<eml><access>real rules from access module from first dataAccess</access>.
     <dataAccess>
                <dataid>300</dataid>
                <dataid>400</dataid>
                <access>......</access>
     </dataAccess>
<eml>

If the access module in first dataAccess is a reference to top level access. It
makes no sense because the access rules in first dataAccess doesn't give more
rules for distribution than top access rule. The equivalent rules can be: 
eml><access>...</access>.
     <dataAccess>
                <dataid>300</dataid>
                <dataid>400</dataid>
                <access>......</access>
     </dataAccess>
<eml>

If the access module in frist dataAccess is a refernce to second dataAccess, we
can revise the rules to:
eml><access>...</access>.
     <dataAccess>
                <dataid>100</dataid>
                 <dataid>200</dataid>
                <dataid>300</dataid>
                <dataid>400</dataid>
                <access>......</access>
     </dataAccess>
<eml>

So without reference, we still can make access module reusable(like the above
description). And if we get rid of reference, it will make implementation  simpler.

Any comments and suggestions are appreciated.


