Re: Further work on the Use Cases and Requirements document

Phil,

Thank you for the deliverable URI's. I am sure they will come in handy. I
have not removed the duplicated deliverable description from the UCR
document yet because that might be a good place to describe 'modifications
of intentions'.

Regards,
Frans


2015-04-10 17:13 GMT+02:00 Phil Archer <phila@w3.org>:

>
>
> On 10/04/2015 10:36, Frans Knibbe wrote:
>
>> Hello all,
>>
>> Thanks to Peter for drawing attention to the ISO 19123 issue. The text
>> about the deliverables in the draft for the Use Cases and Requirements
>> document was copied from the charter
>> <http://www.w3.org/2015/spatial/charter>. So if there is something wrong,
>> probably this bit of the charter needs to be reconsidered. Did the
>> discussion in Barcelona lead to an action item of this sort?
>>
>> We have been asked to not change the charter if possible, but this could
>> be
>> a valid reason for a small change.
>>
>
> No, sorry, I'm not allowed to edit the charter (unless you want to start
> the WG all over again ;-) ).
>
> BUT... that doesn't mean we have to produce something that, for the
> reasons Peter says, would be silly. All we do is say elsewhere - and the
> UCR doc is a good place to start, as is the WG's homepage - that we're
> modifying our intentions. In this case, there's no problem with doing that
> since the motivation is obvious. So no big deal.
>
>
>> And should the charter be changed a bit, I would like to suggest to add
>> local identifiers to the deliverables, so they will become referencable by
>> URI. That way we can link directly to the deliverable definitions.
>>
>
> Now that I am allowed to do... and have done
>
> http://www.w3.org/2015/spatial/charter#bp
> http://www.w3.org/2015/spatial/charter#time
> http://www.w3.org/2015/spatial/charter#ssn
> http://www.w3.org/2015/spatial/charter#cov
>
> all now functional.
>
> Phil
>
>
>> Regards,
>> Frans
>>
>> 2015-04-10 9:18 GMT+02:00 Peter Baumann <p.baumann@jacobs-university.de>:
>>
>>    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
>>> 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)
>>>
>>>
>>>
>>>
>>>
>>
>>
> --
>
>
> Phil Archer
> W3C Data Activity Lead
> http://www.w3.org/2013/data/
>
> http://philarcher.org
> +44 (0)7887 767755
> @philarcher1
>



-- 
Frans Knibbe
Geodan
President Kennedylaan 1
1079 MB Amsterdam (NL)

T +31 (0)20 - 5711 347
E frans.knibbe@geodan.nl
www.geodan.nl
disclaimer <http://www.geodan.nl/disclaimer>