From rickreed at tseng.co.uk  Wed Jan 17 14:49:43 2018
From: rickreed at tseng.co.uk (Rick Reed)
Date: Wed, 17 Jan 2018 14:49:43 +0000
Subject: [SDLnews] Definition of "bit_vector (0 to 31)"
References: <20180117114211.4A14837A7DF@cloud16.unlimitedwebhosting.co.uk>
Message-ID: <0A0245ED-9C59-4242-B8B9-1EF445FC510E@tseng.co.uk>



> From: moez_balti at yahoo.fr ()
> Date: 17 January 2018 at 11:42:11 GMT
> email: moez_balti at yahoo.fr
> Name: moez Balti
> 
> Please is  "bit_vector (0 to 31)" defined in sdl
> 
> Thanks

If anyone already has definition of this data type in the Specification and Description Language perhaps they could share it on sdlnews at sdl-forum.org

--
Rick Reed - rickreed at tseng.co.uk
Tel:+44 15394 88462 Mob.:+44 7970 50 96 50
Skype: rickreed_windermere (by arrangement)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sdl-forum.org/pipermail/sdlnews/attachments/20180117/058ac50a/attachment.html>

From Maxime.Perrotin at esa.int  Wed Jan 17 15:41:33 2018
From: Maxime.Perrotin at esa.int (Maxime Perrotin)
Date: Wed, 17 Jan 2018 16:41:33 +0100
Subject: [SDLnews] Definition of "bit_vector (0 to 31)"
In-Reply-To: <0A0245ED-9C59-4242-B8B9-1EF445FC510E@tseng.co.uk>
References: <20180117114211.4A14837A7DF@cloud16.unlimitedwebhosting.co.uk>
	<0A0245ED-9C59-4242-B8B9-1EF445FC510E@tseng.co.uk>
Message-ID: <CAETTRT4iP5V5OQGPOfogDwVbzX42cfHCTmb6R=b+SFNjZT8apA@mail.gmail.com>

Bit_Vector ::= BIT STRING (SIZE (32))

or

Bit_Vector ::= SEQUENCE (SIZE(32)) OF BOOLEAN

will do it, since SDL has a native support for ASN.1 types

Kind regards,
Maxime

2018-01-17 15:49 GMT+01:00 Rick Reed <rickreed at tseng.co.uk>:

>
>
> *From: *moez_balti at yahoo.fr ()
> *Date: *17 January 2018 at 11:42:11 GMT
> email: moez_balti at yahoo.fr <moez_balti at yahoo.fr>
> Name: moez Balti
>
> Please is  "bit_vector (0 to 31)" defined in sdl
>
> Thanks
>
>
> If anyone already has definition of this data type in the Specification
> and Description Language perhaps they could share it on
> sdlnews at sdl-forum.org
>
> --
> Rick Reed - rickreed at tseng.co.uk
> Tel:+44 15394 88462 <+44%2015394%2088462> Mob.:+44 7970 50 96 50
> Skype: rickreed_windermere (by arrangement)
>
>
> _______________________________________________
> SDLnews mailing list
> SDLnews at sdl-forum.org
> http://lists.sdl-forum.org/mailman/listinfo/sdlnews
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sdl-forum.org/pipermail/sdlnews/attachments/20180117/85a5bd7c/attachment.html>

From rickreed at tseng.co.uk  Wed Jan 17 16:15:59 2018
From: rickreed at tseng.co.uk (Rick Reed)
Date: Wed, 17 Jan 2018 16:15:59 +0000
Subject: [SDLnews] MailForm at sdl-forum.org - bit_vector (0 to 31) -
	more
In-Reply-To: <20180117114211.4A14837A7DF@cloud16.unlimitedwebhosting.co.uk>
References: <20180117114211.4A14837A7DF@cloud16.unlimitedwebhosting.co.uk>
Message-ID: <075F5227-7728-4CBB-AE0F-DD61761464CD@tseng.co.uk>



> On 17 Jan 2018, at 11:42, moez_balti at yahoo.fr <mailto:moez_balti at yahoo.fr> () <moez_balti at yahoo.fr <mailto:moez_balti at yahoo.fr>> wrote:
> 
> Please is  "bit_vector (0 to 31)" defined in sdl


. . .

