Regards
Adrian Zoicas
Mobile Competence Centre (MCC),
ETSI
Phone: +33 (0)4
92 94 42 21
Mobile:
+33 (0)6 74 40 83 72
Fax: +33 (0)4 92 38 52 21
mailto: adrian.zoicas@etsi.org
http://www.etsi.org
http://www.3gpp.org
-----Original Message-----
From: Adrian Zoicas [mailto:Adrian.Zoicas@etsi.org]
Sent: den 5 juli 2005 15:17
To: Thomas Tovinger (LN/EAB); Ultan Mulligan; Peng Dai (SH/RDC); John M Meredith
Cc: istvan.aba@t-mobile.at; Robert Petersen (LI/EAB); Edwin Tse (QA/EMC); J.Schmidt@MOTOROLA.COM; toche@nortel.com; Mike Truss; lariven@nortelnetworks.com; Frédéric Bonneau
Subject: RE: SA5 request for name space for SOAP SSThomas,you are mixing ETSI with 3GPP issues.You have the 3GPP specs twice onceon the 3GPP site and 2nlytransposed as ETSI TS e.g. 132.101 on the ETSI site.The XML schema is only on the 3GPP web site.Not Ultan but JMM is in charge of the 3GPP site and its transposition in ETSI.Regards
Adrian Zoicas
Mobile Competence Centre (MCC), ETSI
Phone: +33 (0)4 92 94 42 21
Mobile: +33 (0)6 74 40 83 72
Fax: +33 (0)4 92 38 52 21
mailto: adrian.zoicas@etsi.org
http://www.etsi.org
http://www.3gpp.org
From: Thomas Tovinger (LN/EAB) [mailto:thomas.tovinger@ericsson.com]
Sent: 05 July 2005 15:06
To: Ultan Mulligan; Adrian Zoicas; Peng Dai (SH/RDC); John M Meredith
Cc: istvan.aba@t-mobile.at; Robert Petersen (LI/EAB); Edwin Tse (QA/EMC); J.Schmidt@MOTOROLA.COM; toche@nortel.com; Mike Truss; lariven@nortelnetworks.com; Fr¨¦d¨¦ric Bonneau
Subject: RE: SA5 request for name space for SOAP SSThanks for this clarification, Ultan.(If this response appears to be "late" it's because I am writing this from an offline location, and once it is sent, this afternoon, I guess that some other responses in the same thread may have arrived already...)Thus, I think we need to ask for your help to set up such a namespace for these new specifications.Possibly we can reuse the same namespace as we already have (or do we?) for the existing 32.6x5 TSs.If we use the option described below, to have a namespace based on specification number, maybe that would be fine for all the SA5 XML specifications. Otherwise we can use a namespace based on technical domain. I am sure that Frederic and Dai Peng could advise us on what is the best solution.But I am puzzled by your statement (Ultan) that "As far as I'm aware, there is no defined 3GPP namespace for XML documents." - we do have a namespace defined in our SA5 specs (see examples below), it's just if it has been correctly allocated in the 3GPP adm. handling. Since Adrian Zoicas has supported us in that, I absolutely thought this was the case (one per 32.6x5 spec). Otherwise we have to sort that out as well! And if this is correctly made so far, can't we just continue in the same way since each SA5 XML specification will have the need for its own namespace? And as you say that for this case, each such namespace is assigned automatically every time a new specification number is issued, then it should be easy to handle for the new SOAP SS-related specs as well, or? I must admit that I don't understand how much is automatic and manually handled by MCC support here - Adrian has said to us that we need to ask you Ultan or John M to provide the new namespaces, but the description below tells me that it is fully automatic once it is set up in a good way. Don't we have the same procedures for this in ETSI and 3GPP?Here are examples of namespace declarations inside our 32.6x5 specs (32.615 in this case) - and the archive folders stated there do exist on the 3GPP server:<schema
targetNamespace=
"http://www.3gpp.org/ftp/specs/archive/32_series/32.615#configData"
elementFormDefault="qualified"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:xn=
"http://www.3gpp.org/ftp/specs/archive/32_series/32.625#genericNrm"
xmlns:cn=
http://www.3gpp.org/ftp/specs/archive/32_series/32.635#coreNrm
........BR/ Thomas-----Original Message-----
From: Ultan Mulligan [mailto:Ultan.Mulligan@etsi.org]
Sent: den 4 juli 2005 12:14
To: Adrian Zoicas; Peng Dai (SH/RDC); John M Meredith
Cc: istvan.aba@t-mobile.at; Robert Petersen (LI/EAB); Edwin Tse (QA/EMC); J.Schmidt@MOTOROLA.COM; toche@nortel.com; Thomas Tovinger (LN/EAB); Mike Truss; lariven@nortelnetworks.com; Frédéric Bonneau
Subject: RE: SA5 request for name space for SOAP SSHello,As far as I'm aware, there is no defined 3GPP namespace for XML documents. If one needs to be defined (and it seems this is the case), the person who would manage such a process would be John Meredith of the MCC. I would strongly recommend not to allow individual working groups define their own namespace in an un-coordinated manner, and defining something such as http://www.3GPP.org/NotificationIRP without identifying the context in which it is used.At ETSI, we do have such a namespace, which could be used as a model for the 3GPP one. Our namespace is very similar to our ASN.1 OID namespace. It is split in 3 sections:A namespace based on specification number:Since each specification number at ETSI is unique, this forms an ideal basis for a namespace. And since each specification is owned and managed by only one technical committee, there is limited scope for conflict within the namespace. Each such namespace is assigned automatically every time a new specification number is issued, and the ETSI secretariat does not track if the namespace is ever used in the specification. The technical body owning the specification is entirely responsible for managing the namespace under the specification number: adding version or release numbers as it requires.A namespace based on technical domainThis is assigned on request from a technical committee, usually when the same namespace needs to be used across a series of specifications. Such a namespace is again managed entirely by the technical committee, who should define policies for version or release numbering etc. ETSI simply registers the allocation of the top-level namespace, and leaves the rest for the committee.A namespace for company namesAny company, whether or not a member of ETSI, can request to have a namespace allocated to them for free. This is probably not so useful, but it is available.You can find further information at:andI'm happy to help 3GPP and MCC to set up such a namespace if this is required.Best regardsUltan Mulligan__________________________________________________
Ultan Mulligan
Protocol & Testing Competence Centre (PTCC)
ETSI
F-06921 Sophia Antipolis Cedex
Tel: +33 4 92 94 43 88 Mobile: +33 6 87 80 28 08
Fax: + 33 4 92 38 52 88
mailto:ultan.mulligan@etsi.org
PTCC Helpdesk e-mail: mailto:ptcchelp@etsi.org
PTCC Web Pages: http://www.etsi.org/ptcc/
_______________________________________
ETSI web-page: http://www.etsi.org
ETSI infocentre: mailto:infocentre@etsi.org
From: Adrian Zoicas
Sent: Monday, July 04, 2005 11:51 AM
To: Peng Dai (SH/RDC); Ultan Mulligan
Cc: istvan.aba@t-mobile.at; Robert Petersen (LI/EAB); Edwin Tse (QA/EMC); J.Schmidt@MOTOROLA.COM; toche@nortel.com; Thomas Tovinger (LN/EAB); Mike Truss; lariven@nortelnetworks.com; Fr¨¦d¨¦ric Bonneau
Subject: RE: SA5 request for name space for SOAP SSOur ETSI expert on this isUltan MulliganI am adding to this reply.Regards
Adrian Zoicas
From: Peng Dai (SH/RDC) [mailto:peng.dai@ericsson.com]
Sent: 04 July 2005 11:46
To: Adrian Zoicas
Cc: istvan.aba@t-mobile.at; Robert Petersen (LI/EAB); Edwin Tse (QA/EMC); J.Schmidt@MOTOROLA.COM; toche@nortel.com; Thomas Tovinger (LN/EAB); Mike Truss; lariven@nortelnetworks.com; Fr¨¦d¨¦ric Bonneau
Subject: RE: SA5 request for name space for SOAP SSHi, Adrian:Thanks for quick response.One quick feeling is that it's better to seperate the publication of XML Schema and WSDL file since they are different.And it's better to have a document to mention the rule of XML namespace defintion as:http://www.3gpp.org/ftp/specs/latest/[release version]/[series number]/[specficaiton number]Maybe the "ftp/specs/latest/" is not necessary in my own opinion.It seems no document version information is included in the XML namesapce according the below mail, shall we have further discussion on it ?Best Regards
Dai Peng-----Original Message-----
From: Adrian Zoicas [mailto:Adrian.Zoicas@etsi.org]
Sent: 2005Äê7ÔÂ4ÈÕ 16:56
To: Adrian Zoicas; Peng Dai (SH/RDC)
Cc: istvan.aba@t-mobile.at; Robert Petersen (LI/EAB); Edwin Tse (QA/EMC); J.Schmidt@MOTOROLA.COM; toche@nortel.com; Thomas Tovinger (LN/EAB); Mike Truss; lariven@nortelnetworks.com; Fr¡§¦d¡§¦ric Bonneau
Subject: RE: SA5 request for name space for SOAP SSthe attachment.
<<S5-040517 Procedure for XML schema electronic files publication.zip>>
_____________________________________________
From: Adrian Zoicas
Sent: 04 July 2005 10:53
To: 'Peng Dai (SH/RDC)'
Cc: istvan.aba@t-mobile.at; Robert Petersen (LI/EAB); Edwin Tse (QA/EMC); J.Schmidt@MOTOROLA.COM; toche@nortel.com; Thomas Tovinger (LN/EAB); Mike Truss; Suz¨¨le Lariven (lariven@nortelnetworks.com); Fr¨¦d¨¦ric BonneauSubject: RE: SA5 request for name space for SOAP SS
Dear Dai Peng,
I wonder if for this we should use the same procedure as for the XML schema extractions (32.3/6x5). See below & attachment.
=============
Annex A (normative):
Configuration data file base XML schema (file name "notificationLog.xsd")
<?xml version="1.0" encoding="UTF-8"?>
<!--
3GPP TS 32.335 Notification Log IRP
The 3GPP Notification Log IRP XML Solution Definition, Schema Definition
notificationLog.xsd
--><schema
targetNamespace="http://www.3gpp.org/ftp/specs/latest/rel-6/32_series/32335#notifLog" elementFormDefault="qualified"
attributeFormDefault="unqualified"
¡.
</element>
</schema>Annex C (informative):
NL IRP XML schema electronic files
The electronic files corresponding to the normative XML schemas defined in the present document are available in native form in the following archive:http://www.3gpp.org/ftp/specs/archive/32_series/32.335/schema/326335-600-XMLSchema.zip
=======================Regards
Adrian Zoicas
Mobile Competence Centre (MCC), ETSI
Phone: +33 (0)4 92 94 42 21
Mobile: +33 (0)6 74 40 83 72
Fax: +33 (0)4 92 38 52 21
mailto: adrian.zoicas@etsi.org
http://www.etsi.org
http://www.3gpp.org
-----Original Message-----
From: Peng Dai (SH/RDC) [mailto:peng.dai@ericsson.com]
Sent: 04 July 2005 08:11
To: Adrian Zoicas; istvan.aba@t-mobile.at; Robert Petersen (LI/EAB); Edwin Tse (QA/EMC); J.Schmidt@MOTOROLA.COM; toche@nortel.com; Thomas Tovinger (LN/EAB); Mike TrussSubject: RE: SA5 request for name space for SOAP SS
Hi, guys:
Sorry for late response, actually I left Sophia in Thursday afternoon.
I would say we need to check the following points:
1. Does 3GPP has some strategy or rule for the XML Namespace definition ?
The current proposal in the attatched document is:Prefix Namespace
basicCMIRP http://www.3GPP.org/BasicCMIRP
genericIRP http://www.3GPP.org/ManagedGenericIRP
kernelCMIRP http://www.3GPP.org/kernelCMIRP
ntfIRP http://www.3GPP.org/NotificationIRP2. Does 3GPP has some strategy or rule to put the version information into XML Namespace ?
For example: basicCMIRP http://www.3GPP.org/BasicCMIRP/Rel6/0.2.13. Does 3GPP has some strategy or rule for the Namespace prefix definition ?
For example: basicCMIRPThanks a lot.
<<S5-056433r1 Notification IRP SOAP SS.zip>> <<S5-056432r1 Kernel CM IRP SOAP SS.zip>> <<S5-056431r1 Basic CM IRP SOAP SS.zip>> <<S5-056434r1 Generic IRP SOAP SS.zip>>
Best Regards
Dai Peng
-----Original Message-----
From: Adrian Zoicas [mailto:Adrian.Zoicas@etsi.org]
Sent: 2005?6?30? 22:17
To: istvan.aba@t-mobile.at; Peng Dai (SH/RDC); Robert Petersen (LI/EAB); Edwin Tse (QA/EMC); J.Schmidt@MOTOROLA.COM; toche@nortel.com; Thomas Tovinger (LN/EAB); Mike TrussSubject: SA5 request for name space for SOAP SS
Importance: High
Please provide your request
&
attach the draft TSs.
Regards
Adrian Zoicas
Mobile Competence Centre (MCC), ETSI
Phone: +33 (0)4 92 94 42 21
Mobile: +33 (0)6 74 40 83 72
Fax: +33 (0)4 92 38 52 21
mailto: adrian.zoicas@etsi.org
http://www.etsi.org
http://www.3gpp.org
<< File: S5-040517 Procedure for XML schema electronic files publication.zip >>