Re: Further work on the Use Cases and Requirements document

Thanks, Frans! The document structure looks good to me. I will start  
refining the requirements from the spreadsheet and adding descriptions  
for them in the document next week. I plan to start with the SSN  
deliverable requirements.

Thanks for pointing this out, Peter. This seems very relevant for the  
group work on Coverage related issues and should definitely be taken  
into account.

Cheers,
Alejandro


Peter Baumann <p.baumann@jacobs-university.de> escribió:

> Hi all,
>
> in the below document there is the stanza "The WG will develop a formal
> Recommendation for expressing discrete coverage data conformant to  
> the ISO 19123
> abstract model" in 2.5. As already pointed out at the joint W3C/OGC  
> meeting this
> will hinder interoperability: many different implementations of the same
> abstract model are possible, and have been done actually.
>
> But there is more: ISO is currently restructuring 19123 into
> - 19123-1, the current abstract model
> - 19123-2, the coverage implementation model
> the latter will be based verbatim on OGC 09-146r2 which establishes OGC's
> authoritative coverage model. This will be done through a fast track  
> procedure
> (ISO is convinced about the approach, based on both concepts and massive
> implementation evidence), so 19123-2 will be ISO standard on very  
> short notice.
>
> Hence, if W3C will not use OGC's adopted coverage model it will own an
> implementation model which is not interoperable with OGC, ISO, INSPIRE - in
> short: the rest of the world. Therefore, let me suggest to rephrase 2.5
> accordingly. At this stage it does not cost much yet (as usual in  
> the software
> life cycle).
>
> Just wanted to raise awareness of the issue in this group.
>
> cheers,
> Peter
>
>
>
> On 04/09/2015 04:29 PM, Frans Knibbe wrote:
>> Hello Alejandro,
>>
>> I have just made some changes to the Use Cases and Reuirements document
>> <http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html>. I have
>> not put much effort in the textual content yet because I think it is best to
>> get the structure of the document right before putting more meat on  
>> its bones.
>>
>> The main things I changed today:
>>
>>   * I have placed the deliverables in a separate chapter.
>>   * I have added a chapter that should explain the scoping process.
>>   * I have replaced the <details> and <summary> tags, which we can not use
>>     because they are not yet standard HTML, with a CSS-based solution for
>>     expanding and collapsing text.
>>   * I placed a template for use cases in a comment.
>>
>> What do you think of the document structure as it is?
>>
>> Regards,
>> Frans
>>
>> --
>> Frans Knibbe
>> Geodan
>> President Kennedylaan 1
>> 1079 MB Amsterdam (NL)
>>
>> T +31 (0)20 - 5711 347
>> E frans.knibbe@geodan.nl <mailto:frans.knibbe@geodan.nl>
>> www.geodan.nl <http://www.geodan.nl>
>> disclaimer <http://www.geodan.nl/disclaimer>
>>
>
> --
> Dr. Peter Baumann
>  - Professor of Computer Science, Jacobs University Bremen
>    www.faculty.jacobs-university.de/pbaumann
>    mail: p.baumann@jacobs-university.de
>    tel: +49-421-200-3178, fax: +49-421-200-493178
>  - Executive Director, rasdaman GmbH Bremen (HRB 26793)
>    www.rasdaman.com, mail: baumann@rasdaman.com
>    tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
> "Si forte in alienas manus oberraverit hec peregrina epistola  
> incertis ventis dimissa, sed Deo commendata, precamur ut ei reddatur  
> cui soli destinata, nec preripiat quisquam non sibi parata." (mail  
> disclaimer, AD 1083)

Received on Friday, 10 April 2015 08:51:54 UTC