From bugzilla-daemon at ecoinformatics.org  Mon May 10 15:22:59 2004
From: bugzilla-daemon at ecoinformatics.org (bugzilla-daemon@ecoinformatics.org)
Date: Mon, 10 May 2004 15:22:59 -0700 (PDT)
Subject: [Bug 1132]  - fix access control rule ambiguities
Message-ID: <20040510222259.E9894B7574@ecoinfo.nceas.ucsb.edu>

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

sgarg at nceas.ucsb.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|EML2.0.2                    |EML2.1.0



------- Additional Comments From sgarg at nceas.ucsb.edu  2004-05-10 15:22 -------

Notes taken based on the conversation on 6th May 2004:

1. Discussion on how Access should be handled in Metacat while reading eml 2.0.0
In eml 2.0.0 Access can be specified in following places.
//eml/dataset/access
//eml/citation/access
//eml/software/access
//eml/protocol/access
//eml/additionalMetadata

Permissions in //eml/dataset/access will be applied to all the metadata and by 
default to the data. Any permissions specified in //eml/citation/access, 
//eml/software/access and //eml/protocol/access are ignored. So all the 
metadata has same permissions overall. However, access rules can still be 
specified for any data attached to the metadata. This can be done in following 
manner:
Define a reference id in the <distribution> for which you want to define the 
access control. e.g. 
        <distribution id="xxyyzz">
                .
                .
        </distribution>
To define the access rule for the above distribution, use
//eml/additionalMetadata is following way:
<additionalMetadata>
     <describes>
        xxyyzz
     </describes>
     <access>
          .
          .
     <access>
</additionalMetadata>

If additioncalMetadata describes as id which is not defined in the current eml 
document, then that additioncalMetadata is ignored. 
If the id is defined in the current eml document, but is not in distribution 
tag, then also that additioncalMetadata is ignored. 
If a distribution tag contains reference id but there is no additional Metadata 
entry for that reference id, then the rules specified in //eml/dataset/access 
are applied to this distribution. 

2. Discussion on how Access should be handled in Metacat while reading eml 2.1.0
In eml 2.1.0 Access can be specified in following places.
//eml/access
//eml/..../distribution/access

Permissions in //eml/access will be applied to all the metadata and by default 
to the data. So all the metadata has same permissions overall. However, access 
rules can still be specified for any data attached to the metadata. This can be 
done using the /access that will now be added to the distribution tag. e.g. 
        <distribution>
           <access>
              .
           <access>
        </distribution>

If no access is specified in distribution then //eml/access rules are applied.


From Bishop.Gkay at epamail.epa.gov  Wed May 12 07:29:53 2004
From: Bishop.Gkay at epamail.epa.gov (Bishop.Gkay@epamail.epa.gov)
Date: Wed, 12 May 2004 10:29:53 -0400
Subject: Graphical representations of normative EML module nesting
Message-ID: 
 <OF1B3DF2A3.213E9A2F-ON85256E92.004F365D-85256E92.004FFD3E@epamail.epa.gov>




...are there any? If so, where can one view them and perhaps use them in
a presentation to potential STAR grantees?  If there are none, I must
shoulder the burden myself, alas!

Very much obliged,

G.Kay Bishop
Technical Writer
EaGLe project

========================================================================================================

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery.  NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose.



From higgins at nceas.ucsb.edu  Wed May 12 07:00:17 2004
From: higgins at nceas.ucsb.edu (higgins@nceas.ucsb.edu)
Date: Wed, 12 May 2004 07:00:17 -0700
Subject: Graphical representations of normative EML module nesting
In-Reply-To: <OF1B3DF2A3.213E9A2F-ON85256E92.004F365D-85256E92.004FFD3E@epamail.epa.gov>
References: <OF1B3DF2A3.213E9A2F-ON85256E92.004F365D-85256E92.004FFD3E@epamail.epa.gov>
Message-ID: <1084370417.40a22df19bb84@hyperion.nceas.ucsb.edu>

See for example,

http://knb.ecoinformatics.org/software/eml/eml-2.0.0/eml-dataset.png

there are images of the graphical organization for various parts of eml on the 
referenced website. They were generated automatically using EMLSpy from the 
eml echema documents at http://knb.ecoinformatics.org/software/eml/eml-2.0.0/

Dan Higgins
NCEAS

Quoting Bishop.Gkay at epamail.epa.gov:

> 
> 
> 
> 
> ...are there any? If so, where can one view them and perhaps use them in
> a presentation to potential STAR grantees?  If there are none, I must
> shoulder the burden myself, alas!
> 
> Very much obliged,
> 
> G.Kay Bishop
> Technical Writer
> EaGLe project
> 
> 
==============================================================================
==========================
> 
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery.  NOTE: Regardless of content, this e-mail shall not operate to
> bind CSC to any order or other contract unless pursuant to explicit
> written agreement or government initiative expressly permitting the use
> of e-mail for such purpose.
> 
> _______________________________________________
> eml-dev mailing list
> eml-dev at ecoinformatics.org
> http://www.ecoinformatics.org/mailman/listinfo/eml-dev
> 



-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/


From berkley at nceas.ucsb.edu  Wed May 12 08:18:23 2004
From: berkley at nceas.ucsb.edu (Chad Berkley)
Date: Wed, 12 May 2004 08:18:23 -0700
Subject: Graphical representations of normative EML module nesting
In-Reply-To: <1084370417.40a22df19bb84@hyperion.nceas.ucsb.edu>
References: <OF1B3DF2A3.213E9A2F-ON85256E92.004F365D-85256E92.004FFD3E@epamail.epa.gov> <1084370417.40a22df19bb84@hyperion.nceas.ucsb.edu>
Message-ID: <9C0C0356-A427-11D8-B122-000A95DA7EF8@nceas.ucsb.edu>

small typo:

EMLSpy -> XMLSpy

chad

On May 12, 2004, at 7:00 AM, higgins at nceas.ucsb.edu wrote:

> See for example,
>
> http://knb.ecoinformatics.org/software/eml/eml-2.0.0/eml-dataset.png
>
> there are images of the graphical organization for various parts of  
> eml on the
> referenced website. They were generated automatically using EMLSpy  
> from the
> eml echema documents at  
> http://knb.ecoinformatics.org/software/eml/eml-2.0.0/
>
> Dan Higgins
> NCEAS
>
> Quoting Bishop.Gkay at epamail.epa.gov:
>
>>
>>
>>
>>
>> ...are there any? If so, where can one view them and perhaps use them  
>> in
>> a presentation to potential STAR grantees?  If there are none, I must
>> shoulder the burden myself, alas!
>>
>> Very much obliged,
>>
>> G.Kay Bishop
>> Technical Writer
>> EaGLe project
>>
>>
> ======================================================================= 
> =======
> ==========================
>>
>> This is a PRIVATE message. If you are not the intended recipient,  
>> please
>> delete without copying and kindly advise us by e-mail of the mistake  
>> in
>> delivery.  NOTE: Regardless of content, this e-mail shall not operate  
>> to
>> bind CSC to any order or other contract unless pursuant to explicit
>> written agreement or government initiative expressly permitting the  
>> use
>> of e-mail for such purpose.
>>
>> _______________________________________________
>> eml-dev mailing list
>> eml-dev at ecoinformatics.org
>> http://www.ecoinformatics.org/mailman/listinfo/eml-dev
>>
>
>
>
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
> _______________________________________________
> eml-dev mailing list
> eml-dev at ecoinformatics.org
> http://www.ecoinformatics.org/mailman/listinfo/eml-dev



