[eml-dev] [Bug 1662] id key definitions in EML

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Fri Apr 15 12:41:46 PDT 2011


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

gastil <marygastil at yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marygastil at yahoo.com

--- Comment #8 from gastil <marygastil at yahoo.com> 2011-04-15 12:41:46 PDT ---
Prompted by a discussion about id, scope, and system in the lno-nis, I asked
Margaret for clarification of this issue.  Attached are two example EML docs,
one using the current 2.1.0 and one that may work when this feature is added
perhaps in 2.2.0

In EML 2.1.0 the way it is now,
some elements can have none or all of the attributes 
    id
    scope
    system

And the value of the scope attribute can be either
    document
    system

Currently, the EML parser requires that the value of the id attribute be unique
within an EML document, irregardless of the presence and values of the scope
and system attributes.

The feature request in bug 1662 asks that in EML 2.2.0 that the combination of
(id, scope, system) be unique, rather than requiring id alone to be unique.

It would still require that id values with the scope of document be unique. 
There could not be two identical id values both with scope document.

The "example_id_system_scope.xml" (attached and also available as
http://dev.nceas.ucsb.edu/knb/metacat/knb-lter-xxx.1) parses.  The
"example_id_system_scope_future.xml" does not parse in EML 2.1.0 but we suggest
it would parse if this feature is added.  The same id, janedoe, is used twice,
but with different scopes.  The use of that id in a reference raises the issue
of how that reference would be disambiguated.

Is that clarification accurate?

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the Eml-dev mailing list