OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

legalruleml message

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


Subject: Re: [legalruleml] LegalRuleML namespace


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


On 02/08/2012, at 12:28 AM, Giuseppe Contissa <giuseppe.contissa@unibo.it> wrote:

> +1
>
> Best,
>
> GC
>
>
> Il giorno 01/ago/2012, alle ore 15:14, monica.palmirani <monica.palmirani@unibo.it>
> ha scritto:
>
>> Dear all,
>>
>> I agree with the Tara's idea to vote via email the name space for LegalRuleML TC.
>>
>> my favorite one is:
>>
>> http://docs.oasis-open.org/legalruleml/ns/v1.0/
>>
>> for some reasons:
>> 1. I like name space with "slash"  for the reasons that Robin provided
>> 2. I'd prefer v1.0 because the other naming convention (2012-01-19) depends too much to the date of delivery and we are not free to make some minor changes
>> 3. the 2012-01-19 annotation makes the reference more complex and prone of errors
>>
>> I am encourage you to reply with your opinion in order to arrive to a prompt shared and negotiated decision.
>>
>> Yours,
>> Monica
>> Il 29/07/2012 18:53, Robin Cover ha scritto:
>>> Tara,
>>>
>>> The two examples you provided for URIs identifying XML namespace names
>>> are allowable for the LegalRuleML TC's identifier strings:
>>>
>>> http://docs.oasis-open.org/legalruleml/ns/v1.0
>>> http://docs.oasis-open.org/legalruleml/ns/2012-01-19
>>>
>>> I note that both examples are the "slashless" type (lacking
>>> final "/" character), and indeed, these three common types
>>> are allowable: [terminal] hash, slash, slashless.
>>>
>>> Some TCs prefer to use the "slash" type because provides
>>> an optimal base string to which one may join Qnames or
>>> other simple strings for non-information resources, by
>>> simple concatenation.  Suppose you have these base
>>> names:
>>>
>>> http://docs.oasis-open.org/legalruleml/ns/v1.0/
>>> http://docs.oasis-open.org/legalruleml/ns/2012-01-19/
>>>
>>> Then you can define URI-based identifiers for named objects
>>> (message types, link types, link relations, etc) using
>>> just the names.  E.g., if you had message types "request"
>>> and "response", you can use these identifiers
>>>
>>> http://docs.oasis-open.org/legalruleml/ns/2012-01-19/request
>>> http://docs.oasis-open.org/legalruleml/ns/2012-01-19/response
>>>
>>> See the details, as allowed by the Naming Directives, and
>>> examples from the OASIS CMIS specification:
>>>
>>> http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#nonInformationResources
>>>
>>> "Non-information resources using identifiers associated with XML
>>> namespaces may be based upon any HTTP scheme URI XML namespace
>>> declared by the TC (i.e., identifiers for named properties,
>>> functions, dialects, faults, actions, or any named message
>>> types). Example: see the Link Relations URIs in one of the
>>> CMIS v1.0 XML namespace documents (e.g.,
>>> http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions
>>> http://docs.oasis-open.org/ns/cmis/link/200908/policies )."
>>>
>>> CMIS:
>>>
>>> URI identifying the XML namespace name:
>>> http://docs.oasis-open.org/ns/cmis/link/200908/
>>>
>>> URIs for named link relations (based upon the namespace URI)
>>> Link relations: allowableactions, relationships, source, target, policies,...
>>>
>>> URIs:
>>> http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions
>>> http://docs.oasis-open.org/ns/cmis/link/200908/relationships
>>> http://docs.oasis-open.org/ns/cmis/link/200908/source
>>>
>>>
>>> On Sun, Jul 29, 2012 at 11:17 AM, Tara Athan <taraathan@gmail.com> wrote:
>>>> 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
>>>
>>>
>>
>>
>> --
>> ===================================
>> Associate professor of Legal Informatics
>> School of Law
>> Alma Mater Studiorum Università di Bologna
>> C.I.R.S.F.I.D. http://www.cirsfid.unibo.it/
>> Palazzo Dal Monte Gaudenzi - Via Galliera, 3
>> I - 40121 BOLOGNA (ITALY)
>> Tel +39 051 277217
>> Fax +39 051 260782
>> E-mail  monica.palmirani@unibo.it
>> ====================================
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: legalruleml-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: legalruleml-help@lists.oasis-open.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legalruleml-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: legalruleml-help@lists.oasis-open.org
>

All the best

Guido
--
Prof Guido Governatori
Associate Education Director and Principal Researcher
Queensland Research Laboratory

NICTA | PO Box 6020 | St Lucia QLD 4067
T +61 7 33008523 | M +61 (0)400 934 738 | F +61 7 3300 8420
www.nicta.com.au | guido.governatori@nicta.com.au


The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.


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