OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emix message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [emix] Re: reference and use of GML artifacts [Re: http://tools.oasis-open.org/issues/browse/EMIX-477]


I would like to echo this.  By way of example, both the IEC 61968-100 CD (which covers JMS and web services integration for CIM) and various MultiSpeak schemas, the namespace does not point to any specific artifact or resource.

 

From: Toby Considine [mailto:tobyconsidine@gmail.com] On Behalf Of Toby Considine
Sent: Thursday, June 23, 2011 8:42 AM
To: emix@lists.oasis-open.org
Subject: RE: [emix] Re: reference and use of GML artifacts [Re: http://tools.oasis-open.org/issues/browse/EMIX-477]

 

As I have stated here before, and to you in conversation, the document declaring profiles produced by the OGC states that to use that profile, you use that text in the appinfo.  AppInfo is not part of a schema – it is documentation. You could put nursery rhymes there.

 

Now an application that is specially written to consume the AppInfo could do something with that, perhaps automate conformance processing. That would not be a standards compliant or required app, although it would be useful. Still, the GML specifications states, to declare profiles include this line.

 

I would hazard a guess that the majority of market contexts that will be created in the next year will not be resolvable. This is not a problem, even though they are of the format AnyURI. It may be a problem under given market rules, but EMIX cannot, may not define markets or market rules.

 

Now as to whether the OGC should change their specifications to mandate a different URL, or put schema hints at the location named, that is entirely out of scope. I forwarded these concerns to them months ago. Based on their [lack of] response, it does not appear to be a priority for that organization. If that changes, if the OGC suddenly publishes that you will get automated CAM processing , say, or perhaps Schematron assertions, if you only point to 3.2.1.7, than I will welcome that. It would be handled, even in the absence of ongoing technical work of the TC as a technical correction to maintain conformance with other bodies of work.

 

Until such time, it is just a string that happens to look like an URL, in a portion of the schema that is ignored by standard schema processing, as specified in the w3 XML schema specifications. Content placed there *may* have meaning. I refer you to http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures.html#element-appinfo if you are interested. I also refer you to http://www.w3.org/XML/SchemaZ for a list of XML tools, in which you can find that while many tools use the information in AppInfo, each tends to use it for quite different purposes.

 

So:

-          The AppInfo documentation element is of legal form

-          It is of the content mandated in the GML Profile specifications

-          It does not point anywhere

 

 

tc

 

 

 

 

 


"He who fights with monsters should look to it that he himself does not become a monster, and if you stare long into an abyss, the abyss also stares into you."   - Fredrich Nietzche


Toby Considine
TC9, Inc

TC Chair: oBIX & WS-Calendar

TC Editor: EMIX, EnergyInterop

U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee

  

Email: Toby.Considine@gmail.com
Phone: (919)619-2104

http://www.tcnine.com/
blog: www.NewDaedalus.com

 

 

From: Anne Hendry [mailto:ahendry@pacbell.net]
Sent: Thursday, June 23, 2011 3:07 AM
To: Considine, Toby (Campus Services IT)
Cc: emix@lists.oasis-open.org
Subject: Re: [emix] Re: reference and use of GML artifacts [Re: http://tools.oasis-open.org/issues/browse/EMIX-477]

 

Hi Toby,

I simply opened up emix.xsd and clicked on the first link under 'Core EMIX objects':
<!-- 1.0 Core EMIX objects-->
−<xs:annotation>
−<xs:appinfo source="http://schemas.opengis.net/gml/3.2.1/profiles/gmlsfProfile/2.0/gmlsfLevels.xsd">

and got a '404 not found' error.

So searched on 'gml' finding gml:AbstractFeature.
Digging from there looked at the namespace and found the gml.xsd.
Could not find 'AbstractFeature' there, but found it in another file at the gml site, feature.xsd.

Digging a bit further, I have found where AbstractFeature gets pulled in -- 3 levels deep within gml.xsd.

But that was a diversion from the original problem -- this '404 Not Found' error in emix.xsd.
Hopefully Carl will come up with a fix for that soon.

-A


Considine, Toby (Campus Services IT) wrote, On 6/22/2011 4:15 PM:

Anne

 

While the question of what an unnamed application might do in undefined circumstances is intriguing, it does not apply here. I can consume the MEIX schemas with any of three tools that *I* use – Liquid XML Studio, XML Spy, and Microsoft XSD.exe. Each of them finds GML and all of its sub-schemas w/o reporting any errors. With each of them, I can generate applications that are fully aware of GML, and produce Abstract Feature classes to manipulate and / or read artifacts based on the GML defined Types.  I have been doing so since we replaced KML with GML in the schema.

 

I do  not know which tool *you* are using, or whether you are attempting it by hand. I cannot know why you cannot find the features.

 

As to what happens when one is missing, that’s easy to find out. Grab any of the schemas. Take any one of the imported spaces. That will show you the error that your tools and or your environment generates.

 

tc

 


"It is the theory that decides what can be observed."   - Albert Einstein


Toby Considine

Chair, OASIS oBIX Technical Committee
U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee

Facilities Technology Office
University of North Carolina
Chapel Hill, NC

  

Email: Toby.Considine@ unc.edu
Phone: (919)962-9073

http://www.oasis-open.org

blog: www.NewDaedalus.com

 

 

From: Anne Hendry [mailto:ahendry@pacbell.net]
Sent: Wednesday, June 22, 2011 5:48 PM
To: Toby Considine
Cc: emix@lists.oasis-open.org
Subject: [emix] Re: reference and use of GML artifacts [Re: http://tools.oasis-open.org/issues/browse/EMIX-477]

 

While Carl is investigating ...

My question was really a technical question to assess the impact of the situation.  What does happen when an XML instance is created that refers to a schema element that can't be found (as in serviceArea refering to gml:AbstractFeature)?  If one of our XML examples referred to that element, what would happen when someone tried to use it?

I believe I have a general idea, but with all the XML experts on this list was hoping to get a more concrete idea.

-Anne


Toby Considine wrote, On 6/22/2011 2:13 PM:

I rely on the normative published specifications of the GML community.

Perhaps Carl, who is on this list, can answer....


tc


"He who fights with monsters should look to it that he himself does not
become a monster, and if you stare long into an abyss, the abyss also stares
into you."   - Fredrich Nietzche

Toby Considine
TC9, Inc
TC Chair: oBIX & WS-Calendar
TC Editor: EMIX, EnergyInterop
U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee

  Email: Toby.Considine@gmail.com
Phone: (919)619-2104
http://www.tcnine.com/
blog: www.NewDaedalus.com


-----Original Message-----
From: Anne Hendry [mailto:ahendry@pacbell.net] Sent: Wednesday, June 22, 2011 5:10 PM
To: Toby Considine; emix@lists.oasis-open.org
Subject: reference and use of GML artifacts [Re:
http://tools.oasis-open.org/issues/browse/EMIX-477]

My concern on our use of gml might be cleared up if I could get an answer to
this one hopefully straight-forward question:

What will happen if a user tries to create an XML instance of either EMIX
'serviceArea' or 'serviceLocation', which both refer to gml:AbstractFeature?

Thanks,
Anne

-----------------

Background info:

EMIX references only one GML artifact: 'gml:AbstractFeature' in two
locations:

- emix.xsd when defining 'serviceArea'
- power.xsd when defining 'serviceLocation'

gml:AbstractFeature is defined in
http://schemas.opengis.net/gml/3.2.1/feature.xsd.

EMIX namespace table 1-1 has the GML namespace: http://www.opengis.net/gml/3.2.
This redirects to http://schemas.opengis.net/gml/3.2.1/gml.xsd which
'includes' 7 other GML schema.

It does not include 'feature.xsd', where AbstractFeature is defined.

With no indication of where to find 'AbstractFeature'
(since the gml url in the EMIX schema doesn't exist either as per Jira 477),
what will happen if a user tries to use either 'serviceArea' or
'serviceLocation'?





 

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]