LegalRuleML namespace

I have located the OASIS policy on XML namespaces.

    

http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#xml-namespaces

    

    According to my reading, the LegalRuleML namespace must comply with
    the following:

    

    "An XML namespace
      name identified by an HTTP scheme URI reference must conform
    to the pattern: 

    
      
http://docs.oasis-open.org/[tc-shortname]/ns/xxxx

    
    
Where: 

    
      
"[tc-shortname]" is the official spelling of the TC
        abbreviation as used in the (Kavi) group and typically in the TC
        email list URI (e.g., bias in the namespace
        name http://docs.oasis-open.org/bias/ns/bias-1.0/,
        owned and managed by the OASIS
          Biometric Identity Assurance Services (BIAS) Integration TC)

      
"xxxx" is a short string identifying an XML namespace, which
        should incorporate a versioning subcomponent (e.g., a
        string like 201011 representing a date or v1.1
        representing a version number)

      
"xxxx" may use any of the same sixty-four
          characters as names for files and directories/folders,
        plus internal "/", provided that it terminates with the
        character "/", "#", or an alphanumeric character [A-Za-z0-9].

    
    For example, 

    http://docs.oasis-open.org/legalruleml/ns/v1.0

    

    or

    

    http://docs.oasis-open.org/legalruleml/ns/2012-01-19

    (date is that of the first LegalRuleML TC meeting)

    

    As I start to develop more examples and schemas, there will be more
    and more files that use the LegalRuleML namespace.

    Up to now I have been using a blatantly temporary namespace, like

    

    http://example.legalruleml.org/lrml

    

    I would like to start using an official LegalRuleML namespace, so
    that I don't have to go back and change large numbers of files at a
    later date.

    May I suggest that we use the mailing list to choose a namespace?

    

    My personal preference is for the namespace with date, as that
    allows the namespace to stay the same through several versions as
    long as the versions are backward compatible.

    

    Tara