OASIS LegalRuleML TC

 View Only
  • 1.  Multiversioning document in Akoma Ntoso

    Posted 07-25-2012 17:37
      |   view attached
    Dear all, please find the multiversioning document related to TCP C628 in Akoma Ntoso format. Find also in attachment a simple XSLT for checking the consistency between the id and idRef where the idRef have anyURI type. mp -- =================================== 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 ==================================== <?xml version="1.0" encoding="UTF-8"?> <akomaNtoso xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance" ; xsi:schemaLocation=" http://www.akomantoso.org/2.0 ./akomantoso20.xsd" xmlns=" http://www.akomantoso.org/2.0" ;> <!-- sources http://www.acma.gov.au/WEB/STANDARD/pc=PC_311151 http://www.acma.gov.au/scripts/nc.dll?WEB/STANDARD/1001/pc=PC_410421 The ACMA ??s registration of the TCP will become effective on 1 September, 2012 --> <!-- date of the document C628:2007: 2007-09-10: date of delivary of the original TCP 2008-05-19: date of registration of the TCP by ACMA. In this date the TCP becomes "code". This date is equivalent to the enter in force date 2008-05-19: commencement of efficacy --> <!-- date of the document C628:2012: 2012-05-30: date of delivary of the original TCP 2008-07-11: date of registration of the TCP by ACMA. In this date the TCP becomes "code". This date is equivalent to the enter in force date 2012-09-01: commencement of efficacy --> <act> <meta> <identification source="#palmirani"> <FRBRWork> <FRBRthis value="/au/2007-09-10/C628/main"/> <FRBRuri value="/au/2007-09-10/C628/"/> <!-- date of creation of this work = date of the original document --> <FRBRdate date="2007-09-10" name="Creation"/> <FRBRauthor href="#cal" as="#author"/> <FRBRauthor href="#acma" as="#authority"/> <componentInfo> <componentData id="wmain" href="#emain" name="main" showAs="Main document"/> <componentData id="wannex1" href="#eannex1" name="annex1 " showAs="Role and Obligations of Communications Compliance"/> <componentData id="wannex2" href="#eannex2" name="annex2" showAs="FLOWCHART"/> </componentInfo> <FRBRcountry value="au"/> </FRBRWork> <FRBRExpression> <FRBRthis value="/au/2007-09-10/C628/main/eng@2012-09-01/main"/> <FRBRuri value="/au/2007-09-10/C628/eng@2012-09-01"/> <FRBRalias value="/au/2007-09-10/C628/eng@"/> <!-- date of creation of the current expression= date of creation of this new version of the legal coordinated text --> <FRBRdate date="2012-07-11" name="Expression"/> <FRBRauthor href="#cal" as="#author"/> <componentInfo> <componentData id="emain" href="#mmain" name="main" showAs="Main document"/> <componentData id="eannex1" href="#mannex1" name="annex1 " showAs="Role and Obligations of Communications Compliance"/> <componentData id="eannex2" href="#mannex2" name="annex2" showAs="FLOWCHART"/> </componentInfo> <FRBRlanguage language="eng"/> </FRBRExpression> <FRBRManifestation> <FRBRthis value="/au/2007-09-10/C628/main/eng@2012-09-01/main.xml"/> <FRBRuri value="/au/2007-09-10/C628/main/eng@2012-09-01.akn"/> <!-- date of creation of this manifestation= date of creation of this xml file --> <FRBRdate date="2012-07-25" name="XML-formalization"/> <FRBRauthor href="#athan" as="#editor"/> <FRBRauthor href="#palmirani" as="#editor"/> <componentInfo> <componentData id="mmain" href="/au/2007-09-10/C628/main/eng@2012-09-01/main.xml" name="main" showAs="Main document"/> <componentData id="mannex1" href="/au/2007-09-10/C628/main/eng@2012-09-01/annex1.xml" name="annex1 " showAs="Role and Obligations of Communications Compliance"/> <componentData id="mannex2" href="/au/2007-09-10/C628/main/eng@2012-09-01/annex2.xml" name="annex2" showAs="FLOWCHART"/> </componentInfo> <FRBRformat value="xml"/> </FRBRManifestation> </identification> <lifecycle source="#palmirani"> <eventRef id="e1" date="2008-05-19" source="#ro1" refersTo="#efficacy" type="generation"/> <!-- the new version will enter in efficacy at 1 September 2012 so the event that produces the new version is 1 Sept. 2012 --> <eventRef id="e2" date="2008-07-11" source="#ra1" refersTo="#inforce" type="generation"/> <eventRef id="e3" date="2012-09-01" source="#ra1" refersTo="#efficacy" type="amendment"/> </lifecycle> <workflow source="#palmirani"> <step date="2008-05-19" actor="#acma" refersTo="#registered" outcome="#approvedWithoutModifications" href="/au/2007-09-10/C628/main/eng@/main"/> <step date="2012-07-11" actor="#acma" refersTo="#registered" outcome="#approvedWithoutModifications" href="/au/2007-09-10/C628/main/eng@2012-09-01/main"/> </workflow> <analysis source="#palmirani"> <passiveModifications> <textualMod type="substitution" id="pm1"> <source href="#sec2.1-v2"/> <destination href="#sec2.1-v1"/> </textualMod> <textualMod type="renumbering" id="pm2"> <source href="#sec2.1-v2"/> <destination href="#sec2.2-v1"/> </textualMod> </passiveModifications> </analysis> <temporalData source="#palmirani"> <temporalGroup id="t1"> <timeInterval refersTo="#inforce" start="#e1" end="#e2"/> <timeInterval refersTo="#efficacy" start="#e1" end="#e3"/> </temporalGroup> <temporalGroup id="t2"> <timeInterval refersTo="#inforce" start="#e2"/> <timeInterval refersTo="#efficacy" start="#e3"/> </temporalGroup> </temporalData> <references source="#palmirani"> <original id="ro1" href="/au/2007-09-10/C628/main" showAs="TELECOMMUNICATIONS CONSUMER PROTECTIONS CODE"/> <activeRef id="ra1" href="/au/2012-05-30/cal/C628/main" showAs="TELECOMMUNICATIONS CONSUMER PROTECTIONS CODE by CAL"/> <hasAttachment id="annex1" href="/au/2007-09-10/C628/main/annex1" showAs="Role and Obligations of Communications Compliance"/> <hasAttachment id="annex2" href="/au/2007-09-10/C628/main/annex2" showAs="FLOWCHART"/> <TLCPerson id="athan" href="/ontology/persons/akn/athan" showAs="Athan"/> <TLCPerson id="palmirani" href="/ontology/persons/akn/athan" showAs="palmirani"/> <TLCRole id="editor" href="/ontology/roles/editor" showAs="Editor"/> <TLCRole id="author" href="/ontology/roles/author" showAs="Author"/> <TLCRole id="authority" href="/ontology/roles/authority" showAs="Authority"/> <TLCConcept id="complaint" href="/ontology/concepts/complaint" showAs="Complaint"/> <TLCProcess id="registered" href="/ontology/process/registered" showAs="Registered"/> <TLCConcept id="approvedWithoutModifications" href="ontology/concepts/approved" showAs="Approved"/> <TLCConcept id="industryCode" href="ontology/concepts/industryCode" showAs="Industry Code"/> <TLCConcept id="dateDelivery" href="ontology/concepts/dateDelivery" showAs="Date of Delivery"/> <TLCOrganization id="cal" href="/ontology/organizations/communicationsAlliance" showAs="Communications Alliance Ltd"/> <TLCOrganization id="acma" href="/ontology/organizations/acma" showAs="ACMA"/> <TLCConcept id="efficacy" href="/ontology/process/registered" showAs="Efficacy"/> <TLCConcept id="inforce" href="/ontology/process/inforce" showAs="Inforce"/> </references> </meta> <preface> <p> <docType refersTo="#industryCode">INDUSTRY CODE</docType> </p> <p> <docTitle>TELECOMMUNICATIONS CONSUMER PROTECTIONS CODE</docTitle> </p> <p> <docNumber period="#t1">C628:2007</docNumber> <docNumber period="#t2">C628:2012</docNumber> </p> <p> <docDate date="2007-09-10" period="#t1" refersTo="#dateDelivery">Sept 2007</docDate> <docDate date="2012-05-30" period="#t2" refersTo="#dateDelivery">MAY 2012</docDate> </p> </preface> <preamble> <container id="cnt1" name="content" period="#t1"> <block name="cnt1-blc1" class="title">INTRODUCTORY STATEMENT</block> <p>The Telecommunications Consumer Protections Code (TCP) Code (C628:2007) replaces the following registered ACIF codes: <omissis/> </p> </container> <container id="cnt2" name="content" period="#t2"> <block name="cnt1-blc1" class="title">INTRODUCTORY STATEMENT</block> <p>This Communications Alliance Telecommunications Consumer Protections (TCP) Code is a code of conduct designed to ensure good service and fair outcomes for all Consumers of Telecommunications Products in Australia. All Carriage Service Providers who supply Telecommunications Products to Customers in Australia are required to observe and comply with the Code.</p> <p>The Code is registered by the Australian Communications and Media Authority (ACMA), which has appropriate powers of enforcement. Compliance with the Code is monitored by Communications Compliance (CC).</p> </container> </preamble> <body> <!-- Title 2 in the version of 2007--> <title id="tit1-v1" period="#t1" evolvingId="tit1"> <num> 2</num> <heading>ACRONYMS, DEFINITIONS AND INTERPRETATIONS</heading> <section id="sec2.1-v1" evolvingId="sec2.1"> <num>2.1</num> <heading>Acronyms</heading> <content> <p> <omissis/> </p> </content> </section> <section id="sec2.2-v1" evolvingId="sec2.2"> <num>2.2</num> <heading>Definitions</heading> <content> <blockList id="sec2.2-list1-v1"> <listIntroduction>For the purposes of this Code: <omissis>items 1- 30 are omitted</omissis> </listIntroduction> <item id="sec2.2-list1-itm24-v1"> <blockList id="sec2.2-list1-itm24-list1-v1"> <listIntroduction> <def refersTo="#complaint" class="definition">Complaint</def> means an expression of dissatisfaction made to Supplier in relation to: </listIntroduction> <item id="sec2.2-list1-itm24-list1-itma-v1"> <num>(a) </num> <p>carrying on business as a Carrier;</p> </item> <item id="sec2.2-list1-itm24-list1-itmb-v1"> <num>(b) </num> <p> carrying on business as a Carriage Service Provider;</p> </item> <item id="sec2.2-list1-itm24-list1-itmc-v1"> <num>(c) </num> <p> supplying a content service using a Listed Carriage Service ; and/or</p> </item> <item id="sec2.2-list1-itm24-list1-itmd-v1"> <num>(d) </num> <p>supplying a Telecommunications Product</p> </item> </blockList> </item> </blockList> </content> </section> </title> <!-- Title 2 in the version of 2012--> <title id="tit1-v2" period="#t2" evolvingId="tit1"> <num> 2</num> <heading>DEFINITIONS AND INTERPRETATION</heading> <section id="sec2.1-v2"> <num>2.1</num> <heading>Definitions</heading> <content> <blockList id="sec2.1-list1-v2" evolvingId="sec2.2"> <listIntroduction>For the purposes of this Code: <omissis>items 1- 30 are omitted</omissis> </listIntroduction> <item id="sec2.1-list1-itm31-v2"> <heading>Complaint</heading> <p id="sec2.1-list1-itm31-par1-v2"> <def refersTo="#complaint" class="definition">Complaint</def> means <span id="defn-complaint">an expression of dissatisfaction made to a Supplier in relation to its Telecommunications Products or the complaints handling process itself, where a response or Resolution is explicitly or implicitly expected by the Consumer</span>.</p> <p id="sec2.1-list1-itm31-par2"> <span id="sec2.1-list1-itm31-par2-snt1-v2">An initial call to a provider to request a service or information or to request support is not necessarily a Complaint.</span> <span id="sec2.1-list1-itm31-par2-snt2-v2">An initial call to report a fault or service difficulty is not a Complaint.</span> <span id="sec2.1-list1-itm31-par2-snt3-v2">However, if a Customer advises that they want this initial call treated as a Complaint, the Supplier will also treat this initial call as a Complaint.</span> </p> <p id="sec2.1-list1-itm31-par3-v2">If a Supplier is uncertain, a Supplier must ask a Customer if they wish to make a Complaint and must rely on the Customer ??s response.</p> </item> </blockList> </content> </section> </title> </body> </act> </akomaNtoso> <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl=" http://www.w3.org/1999/XSL/Transform" ; version="2.0"> <xsl:output method="html" encoding="UTF-8"/> <xsl:template match="/"> <html> <head> <title>Check Akoma Ntoso</title> </head> <body> <xsl:call-template name="EmptySource"/> <xsl:call-template name="BlockListSenzalistIntro"/> <xsl:call-template name="ListSenzaIntro"/> <xsl:call-template name="SectionSenzaNum"/> <xsl:call-template name="SectionSenzaNumDebate"/> <xsl:call-template name="SectionSenzaNumReport"/> <xsl:call-template name="bb"/> <xsl:call-template name="MappaId"/> <xsl:call-template name="ReferenceSenzaCall"/> </body> </html> </xsl:template> <xsl:template name="EmptySource"> <h1>EmptySource</h1> <xsl:for-each select="//@*[string(.)='']"> <p>&lt;<xsl:value-of select="."/> --<xsl:value-of select="name()"/> <span style="background-color:green; color:white; font-weight:bold;"> -- contenuto vuoto.</span> </p> </xsl:for-each> </xsl:template> <xsl:template name="BlockListSenzalistIntro"> <h1>BlockList Senza listIntroduction</h1> <xsl:for-each select="//blockList[not(listIntroduction)]"> <p>&lt;<xsl:value-of select="name()"/> -- id='<xsl:value-of select="./@id"/> <span style="background-color:red; color:white; font-weight:bold;"> -- senza listIntroduction.</span> </p> </xsl:for-each> </xsl:template> <xsl:template name="ListSenzaIntro"> <h1>List Senza intro</h1> <xsl:for-each select="//list[not(intro)]"> <p>&lt;<xsl:value-of select="name()"/> -- id='<xsl:value-of select="./@id"/> <span style="background-color:red; color:white; font-weight:bold;"> -- senza listIntroduction.</span> </p> </xsl:for-each> </xsl:template> <xsl:template name="bb"> <h1>Bold bold</h1> <xsl:for-each select="//b/b"> <p>&lt;<xsl:value-of select="name(.)"/> <span style="background-color:red; color:white; font-weight:bold;"> -- bold in bold</span> </p> </xsl:for-each> </xsl:template> <xsl:template name="SectionSenzaNum"> <h1>Hcontainer senza num</h1> <xsl:for-each select="//body/*[not(num) and .//content]"> <p>&lt;<xsl:value-of select="name(.)"/> -- id='<xsl:value-of select="./@id"/>'&gt; non contiene &lt;num&gt; </p> <span style="background-color:red; color:white; font-weight:bold;"> -- occhio che manca il num</span> </xsl:for-each> </xsl:template> <xsl:template name="SectionSenzaNumDebate"> <h1>Hcontainer senza num nei debate</h1> <xsl:for-each select="//debateBody/*[not(num) and .//content]"> <p>&lt;<xsl:value-of select="name(.)"/> -- id='<xsl:value-of select="./@id"/>'&gt; non contiene &lt;num&gt; </p> <span style="background-color:red; color:white; font-weight:bold;"> -- occhio che manca il num</span> </xsl:for-each> </xsl:template> <xsl:template name="SectionSenzaNumReport"> <h1>Hcontainer senza num nei report</h1> <xsl:for-each select="//mainBody/*[not(num) and .//content]"> <p>&lt;<xsl:value-of select="name(.)"/> -- id='<xsl:value-of select="./@id"/>'&gt; non contiene &lt;num&gt; </p> <span style="background-color:red; color:white; font-weight:bold;"> -- occhio che manca il num</span> </xsl:for-each> </xsl:template> <xsl:template name="MappaId"> <h1>Mappa degli id senza Reference</h1> <xsl:for-each select="//@*[starts-with(string(.),'#')]"> <xsl:variable name="io" select="."/> <xsl:variable name="val" select="//*[@id=substring-after(string($io),'#')]"/> <p> <xsl:value-of select="$io"/> <span style="background-color:white; color:black; font-weight:bold;"> -- </span> <xsl:value-of select="name()"/> <xsl:if test="not($val)"> <span style="background-color:red; color:white; font-weight:bold;"> -- non esiste questo id...</span> </xsl:if> </p> </xsl:for-each> </xsl:template> <xsl:template name="ReferenceSenzaCall"> <h1>Reference Senza Call</h1> <xsl:for-each select="//*[@showAs and @href and @id and not(@name)]"> <xsl:variable name="io" select="@id"/> <xsl:variable name="val" select="//*[@refersTo=concat('#',string($io)) or @source=concat('#',string($io)) or @as=concat('#',string($io)) or @outcome=concat('#',string($io)) or @href=concat('#',string($io)) or @by=concat('#',string($io))]"/> <p> <xsl:value-of select="$io"/> <xsl:value-of select="@refersTo"/> <xsl:if test="not($val)"> <span style="background-color:blue; color:white; font-weight:bold;"> -- questa reference non ha chiamate..</span> </xsl:if> </p> </xsl:for-each> </xsl:template> <xsl:template match="@* text()"/> <xsl:template match="*"> <xsl:apply-templates select="@*"/> <xsl:apply-templates select="*"/> </xsl:template> </xsl:stylesheet>

    Attachment(s)



  • 2.  LegalRuleML namespace

    Posted 07-29-2012 16:17
    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


  • 3.  Re: [legalruleml] LegalRuleML namespace

    Posted 07-29-2012 16:54
    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 -- Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/people/staff/robin-cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783


  • 4.  Re: [legalruleml] LegalRuleML namespace

    Posted 08-01-2012 13:15
    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 ====================================


  • 5.  Re: [legalruleml] LegalRuleML namespace

    Posted 08-01-2012 13:59
    +1 On Wed, Aug 1, 2012 at 9:14 AM, monica.palmirani < monica.palmirani@unibo.it > wrote: 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 -- CEO CheckMi President BTUSAR Dive Team Producer Shore Adventure Cell (usa) (732) 497-CARL {2275} CarlMattocks@CheckMi.com Information Risk Checks > Secure Continuous Service


  • 6.  Re: [legalruleml] LegalRuleML namespace

    Posted 08-01-2012 14:28
    +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 >


  • 7.  Re: [legalruleml] LegalRuleML namespace

    Posted 08-01-2012 19:21
    +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.


  • 8.  Re: [legalruleml] LegalRuleML namespace

    Posted 08-01-2012 19:46
    I am neutral on slash versus slashless. I see no case where this namespace IRI will be used as a base IRI, but there is no harm to having a trailing slash. As to the versioning information, using the full version number in the namespace means that the possibility for backward compatibility is lost whenever the version number is changed (because the namespace of any existing LegalRuleML document would have to be changed to comply with the schema of the new version). If that is an acceptable situation, then I would be OK with the proposed namespace. Tara On 8/1/2012 3:20 PM, Guido Governatori wrote: +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. --------------------------------------------------------------------- To unsubscribe, e-mail: legalruleml-unsubscribe@lists.oasis-open.org For additional commands, e-mail: legalruleml-help@lists.oasis-open.org


  • 9.  R: [legalruleml] LegalRuleML namespace

    Posted 08-01-2012 19:55
    +1 for http://docs.oasis-open.org/legalruleml/ns/v1.0/ Cheers Nino 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. --------------------------------------------------------------------- To unsubscribe, e-mail: legalruleml-unsubscribe@lists.oasis-open.org For additional commands, e-mail: legalruleml-help@lists.oasis-open.org