I have done some Googling and it seems that ?BIT_VECTOR? is a VHDL data type that is defined as a BIT ?array? (in VHDL terminology) with an unknown range. 
I assume therefore that BIT_VECTOR(0 to 31) constrains the index have a maximum value of 31.

Bit is defined in SDL-2010 as follows:

VALUE TYPE Bit
INHERITS Boolean ( 0 = false, 1 = true );
  ADDING;
  OPERATORS
num ( THIS Bit ) -> Integer;
bit ( Integer) -> THIS Bit RAISE OutOfRange; 
AXIOMS
<<TYPE Bit>>num (0) == 0;
<<TYPE Bit>>num (1) == 1;
<<THIS Bit>>bit (0) == 0;
<<THIS Bit>>bit (1) == 1;
FOR ALL i IN Integer (
 i > 1 or i < 0 ==> bit(i)== RAISE OutOfRange; 
ENDVALUE TYPE Bit;

Bit

VALUE TYPE Bitstring
  OPERATORS
/*The following defines the literals allowed for Bitstring values */
      bs IN NAMECLASS
      ?''' ( (('0' OR '1')*'''B') OR ((('0':'9') OR ('A':'F'))*'''H') )-> THIS Bitstring;

/*The following operators that are the same as String except Bitstring
      is indexed from zero*/
      mkstring (Bit                                    ) -> THIS Bitstring;
      Make       (Bit                                   ) -> THIS Bitstring;
      length     ( THIS Bitstring                     ) -> Integer;
      first      ( THIS Bitstring                     ) -> Bit;
      last       ( THIS Bitstring                     ) -> Bit;
      "//"       ( THIS Bitstring, THIS Bitstring     ) -> THIS Bitstring;
      Extract  ( THIS Bitstring, Integer          ) -> Bit RAISE InvalidIndex;
      /* bs(i) in an expression expands to Extract (bs,i) the value ith element of bs*/
      Modify     ( THIS Bitstring, Integer, Bit    ) -> THIS Bitstring;
      /* bs(i) on the left hand side of an assignment is mapped to
         bs := Modify(bs, i, rhs)
         where rhs is the (Bit) expression on the assignment right hand side*/
      substring  ( THIS Bitstring, Integer, Integer   ) -> THIS Bitstring RAISE InvalidIndex;
      /* substring (s,i,j) gives a string of length j starting from the ith element */
      remove     ( THIS Bitstring, Integer, Integer   ) -> THIS Bitstring;
      /* remove (s,i,j) gives a string with a substring of length j starting from
         the ith element removed */
/*The following operators are specific to Bitstrings*/
      "not" ( THIS Bitstring                  ) ->  THIS Bitstring;
      "and" ( THIS Bitstring, THIS Bitstring  ) ->  THIS Bitstring;
      "or"  ( THIS Bitstring, THIS Bitstring  ) ->  THIS Bitstring;
      "xor" ( THIS Bitstring, THIS Bitstring  ) ->  THIS Bitstring;
      "=>"  ( THIS Bitstring, THIS Bitstring  ) ->  THIS Bitstring
      num   ( THIS Bitstring                  ) ->  Integer;
      bitstring ( Integer                    ) ->  THIS Bitstring RAISE OutOfRange;
      octet ( Integer                           ) ->  THIS Bitstring RAISE OutOfRange;
AXIOMS
. . . omitted here for brevity - see Z.104
ENDVALUE TYPE Bitstring;

The SDL-2010 data type Bitstring is therefore the equivalent of the VHDL BIT_VECTOR.

The required data type is therefore provided by the following definition:

SYNTYPE Bit_vector = Bitstring SIZE (0..32);

which uses the language defined Bitstring data type with a size constraint that the length of the string is between 0 and 32 bits.
which allows an empty string and any length up to 32 Bit elements. To exclude zero length strings change the size to 1..32.

By convention, data types in SDL-2010 usually start with a capital letter, but this is not a language rule so the name could be ?bit_vector? is preferred.

--
Rick Reed - rickreed at tseng.co.uk <mailto:rickreed at tseng.co.uk>
Tel:+44 15394 88462 Mob.:+44 7970 50 96 50
Skype: rickreed_windermere (by arrangement)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sdl-forum.org/pipermail/sdlnews/attachments/20180117/e1ce3e7f/attachment.html>

From rickreed at tseng.co.uk  Wed Jan 17 16:23:09 2018
From: rickreed at tseng.co.uk (Rick Reed)
Date: Wed, 17 Jan 2018 16:23:09 +0000
Subject: [SDLnews] MailForm at sdl-forum.org - bit_vector (0 to 31)
In-Reply-To: <527080898.8544194.1516201803670@mail.yahoo.com>
References: <20180117114211.4A14837A7DF@cloud16.unlimitedwebhosting.co.uk>
	<5F5A567F-5DAC-449F-B305-9AE734488036@tseng.co.uk>
	<527080898.8544194.1516201803670@mail.yahoo.com>
Message-ID: <E05521C1-4B67-4A5D-BE3B-92E3F10FC767@tseng.co.uk>



> On 17 Jan 2018, at 15:10, Moez Balti <moez_balti at yahoo.fr> wrote:
> 
> Thank you for your response , in fact, i try to define a bus with n bits.
> 


In which case, if it exactly 32 bits wide, I think you need to add to your model:

SYNTYPE Bit_vector32 = Bitstring SIZE (32);

and use the data type Bit_vector32.

--
Rick Reed - rickreed at tseng.co.uk
Tel:+44 15394 88462 Mob.:+44 7970 50 96 50
Skype: rickreed_windermere (by arrangement)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sdl-forum.org/pipermail/sdlnews/attachments/20180117/f9c39069/attachment-0001.html>

From rickreed at tseng.co.uk  Thu Jan 18 10:28:58 2018
From: rickreed at tseng.co.uk (Rick Reed)
Date: Thu, 18 Jan 2018 10:28:58 +0000
Subject: [SDLnews] Call for Papers SAM2018
Message-ID: <260BB6D4-63D0-4FDB-8433-3593E272C1C0@tseng.co.uk>

The Call for Papers for SAM2018 is at 
<http://sdl-forum.org/Events/SAM2018/index.htm>
as an HTML file, and at
<http://sdl-forum.org/Events/SAM2018/CfP_SAM2018.pdf>
as a PDF file.

Please circulate this to encourage your colleagues to submit a paper to SAM2018 and consider a paper yourself.

--
Rick Reed - rickreed at tseng.co.uk
Tel:+44 15394 88462 Mob.:+44 7970 50 96 50
Skype: rickreed_windermere (by arrangement)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sdl-forum.org/pipermail/sdlnews/attachments/20180118/86e6f52b/attachment.html>

From rickreed at tseng.co.uk  Sun Mar  4 14:57:09 2018
From: rickreed at tseng.co.uk (Rick Reed)
Date: Sun, 4 Mar 2018 14:57:09 +0000
Subject: [SDLnews] Society events for 2018 and 2019
Message-ID: <3543434D-78EC-423D-B42C-91BFDC47C93E@tseng.co.uk>

Dear Colleagues,

This year the SDL Forum Society event is SAM2018 and will be held in Copenhagen in October. 
For details see <http://sdl-forum.org/Events/SAM2018/index.htm <http://sdl-forum.org/Events/SAM2018/index.htm>>.

For 2019 at <http://sdl-forum.org/Events/SDL19RFP.htm <http://sdl-forum.org/Events/SDL19RFP.htm>> there is an open Request for Proposals to host SDL2019.
Normally the final decision of when/where to hold the event in the following year is made at the Society AGM during the Society event in the current year based on proposals available at that time. Therefore the decision on SDL2019 s expected to be made during SAM2018.

--
Rick Reed - rickreed at tseng.co.uk
Tel:+44 15394 88462 Mob.:+44 7970 50 96 50
Skype: rickreed_windermere (by arrangement)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sdl-forum.org/pipermail/sdlnews/attachments/20180304/6f19bf19/attachment.html>

From salvadoralcarazcarrasco at gmail.com  Mon Mar  5 17:31:10 2018
From: salvadoralcarazcarrasco at gmail.com (Salvador Alcaraz)
Date: Mon, 5 Mar 2018 18:31:10 +0100
Subject: [SDLnews] The access Control model
Message-ID: <CAOzoT7uyDen6oYKdn=qiY+5tfswTJzBZ1R3FQ7tiUPHBqn4KRg@mail.gmail.com>

do you have the complete AccessControl model used in SDL by example

Here, it is incomplete:

http://www.sdl-forum.org/Tools/TIMe/HTML/elb/sdl/sdl_t03.htm

for example, door, logDevice and others... are incomplete.

Thank you in advance.

-s
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sdl-forum.org/pipermail/sdlnews/attachments/20180305/6f84be2b/attachment.html>

From oystein.haugen at hiof.no  Mon Mar  5 20:27:57 2018
From: oystein.haugen at hiof.no (=?utf-8?B?w5h5c3RlaW4gSGF1Z2Vu?=)
Date: Mon, 5 Mar 2018 20:27:57 +0000
Subject: [SDLnews] The access Control model
In-Reply-To: <CAOzoT7uyDen6oYKdn=qiY+5tfswTJzBZ1R3FQ7tiUPHBqn4KRg@mail.gmail.com>
References: <CAOzoT7uyDen6oYKdn=qiY+5tfswTJzBZ1R3FQ7tiUPHBqn4KRg@mail.gmail.com>
Message-ID: <d76fbe1d17da43a891183ff0f46f203c@exchf01.hiof.no>

Dear Salvador
I appreciate your interest in our old example on AccessControl. It is not evident for me why you want a more complete system. All the essential elements are there. Those that are not found there are in some way trivial.

I do not think there exists any version modeled in a real tool. The diagrams you see are modeled in Framemaker originally.

Notice also that the SDL version that we were using, is not the SDL version valid today.

I am sure my co-authors of TIMe will supplement me if my memory is failing me.

Regards,
?ystein Haugen


From: sdlnews-bounces at sdl-forum.org [mailto:sdlnews-bounces at sdl-forum.org] On Behalf Of Salvador Alcaraz
Sent: 5. mars 2018 18:31
To: sdlnews at sdl-forum.org
Subject: [SDLnews] The access Control model

do you have the complete AccessControl model used in SDL by example

Here, it is incomplete:

http://www.sdl-forum.org/Tools/TIMe/HTML/elb/sdl/sdl_t03.htm
for example, door, logDevice and others... are incomplete.
Thank you in advance.
-s

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sdl-forum.org/pipermail/sdlnews/attachments/20180305/b246da59/attachment.html>

From emmanuel.gaudin at pragmadev.com  Tue Mar  6 08:39:13 2018
From: emmanuel.gaudin at pragmadev.com (Emmanuel Gaudin)
Date: Tue, 6 Mar 2018 09:39:13 +0100
Subject: [SDLnews] The access Control model
In-Reply-To: <d76fbe1d17da43a891183ff0f46f203c@exchf01.hiof.no>
References: <CAOzoT7uyDen6oYKdn=qiY+5tfswTJzBZ1R3FQ7tiUPHBqn4KRg@mail.gmail.com>
	<d76fbe1d17da43a891183ff0f46f203c@exchf01.hiof.no>
Message-ID: <1a41ebc0-90c7-2455-6ed8-df23c738f97c@pragmadev.com>

Dear Salvador,

There is an Access Control System coming as an example in PragmaDev 
Studio distribution. It is not the same one but it is executable with a 
little GUI. The example is small enough to be edited with the free 
version of Studio you can download here 
<http://www.pragmadev.com/downloads/Studio/STUDIOV5-3-1.zip>.

Regards,

Emmanuel Gaudin


Le 05/03/2018 ? 21:27, ?ystein Haugen a ?crit?:
>
> Dear Salvador
>
> I appreciate your interest in our old example on AccessControl. It is 
> not evident for me why you want a more complete system. All the 
> essential elements are there. Those that are not found there are in 
> some way trivial.
>
> I do not think there exists any version modeled in a real tool. The 
> diagrams you see are modeled in Framemaker originally.
>
> Notice also that the SDL version that we were using, is not the SDL 
> version valid today.
>
> I am sure my co-authors of TIMe will supplement me if my memory is 
> failing me.
>
> Regards,
>
> ?ystein Haugen
>
> *From:*sdlnews-bounces at sdl-forum.org 
> [mailto:sdlnews-bounces at sdl-forum.org] *On Behalf Of *Salvador Alcaraz
> *Sent:* 5. mars 2018 18:31
> *To:* sdlnews at sdl-forum.org
> *Subject:* [SDLnews] The access Control model
>
> do you have the complete AccessControl model used in SDL by example
>
> Here, it is incomplete:
>
> http://www.sdl-forum.org/Tools/TIMe/HTML/elb/sdl/sdl_t03.htm
>
> for example, door, logDevice and others... are incomplete.
>
> Thank you in advance.
>
> -s
>
>
>
> _______________________________________________
> SDLnews mailing list
> SDLnews at sdl-forum.org
> http://lists.sdl-forum.org/mailman/listinfo/sdlnews

-- 
Cyber Physical Systems simulation with FMI support in PragmaDev Studio 
latest release <http://www.pragmadev.com/product/newFeatures.html>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sdl-forum.org/pipermail/sdlnews/attachments/20180306/8b6cb9e0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: emmanuel_gaudin.vcf
Type: text/x-vcard
Size: 446 bytes
Desc: not available
URL: <http://lists.sdl-forum.org/pipermail/sdlnews/attachments/20180306/8b6cb9e0/attachment.vcf>

From rickreed at tseng.co.uk  Tue May  1 15:38:38 2018
From: rickreed at tseng.co.uk (Rick Reed)
Date: Tue, 1 May 2018 15:38:38 +0100
Subject: [SDLnews] SDLnews mailing list - failure and recovery
In-Reply-To: <5ABF5492-652A-49EE-B4E1-8CDD1C1D2EE3@tseng.co.uk>
References: <5ABF5492-652A-49EE-B4E1-8CDD1C1D2EE3@tseng.co.uk>
Message-ID: <E2A9A550-3442-44FD-AF8A-24A3EE86E0DA@tseng.co.uk>



> On 26 Apr 2018, at 23:05, Rick Reed <rickreed at tseng.co.uk> wrote:
> 
> I will notify you again when the archive has been restored and archiving is in operation again, or if it restoration of the archive was not possible.
> 
Hi,

The archive is now accessible, but this is still an issue that messages to the list are not being archived.
There has been nothing new added to the archive since March 2018.

--
Rick Reed - rickreed at tseng.co.uk
Tel:+44 15394 88462 Mob.:+44 7970 50 96 50
Skype: rickreed_windermere (by arrangement)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sdl-forum.org/pipermail/sdlnews/attachments/20180501/59c6a86c/attachment.html>

From rickreed at tseng.co.uk  Wed May  9 23:00:34 2018
From: rickreed at tseng.co.uk (Rick Reed)
Date: Wed, 9 May 2018 23:00:34 +0100
Subject: [SDLnews] Another Test - please ignore
Message-ID: <14C108E0-8014-4EAF-9563-981E4B8F5F9B@tseng.co.uk>

Another Test - please ignore
--
Rick Reed - rickreed at tseng.co.uk <mailto:rickreed at tseng.co.uk>
Tel:+44 15394 88462 Mob.:+44 7970 50 96 50
Skype: rickreed_windermere (by arrangement)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sdl-forum.org/pipermail/sdlnews/attachments/20180509/e77d42b2/attachment.html>

From amm at fct.unl.pt  Mon May 21 17:40:09 2018
From: amm at fct.unl.pt (Ana Moreira)
Date: Mon, 21 May 2018 17:40:09 +0100
Subject: [SDLnews] Call for Papers MoDRE 2018 @ RE'18
Message-ID: <CAK0=q8EuNaQ_L9+tnsK70CuEwUtm6bym_7Fk3Lx6FCJ_c1UNdQ@mail.gmail.com>

[Our apologies for multiple posts]

===========================================================================
Call for Papers
8th INT. WORKSHOP ON MODEL-DRIVEN REQUIREMENTS ENGINEERING (MoDRE)
Co-located with the 26th IEEE Int. Requirements Engineering (RE)
Conference in Banff, Canada, August 20th, 2018
                  http://www.modre2018.ece.mcgill.ca/
===========================================================================

IMPORTANT DATES

Abstract Submission : June    5th, 2018
Paper Submission    : June   12th, 2018
Author Notification : July    6th, 2018
Camera Ready Due    : July   17th, 2018
Workshop Date       : August 20th, 2018

All deadlines are 23:59:59, Anywhere on Earth (AoE) Standard Time.

ABOUT MoDRE

The 8th International Model-Driven Requirements Engineering (MoDRE) workshop
continues to provide a forum to discuss the challenges of Model-Driven
Development (MDD) for Requirements Engineering (RE). Building on the
interest
of MDD for design and implementation, RE may benefit from MDD techniques
when
properly balancing flexibility for capturing varied user needs with formal
rigidity required for model transformations as well as high-level
abstraction
with information richness. MoDRE seeks to explore those areas of
requirements
engineering that have not yet been formalized sufficiently to be
incorporated
into a model-driven development environment as well as how requirements
engineering models may benefit from emerging topics in the model-driven
community, such as flexible modeling or collaborative modeling. This
workshop
intends to identify new challenges, discuss on-going work and potential
solutions, analyze the strengths and weaknesses of MDD approaches for RE,
foster stimulating discussions on the topic, and provide opportunities to
apply MDD approaches for RE.

For more information, see the complete CFP at
   http://www.modre2018.ece.mcgill.ca/cfp.htm
or contact the organizers at modre2018-info at cs.mcgill.ca.

TOPICS

Submissions are welcome in all workshop topics including (but not limited
to)
the following:

* Modeling languages and metamodels for requirements engineering approaches.
* Modeling languages and metamodels for supporting separation of concerns in
  requirements models.
* Modeling languages and metamodels for non-functional requirements.
* Modeling languages and metamodels for requirements engineering for
specific
  domains, such as cyber-physical systems or Big Data applications.
* Synchronicity and consistency of different requirements models and views.
* Requirements models at runtime.
* Automatic analysis of requirements models.
* Automatic generation of tools for requirements engineering using MDD.
* Traceability and correctness of model transformations involving
requirements
  models.
* Empirical studies on model-driven requirements engineering.
* Simulation of requirements models. Flexible and collaborative modeling in
  requirements engineering.
* Requirements models for simplicity and complementarity.

Moreover, industry papers covering topics such as the following are highly
welcome:

* Industry problems and practices about model-driven requirements
engineering.
* Success stories about adopting model-driven requirements engineering in
  industry.
* Industrial empirical studies on model-driven requirements engineering.

SUBMISSION AND PROCEEDINGS PUBLICATION

Participants are invited to submit four kinds of papers:

(1) Full research papers with a length of eight (8) to ten (10) pages,
    reporting on findings for problems related to model-driven requirements
    engineering that are novel and improve on or analyze existing solutions.
(2) Short research papers with a length of four (4) to five (5) pages,
    reporting on initial work that may not yet have been fully developed.
(3) Position papers with a length of four (4) to five (5) pages, reporting
on
    ideas and visions for the future of model-driven requirements
engineering.
(4) Industry Papers, with a length of four (4) to ten (10) pages, describing
    experiences related to the adoption of model-driven requirements
    engineering practices in the industry or highlighting future challenges.

Accepted papers will become part of the workshop proceedings and will be
submitted for inclusion into the IEEE Digital Library.

ORGANIZING COMMITTEE
Ana Moreira, Associate Professor, Universidade Nova de Lisboa, Portugal
Gunter Mussbacher, Assistant Professor, McGill University, Canada
Jo?o Ara?jo, Assistant Professor, Universidade Nova de Lisboa, Portugal
Pablo S?nchez, Assistant Professor, Univ. de Cantabria, Spain

PROGRAM COMMITTEE
Vasco Amaral, Universidade Nova de Lisboa, Portugal
Joanne M. Atlee, University of Waterloo, Canada
Luciano Baresi, Politecnico di Milano, Italy
Nelly Bencomo, Aston University, UK
Jean-Michel Bruel, Universit? de Toulouse, France
Betty Cheng, Michigan State University, USA
Ruzanna Chitchyan, University of Bristol, UK
Jos? Mar?a Conejero, Universidad de Extremadura, Spain
Mustafa Berk Duran, McGill University, Canada
Kleinner Farias, Universidade do Vale do Rio dos Sinos (Unisinos), Brazil
Xavier Franch, University Polit?cnica de Catalunya, Spain
Martin Glinz, Universit?t Z?rich, Switzerland
Arda Goeknil, University of Luxembourg, Luxembourg
Martin Gogolla, Universit?t Bremen, Germany
Renata Guizzardi, Universidade Federal do Esp?rito Santo, Brazil
Em?lio Insfran, Universitat Polit?cnica de Val?ncia, Spain
Juan de Lara, Universidad Aut?noma de Madrid, Spain
Julio Leite, Pontif?cia Universidade Cat?lica do Rio de Janeiro, Brazil
Nicholas Matragkas, University of Hull, UK
Anna Medve, Pannon Egyetem, Hungary
John Mylopolous, Universit? di Trento, Italy
Elena Navarro, Universidad de Castilla-La Mancha, Spain
Nan Niu, University of Cincinnati, USA
Oscar Pastor, Universitat Polit?cnica de Val?ncia, Spain
Anna Perini, FBK Center for Information Technology - IRST, Italy
Alfonso Pierantonio, Universit? degli Studi dell'Aquila, Italy
Carme Quer, Universitat Polit?cnica de Catalunya - BarcelonaTech, Spain
William Robinson, Georgia State University, USA
Mehrdad Sabetzadeh, University of Luxembourg, Luxembourg
Eugene Syriani, University of Montreal, Canada
Massimo Tisi, Ecole des Mines de Nantes, France
Jose Luis de la Vara Gonz?les, Universidad Carlos III de Madrid, Spain
Antonio Vallecillo, Universidad de M?laga, Spain
Manuel Wimmer, Technische Universit?t Wien, Austria
Tao Yue, Simula Research Laboratory, Norway


-- 
NOVA LINCS / Departamento de Inform?tica
Faculdade de Ci?ncias e Tecnologia
UNIVERSIDADE NOVA DE LISBOA
Quinta da Torre, 2829 -516 Caparica, Portugal
Phone: +351 212 948 536 (ext. 10716)
Fax:  +351 212 948 541
URL: ctp.di.fct.unl.pt/~amm/

From rickreed at tseng.co.uk  Fri Aug 31 17:32:06 2018
From: rickreed at tseng.co.uk (Rick Reed)
Date: Fri, 31 Aug 2018 17:32:06 +0100
Subject: [SDLnews] ITU SG17 meeting on System Design Languages
Message-ID: <2BE3CEFF-FEA3-470E-88F7-56DE73B3B8DD@tseng.co.uk>

Dear Colleagues,

As you may be aware, ITU-T SG17 that is responsible for several language standards is currently meeting.

The part of SG17 that handles the Specification and Description Language, User Requirements Notation and TTCN-3 is meeting on the afternoon of 5th September.
At that meeting it is proposed that following are consented for the ITU-T approval process:
a new (interim revised) version of the formal definition of the Specification and Description Language;
a revised version of Z.151 for the User Requirements Notation that contains an alternative textual grammar;
updates of some of the TTCN-3 Recommendations (that simply include the ETSI TTCN standards by reference).
In addition a list of a number of minor changes to the Specification and Description Language is proposed for agreement in an update the the Z.100 Implementers? Guide.

Finally, at every ITU-T SG17 meeting a report is provided on collaboration with the SDL Forum Society.

If you an ITU-T member you can obtain the relevant documents from the ITU-T www site.

If you are an SDL Forum Society member, some of the documents have been posted on the sdl-forum.org website.

The proposed update to Z.151 for the User Requirements Notation is available via: 
http://www.sdl-forum.org/members/Downloads/sg17/2017-2020/docs-dms/c/T17-SG17-C-0347-E.htm <http://www.sdl-forum.org/members/Downloads/sg17/2017-2020/docs-dms/c/T17-SG17-C-0347-E.htm>

The updated versions of the Specification and Description Language Recommendations Z.100 to Z.107, the proposed update to the formal definition, the revised Implementers? guide, and the report  on collaboration are available via:
http://www.sdl-forum.org/members/Downloads/sg17/2017-2020/docs-dms/180829/td/plen/index.htm <http://www.sdl-forum.org/members/Downloads/sg17/2017-2020/docs-dms/180829/td/plen/index.htm>

I have not posted the TTCN-3 update documents to this site, because they simply reference the ETSI standards.
However, when the SG17 meeting has finished all the relevant TD items will be posted.

--
Rick Reed - rickreed at tseng.co.uk
Tel:+44 15394 88462 Mob.:+44 7970 50 96 50
Skype: rickreed_windermere (by arrangement)