OASIS Emergency Management TC

 View Only
  • 1.  valueListURN

    Posted 06-08-2005 06:33
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    emergency message

    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


    Subject: valueListURN


    
    The valueListURN structure is used to capture the values from managed 
    vocabularies.
    
    It is defined as "where the content of valueListUrn is the Uniform 
    Resource Name of a published list of values and definitions, and the 
    content of value is a string (which may represent a number) denoting 
    the value itself"
    
    For example:
       <valueListUrn> http://www.dhs.gov/NiemRoleType </valueListURN>
       <value> ICS Operations Branch </value>
    
    valueListUrn is *not* a URN [1] - a true URN does not need to be split 
    as such and the examples
    in the draft document use URLs (which are not URNs).
    
    A URN would look something like "urn:oasis:terms:roles:ics-operations"
    (A list of URN namespaces currently defined are here [2])
    
    Q1: Do we want to use real URN syntax? (in which case, we just use a 
    single element)
    
    Q2: Do we want to use a hybrid system where we identify the authority 
    that manages the
    vocabulary list (with a URI) and then indicate the value?
    For example:
       <list>
         <authority> http://www.dhs.gov/NiemRoleType </authority>
         <value> ICS Operations Branch </value>
       </list>
    
    
    Cheers...
    
    Dr Renato Iannella
    Project Leader, NICTA, Brisbane, QLD, AUSTRALIA
    P: +61 7 3000 0484 F: +61 7 3000 0480 M: +61 4 1313 2206
    E: renato@nicta.com.au W: http://nicta.com.au
    
    [1] <http://ftp.rfc-editor.org/in-notes/rfc3406.txt>
    [2] <http://www.iana.org/assignments/urn-namespaces>
    
    
    --------------------------------------------------------------------------
    This email and any attachments may be confidential. They may contain legally
    privileged information or copyright material. You should not read, copy,
    use or disclose them without authorisation. If you are not an intended
    recipient, please contact us at once by return email and then delete both
    messages. We do not accept liability in connection with computer virus,
    data corruption, delay, interruption, unauthorised access or unauthorised
    amendment. This notice should not be removed.
    


    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]