IDs

[Christopher Jones]

However, in terms of a UI generating a list of objects to choose from, 
the ID's already have to be in place in order to take part in the list. 
  Yes, the ID could be added later, but it would most likely be a manual 
process (or perhaps part of an 'advanced' UI).

Chris

Dan Higgins wrote:
> It doesn't seem to me that putting in ids so that they are "accessible 
> in the future for linking" is really needed, since if someone wants to 
> reference a node, they can always add an id as part of the package 
> editing they are doing. The only case where id might be needed is if 
> access control limited the ability to change some parts of package while 
> editing other parts.
> 
> Dan Higgins
> 
> Peter McCartney wrote:
> 
>> I think we should make all ID's be required to ensure that a content 
>> branch will be accessible in the future for linking. I think the 
>> system attribute should be optional for all except the resource root 
>> (im not so sure about protocol though since i think many protocol 
>> statements do not have general value as a resource). the scope should 
>> be required but i think the default should be document not system, 
>> since setting it to system would requre the scope attribute to be present.
>>
>> Peter McCartney (peter.mccartney at asu.edu)
>> Center for Environmental Studies
>> Arizona State University
>> 480-965-6791
>>
>> -----Original Message-----
>> From: Chad Berkley [ mailto:berkley at nceas.ucsb.edu ]
>> Sent: Monday, June 03, 2002 9:42 AM
>> To: Eml-Dev (E-mail)
>> Subject: IDs
>>
>>
>> A new question for everyone:  Should all ID fields be optional or
>> required or should it depend on the module in which it exists?  For
>> instance, we could say that all attributes must have an id, but not all
>> citations. 
>>
>> comments?
>>  
>> -- 
>> -----------------------
>> Chad Berkley
>> National Center for
>> Ecological Analysis
>> and Synthesis (NCEAS)
>> berkley at nceas.ucsb.edu
>> -----------------------
>>
>> _______________________________________________
>> eml-dev mailing list
>> eml-dev at ecoinformatics.org
>> http://www.ecoinformatics.org/mailman/listinfo/eml-dev
>>
> 
> -- 
> ---------------------------------
> Dan Higgins
> Software Developer
> National Center for Ecological Analysis and Synthesis (NCEAS) 
> 735 State St. Rm 205 
> Santa Barbara, CA 93101 
> 805-892-2531 
> higgins at nceas.ucsb.edu 
> ---------------------------------
> 
> 



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